UI Style Guide Windows and Requesters - Revision history

Steven Solie: /* Requester Design */

2014-04-25T15:06:17Z

Requester Design

← Older revision		Revision as of 15:06, 25 April 2014
Line 106:		Line 106:
	If possible, use the standard requesters provided in the ASL library. Requesters are base-level operations and the user shouldn't have to learn new requester operations with each new software package he buys.		If possible, use the standard requesters provided in the ASL library. Requesters are base-level operations and the user shouldn't have to learn new requester operations with each new software package he buys.

	If you need to create your own, follow the ASL design. Here's an example of the ASL file requester:		If you need to create your own, follow the ASL design. Here's an example of the [[ASL File Requester\|ASL file requester]]:

	[[File:SG4-6.png\|frame\|center\|The standard ASL file requester]]		[[File:SG4-6.png\|frame\|center\|The standard ASL file requester]]

Philippe Ferrucci: /* Window Gadgets */

2013-05-24T22:29:34Z

Window Gadgets

← Older revision		Revision as of 22:29, 24 May 2013
Line 49:		Line 49:
	Here is a specific discussion of when and how to use system gadgets on your windows. More detailed information can be found in [[UI Style Guide Gadgets]].		Here is a specific discussion of when and how to use system gadgets on your windows. More detailed information can be found in [[UI Style Guide Gadgets]].

	~~Fig 4~~.3: Window gadgets.		[[File:SG4-3.png\|center\|Window gadgets]]

	=== Dragging Windows ===		=== Dragging Windows ===

Steven Solie: /* Requester Design */

2013-04-24T21:20:05Z

Requester Design

← Older revision		Revision as of 21:20, 24 April 2013
Line 108:		Line 108:
	If you need to create your own, follow the ASL design. Here's an example of the ASL file requester:		If you need to create your own, follow the ASL design. Here's an example of the ASL file requester:

	[[File:SG4-6.png\|frame\|center\|~~Fig 4.6:~~ The standard ASL file requester]]		[[File:SG4-6.png\|frame\|center\|The standard ASL file requester]]

	Spend some time on the wording and design of your requesters. Make sure they communicate clearly and succinctly what choices the user has and what will happen as a result of his choice.		Spend some time on the wording and design of your requesters. Make sure they communicate clearly and succinctly what choices the user has and what will happen as a result of his choice.
Line 120:		Line 120:
	Requesters should be opened adjoining or within the boundaries of the parent window. Use coordinates relative to the parent window rather than absolute coordinates when positioning a child window.		Requesters should be opened adjoining or within the boundaries of the parent window. Use coordinates relative to the parent window rather than absolute coordinates when positioning a child window.

	[[File:SG4-7.png\|frame\|center\|~~Fig 4.7:~~ A find and replace support window opening within the boundaries of the parent window]]		[[File:SG4-7.png\|frame\|center\|A find and replace support window opening within the boundaries of the parent window]]

	Positioning is especially important when the user is working with an extremely large virtual screen or a high-resolution monitor. On such a monitor, not limiting your requesters to the parent window boundaries can cause an annoying break in the work flow. Here's an example: the user is working in the lower right corner and you open a requester in the upper left. Relatively, that's a lot of screen real estate to move the pointer across. On a virtual screen the requester may not even show up on the current monitor view, leaving the user to wonder if his action had a result at all.		Positioning is especially important when the user is working with an extremely large virtual screen or a high-resolution monitor. On such a monitor, not limiting your requesters to the parent window boundaries can cause an annoying break in the work flow. Here's an example: the user is working in the lower right corner and you open a requester in the upper left. Relatively, that's a lot of screen real estate to move the pointer across. On a virtual screen the requester may not even show up on the current monitor view, leaving the user to wonder if his action had a result at all.
Line 132:		Line 132:
	When your program produces a requester indicating its failure to find a file, the requester's title bar should name the program that is looking for the file and the specific name of the file should be given in the text of the requester. For instance, getting the following requester at boot up could severely limit any troubleshooting:		When your program produces a requester indicating its failure to find a file, the requester's title bar should name the program that is looking for the file and the specific name of the file should be given in the text of the requester. For instance, getting the following requester at boot up could severely limit any troubleshooting:

	[[File:SG4-8.png\|frame\|center\|~~Fig 4.8:~~ The wrong way to do a requester stating that a file can't be found]]		[[File:SG4-8.png\|frame\|center\|The wrong way to do a requester stating that a file can't be found]]

	[[File:SG4-9.png\|frame\|center\|~~Fig 4.9:~~ The correct way to tell the user that your application can't find a file]]		[[File:SG4-9.png\|frame\|center\|The correct way to tell the user that your application can't find a file]]

	==== OK and OK ====		==== OK and OK ====
Line 140:		Line 140:
	Don't create requesters with two identical action gadgets, such as OK and OK. A single gadget for each choice will suffice.		Don't create requesters with two identical action gadgets, such as OK and OK. A single gadget for each choice will suffice.

	[[File:UG4-10.png\|frame\|center\|~~Fig 4.10:~~ Another incorrect requester. This one gives two identical action gadgets and no way for the user to back out of the operation]]		[[File:UG4-10.png\|frame\|center\|Another incorrect requester. This one gives two identical action gadgets and no way for the user to back out of the operation]]

Steven Solie: /* The Modified Project Requester */

2013-04-24T21:19:14Z

The Modified Project Requester

← Older revision		Revision as of 21:19, 24 April 2013
Line 100:		Line 100:
	Whenever the user makes changes to a project currently in memory and subsequently selects an action such as New, Open or Quit, any changes made to the current project will be lost. In that case, a modified project requester similar to the one below should be presented to the user:		Whenever the user makes changes to a project currently in memory and subsequently selects an action such as New, Open or Quit, any changes made to the current project will be lost. In that case, a modified project requester similar to the one below should be presented to the user:

	[[File:SG4-5.png\|frame\|center\|~~Fig 4.5:~~ A requester which should be used if the user tries to leave a file before saving the changes]]		[[File:SG4-5.png\|frame\|center\|A requester which should be used if the user tries to leave a file before saving the changes]]

	=== Requester Design ===		=== Requester Design ===

Steven Solie: /* Size and Position */

2013-04-24T21:18:47Z

Size and Position

← Older revision		Revision as of 21:18, 24 April 2013
Line 23:		Line 23:
	Let the user store his preferred window position "permanently" via the Save Settings menu option (see [[#Menu\|Menu]] for more information on menus). Unlike the scenario in the previous paragraph where the position is remembered only for that session, Save Settings saves the position for use each time the application is opened.		Let the user store his preferred window position "permanently" via the Save Settings menu option (see [[#Menu\|Menu]] for more information on menus). Unlike the scenario in the previous paragraph where the position is remembered only for that session, Save Settings saves the position for use each time the application is opened.

		⚫	{{Note\|text=The save Settings menu option allows the user to specify a default size and position for windows.}}
	{\| class="wikitable"
⚫	\| The save Settings menu option allows the user to specify a default size and position for windows.
	\|}

	=== Opening at Different Resolutions ===		=== Opening at Different Resolutions ===
Line 43:		Line 41:
	=== Successive Windows ===		=== Successive Windows ===

	When your application opens a number of project windows, you may want to position each successive window slightly lower than the previous one -		When your application opens a number of project windows, you may want to position each successive window slightly lower than the previous one - preferably, the height of the title bar plus one pixel. This will leave the window depth arrangement gadget open.
	preferably, the height of the title bar plus one pixel. This will leave the window depth arrangement gadget open.

	[[File:SG4-2.png\|frame\|center\|~~Fig 4.2:~~ Overlapping windows]]		[[File:SG4-2.png\|frame\|center\|Overlapping windows]]

	== Window Gadgets ==		== Window Gadgets ==

Steven Solie: /* A Safe Place to Click */

2013-04-24T21:18:03Z

A Safe Place to Click

← Older revision		Revision as of 21:18, 24 April 2013
Line 10:		Line 10:
	If your application uses the whole window for operations and has has no window title bar (like some paint packages), let the first click of the mouse on an inactive window activate the window instead of doing an operation.		If your application uses the whole window for operations and has has no window title bar (like some paint packages), let the first click of the mouse on an inactive window activate the window instead of doing an operation.

	[[File:SG4-1.png\|frame\|center\|~~Fig 4.1:~~ A window]]		[[File:SG4-1.png\|frame\|center\|A window]]

	== Size and Position ==		== Size and Position ==

Steven Solie at 20:10, 1 September 2012

2012-09-01T20:10:07Z

← Older revision		Revision as of 20:10, 1 September 2012
Line 1:		Line 1:
			== Windows and Requesters ==

	The last chapter noted that context cues on the Amiga come in the form of screens, windows and requesters. Whereas screens represent general		The last chapter noted that context cues on the Amiga come in the form of screens, windows and requesters. Whereas screens represent general
	environments, windows and requesters show the user where he is much more specifically.		environments, windows and requesters show the user where he is much more specifically.

Steven Solie: /* Give Directions */

2012-09-01T19:56:26Z

Give Directions

← Older revision		Revision as of 19:56, 1 September 2012
Line 133:		Line 133:
	When your program produces a requester indicating its failure to find a file, the requester's title bar should name the program that is looking for the file and the specific name of the file should be given in the text of the requester. For instance, getting the following requester at boot up could severely limit any troubleshooting:		When your program produces a requester indicating its failure to find a file, the requester's title bar should name the program that is looking for the file and the specific name of the file should be given in the text of the requester. For instance, getting the following requester at boot up could severely limit any troubleshooting:

	Fig 4.8: The wrong way to do a requester stating that a file can't be found.		[[File:SG4-8.png\|frame\|center\|Fig 4.8: The wrong way to do a requester stating that a file can't be found]]

	Fig 4.9: The correct way to tell the user that your application can't find a file.		[[File:SG4-9.png\|frame\|center\|Fig 4.9: The correct way to tell the user that your application can't find a file]]

	==== OK and OK ====		==== OK and OK ====

Steven Solie: /* Where to Open Requesters */

2012-09-01T19:54:39Z

Where to Open Requesters

← Older revision		Revision as of 19:54, 1 September 2012
Line 121:		Line 121:
	Requesters should be opened adjoining or within the boundaries of the parent window. Use coordinates relative to the parent window rather than absolute coordinates when positioning a child window.		Requesters should be opened adjoining or within the boundaries of the parent window. Use coordinates relative to the parent window rather than absolute coordinates when positioning a child window.

	Fig 4.7: A find and replace support window opening within the boundaries of the parent window.		[[File:SG4-7.png\|frame\|center\|Fig 4.7: A find and replace support window opening within the boundaries of the parent window]]

	Positioning is especially important when the user is working with an extremely large virtual screen or a high-resolution monitor ~~such as Commodore's A2024~~. On a monitor ~~like the A2024~~, not limiting your requesters to the parent window boundaries can cause an annoying break in the work flow. Here's an example: the user is working in the lower right corner and you open a requester in the upper left. Relatively, that's a lot of screen real estate to move the pointer across. On a virtual screen the requester may not even show up on the current monitor view, leaving the user to wonder if his action had a result at all.		Positioning is especially important when the user is working with an extremely large virtual screen or a high-resolution monitor. On such a monitor, not limiting your requesters to the parent window boundaries can cause an annoying break in the work flow. Here's an example: the user is working in the lower right corner and you open a requester in the upper left. Relatively, that's a lot of screen real estate to move the pointer across. On a virtual screen the requester may not even show up on the current monitor view, leaving the user to wonder if his action had a result at all.

	==== Always Give a Safe Way Out ====		==== Always Give a Safe Way Out ====

Steven Solie: /* The Modified Project Requester */

2012-09-01T19:51:56Z

The Modified Project Requester

← Older revision		Revision as of 19:51, 1 September 2012
Line 101:		Line 101:
	Whenever the user makes changes to a project currently in memory and subsequently selects an action such as New, Open or Quit, any changes made to the current project will be lost. In that case, a modified project requester similar to the one below should be presented to the user:		Whenever the user makes changes to a project currently in memory and subsequently selects an action such as New, Open or Quit, any changes made to the current project will be lost. In that case, a modified project requester similar to the one below should be presented to the user:

	Fig 4.5: A requester which should be used if the user tries to leave a file before saving the changes.		[[File:SG4-5.png\|frame\|center\|Fig 4.5: A requester which should be used if the user tries to leave a file before saving the changes]]

	=== Requester Design ===		=== Requester Design ===