Screen class - Revision history

JAL2: Redirected page to Screen classes#Screens and ScreenFields

2012-08-28T19:40:45Z

Redirected page to Screen classes#Screens and ScreenFields

← Older revision		Revision as of 19:40, 28 August 2012
Line 1:		Line 1:
	#REDIRECT [[Screen classes]]		#REDIRECT [[Screen classes#Screens and ScreenFields]]

JAL2: Redirected page to Screen classes

2012-08-28T19:37:49Z

Redirected page to Screen classes

← Older revision		Revision as of 19:37, 28 August 2012
Line 1:		Line 1:
	#REDIRECT [[Screen classes~~#Highlight enumeration~~]]		#REDIRECT [[Screen classes]]

JAL2: Redirected page to Screen classes#Highlight enumeration

2012-08-28T19:15:36Z

Redirected page to Screen classes#Highlight enumeration

← Older revision		Revision as of 19:15, 28 August 2012
Line 1:		Line 1:
	#REDIRECT [[Screen classes]]		#REDIRECT [[Screen classes#Highlight enumeration]]

Tom: Redirected page to Screen classes

2011-04-07T19:17:18Z

Redirected page to Screen classes

Show changes

Dme at 21:02, 17 December 2010

2010-12-17T21:02:11Z

← Older revision		Revision as of 21:02, 17 December 2010
Line 15:		Line 15:
	=Screen methods=		=Screen methods=

	The individual Screen methods are described in the following sections. For information about the conventions followed, see [[~~Conventions and terminology~~]].		The individual Screen methods are described in the following sections. For information about the conventions followed, see [[Notation conventions for methods]].

	== <span style="color:#990000;">ActionKey property</span>==		== <span style="color:#990000;">ActionKey property</span>==
Line 404:		Line 404:
	*How to use [[Mod6 Screen\|Model 6]], or [[Mod6 Screens\|Dynamically Sized screens]] in Model 204.		*How to use [[Mod6 Screen\|Model 6]], or [[Mod6 Screens\|Dynamically Sized screens]] in Model 204.

	*[[~~Conventions~~ and terminology]] used in Sirius Software technical documentation.		*[[Documentation conventions and terminology]] used in Sirius Software technical documentation.

	<br /><br />		<br /><br />

	[[Category:System classes]]		[[Category:System classes]]

Dme at 21:43, 6 December 2010

2010-12-06T21:43:52Z

← Older revision		Revision as of 21:43, 6 December 2010
Line 408:		Line 408:
	<br /><br />		<br /><br />

	~~[[Category:Screen class]]~~		[[Category:System classes]]
	[[Category:System ~~Classes~~]]

Alan at 17:57, 2 December 2010

2010-12-02T17:57:13Z

← Older revision		Revision as of 17:57, 2 December 2010
Line 398:		Line 398:
	*The Janus SOAP manual in PDF format: http://sirius-software.com/maint/download/jansoapr.pdf		*The Janus SOAP manual in PDF format: http://sirius-software.com/maint/download/jansoapr.pdf

	*The [[Screenfield ~~class~~]] page on the Sirius Wiki.		*The [[:Category:Screenfield methods]] page on the Sirius Wiki.

	*[[Screen Object Sample Code]]		*[[Screen Object Sample Code]]
Line 409:		Line 409:

	[[Category:Screen class]]		[[Category:Screen class]]
	[[Category:~~Screen methods~~]]		[[Category:System Classes]]

Alan: add some category markers

2010-11-16T19:41:50Z

add some category markers

← Older revision		Revision as of 19:41, 16 November 2010
Line 405:		Line 405:

	*[[Conventions and terminology]] used in Sirius Software technical documentation.		*[[Conventions and terminology]] used in Sirius Software technical documentation.

			<br /><br />

			[[Category:Screen class]]
			[[Category:Screen methods]]

Alan: Turned on file (image) uploading, which should now appear at the left of everyone's Wiki pages, and added a picture to the Screen class page.

2010-09-28T15:41:16Z

Turned on file (image) uploading, which should now appear at the left of everyone's Wiki pages, and added a picture to the Screen class page.

← Older revision		Revision as of 15:41, 28 September 2010
Line 1:		Line 1:
	Introduced in version 7.1 of the [[Sirius Mods]], '''Screen objects''' are designed to make writing and maintaining User Language full-screen applications easier. They also let you take advantage of dynamic 3270 screen sizes in your applications.		[[File:ScreenObject.png\|thumb\|300px\|Screen object code can dynamically resize the application to use whatever space is available in the user's chosen 3270 configuration.]]Introduced in version 7.1 of the [[Sirius Mods]], '''Screen objects''' are designed to make writing and maintaining User Language full-screen applications easier. They also let you take advantage of dynamic 3270 screen sizes in your applications.

	Most modern 3270 emulators allow flexible definitions of 3270 screen sizes beyond the standard Models 2, 3, 4, and 5. Traditional User Language screen definitions define a fixed layout for a screen and so must be designed to be display correctly on even the smallest screen. This is usually the 3278 Model 2, which contains a none-too-generous 24 rows by 80 columns. Though a screen designed for a 24x80 layout will usually display correctly on other models, screens designed for other models may display misaligned data on a smaller screen, often rendering the application unusable on these screen types. This leaves the application programmer little choice but to design for the lowest common denominator — Model 2 — wasting precious screen space on larger screens.		Most modern 3270 emulators allow flexible definitions of 3270 screen sizes beyond the standard Models 2, 3, 4, and 5. Traditional User Language screen definitions define a fixed layout for a screen and so must be designed to be display correctly on even the smallest screen. This is usually the 3278 Model 2, which contains a none-too-generous 24 rows by 80 columns. Though a screen designed for a 24x80 layout will usually display correctly on other models, screens designed for other models may display misaligned data on a smaller screen, often rendering the application unusable on these screen types. This leaves the application programmer little choice but to design for the lowest common denominator — Model 2 — wasting precious screen space on larger screens.

JAL: /* AddField function */ Manually split syntax onto two lines

2010-08-31T19:28:30Z

AddField function: Manually split syntax onto two lines

← Older revision		Revision as of 19:28, 31 August 2010
Line 42:		Line 42:
	A ScreenField can only be defined within the limits of the current screen. The number of rows and columns in the current screen is determined by Screen class methods (“Rows property” and “Columns property”, below). An attempt to define a field outside these boundaries results in request cancellation. If any part of a new screen field would overlap an existing field, the request is cancelled.		A ScreenField can only be defined within the limits of the current screen. The number of rows and columns in the current screen is determined by Screen class methods (“Rows property” and “Columns property”, below). An attempt to define a field outside these boundaries results in request cancellation. If any part of a new screen field would overlap an existing field, the request is cancelled.

	[%sfield =] %screen:AddField( [Color=fieldcolor,] [Column=num,] [Highlight=bool,] [Invisible=bool,] [Itemid=num,] [Modified=bool,] [Numeric=bool,] [Protected=bool,] [Row=num,] [Value=string,] [Width=num,] )		[%sfield =] %screen:AddField( [Color=fieldcolor,] [Column=num,] [Highlight=bool,] [Invisible=bool,] [Itemid=num,] [Modified=bool,]
			Numeric=bool,] [Protected=bool,] [Row=num,] [Value=string,] [Width=num,] )

	; <font size='3'>AddField syntax</font>		; <font size='3'>AddField syntax</font>
Line 106:		Line 107:

	Each of the screenfield attributes specified by the AddField optional parameters can be updated by their like-named methods in the [[Screenfield class]]. The “modified” and “value” attributes are also set by a user screen-interaction.		Each of the screenfield attributes specified by the AddField optional parameters can be updated by their like-named methods in the [[Screenfield class]]. The “modified” and “value” attributes are also set by a user screen-interaction.



	== <font color="#990000">Columns property</font>==		== <font color="#990000">Columns property</font>==