About Green Screens and mouse-clickable UIs - Revision history

PoC: /* Pros and Cons */ Untypable characters

2025-06-04T15:25:07Z

Pros and Cons: Untypable characters

← Older revision		Revision as of 17:25, 4 June 2025
Line 68:		Line 68:

	The only feature the AS/400 UI itself lacks is [[wikipedia:Cut, copy, and paste\|Copy & Paste]]. So by utilizing a terminal emulator on current GUI based desktop systems to connect to the AS/400 terminal session, one can benefit from the best of both worlds. Also, one may connect a [[Using the Mouse on a Hardware Terminal\|PS/2-Mouse to certain IBM terminals]], also providing facilities for selecting and duplicating text.		The only feature the AS/400 UI itself lacks is [[wikipedia:Cut, copy, and paste\|Copy & Paste]]. So by utilizing a terminal emulator on current GUI based desktop systems to connect to the AS/400 terminal session, one can benefit from the best of both worlds. Also, one may connect a [[Using the Mouse on a Hardware Terminal\|PS/2-Mouse to certain IBM terminals]], also providing facilities for selecting and duplicating text.

			Depending on country the respective terminal keyboard was used for, certain characters can't be typed. A German keyboard lacks square brackets and curly braces, which makes programming in C very cumbersome.<ref>IBM allows certain [[wikipedia:Digraphs and trigraphs (programming)\|digraphs]] to overcome this limitation, though.</ref>

	== Weblinks ==		== Weblinks ==

PoC: /* Why still text, then? */ More precise

2025-06-04T15:09:11Z

Why still text, then?: More precise

← Older revision		Revision as of 17:09, 4 June 2025
Line 52:		Line 52:

	[[File:Main-menu-wsg.png\|thumb\|right\|Main Menu shown in a browser's window through ''Workstation Gateway''.]]		[[File:Main-menu-wsg.png\|thumb\|right\|Main Menu shown in a browser's window through ''Workstation Gateway''.]]
	IBM tried to make the AS/400 more click'n'pointy. There is a facility called ''Workstation Gateway''<ref>Usually available on ''<nowiki>http://your-as400-ip:5061/wsg</nowiki>'' after starting the appropriate TCP service.</ref>, translating AS/400 screen elements on the fly into their HTML counterpart, if existing. It basically works and it's clickable but it looks gross compared to modern standards: No icons, no color, no eye candy.		IBM tried to make the AS/400 more click'n'pointy. There is a facility called ''Workstation Gateway''<ref>Usually available on ''<nowiki>http://your-as400-ip:5061/wsg</nowiki>'' after starting the appropriate TCP service.</ref>, translating AS/400 screen elements on the fly into their HTML counterpart, if existing. It basically works and it's clickable but it looks gross compared to modern standards: No icons, no color, no eye candy. And it's cumbersome, because you're required to actually click those buttons resembling function keys.

	There's a program called ''Operations Navigator'' that comes as a Client Application, running (only) on Windows, providing graphical equivalents of some operating system commands/tasks. Some things (like the management of the integrated CIFS/SMB-Server) could be configured solely with ''OpNav'' but not with Green Screen commands and forms.<ref>If you find out who took this decision, please let me know. I'd love to unload some serious cusses on him.</ref>		There's a program called ''Operations Navigator'' that comes as a Client Application, running (only) on Windows, providing graphical equivalents of some operating system commands/tasks. Some things (like the management of the integrated CIFS/SMB-Server) could be configured solely with ''OpNav'' but not with Green Screen commands and forms.<ref>If you find out who took this decision, please let me know. I'd love to unload some serious cusses on him.</ref>

PoC: /* How the AS/400 Text-UI works */ Typo

2025-06-04T15:07:35Z

How the AS/400 Text-UI works: Typo

← Older revision		Revision as of 17:07, 4 June 2025
Line 43:		Line 43:
	* AS/400 menus, forms and GUIs present structured information to the user that (hopefully) guide the user to take the right steps for completing a given task. They ''interact'' with the user.		* AS/400 menus, forms and GUIs present structured information to the user that (hopefully) guide the user to take the right steps for completing a given task. They ''interact'' with the user.

	It should be worth noting that the design of the user interface is not a complete new invention with the AS/400. Its heritage dates back to the [[wikipedia:IBM_System/38\|System/38 and its inception in the 1970s. An overview about the massive amount of careful planning has been described in ''IBM system/38—an IBM usability experience'' (see [[#Weblinks\|Weblinks]] below), in implicit comparison with the then common mainframe operating systems.		It should be worth noting that the design of the user interface is not a complete new invention with the AS/400. Its heritage dates back to the [[wikipedia:IBM_System/38\|System/38]] and its inception in the 1970s. An overview about the massive amount of careful planning has been described in ''IBM system/38—an IBM usability experience'' (see [[#Weblinks\|Weblinks]] below), in implicit comparison with the then common mainframe operating systems.

	== Why still text, then? ==		== Why still text, then? ==

PoC: /* How the AS/400 Text-UI works */ Linkfix

2025-06-04T15:07:12Z

How the AS/400 Text-UI works: Linkfix

← Older revision		Revision as of 17:07, 4 June 2025
Line 43:		Line 43:
	* AS/400 menus, forms and GUIs present structured information to the user that (hopefully) guide the user to take the right steps for completing a given task. They ''interact'' with the user.		* AS/400 menus, forms and GUIs present structured information to the user that (hopefully) guide the user to take the right steps for completing a given task. They ''interact'' with the user.

	It should be worth noting that the design of the user interface is not a complete new invention with the AS/400. Its heritage dates back to the [~~https~~:~~//en.wikipedia.org/wiki/~~IBM_System/38 System/38] and its inception in the 1970s. An overview about the massive amount of careful planning has been described in ''IBM system/38—an IBM usability experience'' (see [[#Weblinks\|Weblinks]] below), in implicit comparison with the then common mainframe operating systems.		It should be worth noting that the design of the user interface is not a complete new invention with the AS/400. Its heritage dates back to the [[wikipedia:IBM_System/38\|System/38 and its inception in the 1970s. An overview about the massive amount of careful planning has been described in ''IBM system/38—an IBM usability experience'' (see [[#Weblinks\|Weblinks]] below), in implicit comparison with the then common mainframe operating systems.

	== Why still text, then? ==		== Why still text, then? ==

PoC: S/38 heritage

2025-06-02T11:27:39Z

S/38 heritage

← Older revision		Revision as of 13:27, 2 June 2025
Line 42:		Line 42:
	* CLIs are unintuitive because their cursors blink at the user, patiently waiting for a command to be entered but hinting no clue what to type.<ref>Entering <code>help</code> within a ''bash'' Linux Command Line prints overwhelming 46 lines of internal commands. The important lines how to actually get more help have scrolled out of the usual 80×25 window.</ref>		* CLIs are unintuitive because their cursors blink at the user, patiently waiting for a command to be entered but hinting no clue what to type.<ref>Entering <code>help</code> within a ''bash'' Linux Command Line prints overwhelming 46 lines of internal commands. The important lines how to actually get more help have scrolled out of the usual 80×25 window.</ref>
	* AS/400 menus, forms and GUIs present structured information to the user that (hopefully) guide the user to take the right steps for completing a given task. They ''interact'' with the user.		* AS/400 menus, forms and GUIs present structured information to the user that (hopefully) guide the user to take the right steps for completing a given task. They ''interact'' with the user.

			It should be worth noting that the design of the user interface is not a complete new invention with the AS/400. Its heritage dates back to the [https://en.wikipedia.org/wiki/IBM_System/38 System/38] and its inception in the 1970s. An overview about the massive amount of careful planning has been described in ''IBM system/38—an IBM usability experience'' (see [[#Weblinks\|Weblinks]] below), in implicit comparison with the then common mainframe operating systems.

	== Why still text, then? ==		== Why still text, then? ==
Line 66:		Line 68:

	The only feature the AS/400 UI itself lacks is [[wikipedia:Cut, copy, and paste\|Copy & Paste]]. So by utilizing a terminal emulator on current GUI based desktop systems to connect to the AS/400 terminal session, one can benefit from the best of both worlds. Also, one may connect a [[Using the Mouse on a Hardware Terminal\|PS/2-Mouse to certain IBM terminals]], also providing facilities for selecting and duplicating text.		The only feature the AS/400 UI itself lacks is [[wikipedia:Cut, copy, and paste\|Copy & Paste]]. So by utilizing a terminal emulator on current GUI based desktop systems to connect to the AS/400 terminal session, one can benefit from the best of both worlds. Also, one may connect a [[Using the Mouse on a Hardware Terminal\|PS/2-Mouse to certain IBM terminals]], also providing facilities for selecting and duplicating text.

			== Weblinks ==
			* [https://dl.acm.org/doi/10.1145/800049.801791 IBM system/38—an IBM usability experience], ACM Digital Library

	== Footnotes ==		== Footnotes ==

PoC: /* Why still text, then? */ +link

2024-10-07T02:11:42Z

Why still text, then?: +link

← Older revision		Revision as of 04:11, 7 October 2024
Line 54:		Line 54:
	There's a program called ''Operations Navigator'' that comes as a Client Application, running (only) on Windows, providing graphical equivalents of some operating system commands/tasks. Some things (like the management of the integrated CIFS/SMB-Server) could be configured solely with ''OpNav'' but not with Green Screen commands and forms.<ref>If you find out who took this decision, please let me know. I'd love to unload some serious cusses on him.</ref>		There's a program called ''Operations Navigator'' that comes as a Client Application, running (only) on Windows, providing graphical equivalents of some operating system commands/tasks. Some things (like the management of the integrated CIFS/SMB-Server) could be configured solely with ''OpNav'' but not with Green Screen commands and forms.<ref>If you find out who took this decision, please let me know. I'd love to unload some serious cusses on him.</ref>

	Also, the Configuration of the IBM http server is done via Web Browser, and CGI-Programs running on the AS/400. Unfortunately, this facility is painfully slow, at least on a 150. Not exactly the best promotion for IBM, trying to convince programmers and system administrators to abandon text interfaces in favor to Web Based Applications.<ref>Fortunately, the [[IBM HTTP-Server for AS/400 Configuration\|configuration]] is text based and saved in a database file.</ref>		Also, the Configuration of the [[IBM HTTP-Server for AS/400 Configuration\|IBM http server]] is done via Web Browser, and CGI-Programs running on the AS/400. Unfortunately, this facility is painfully slow, at least on a 150. Not exactly the best promotion for IBM, trying to convince programmers and system administrators to abandon text interfaces in favor to Web Based Applications.<ref>Fortunately, the [[IBM HTTP-Server for AS/400 Configuration\|configuration]] is text based and saved in a database file.</ref>

	So, the main reason for IBM retaining the text interface is compatibility. For the rest of us, the fact that they're displayed very quickly with a lot less of resources (memory, data transfer speed, cpu cycles) needed when compared to a graphical UI is possibly of equal importance.		So, the main reason for IBM retaining the text interface is compatibility. For the rest of us, the fact that they're displayed very quickly with a lot less of resources (memory, data transfer speed, cpu cycles) needed when compared to a graphical UI is possibly of equal importance.

Mlc: /* How the AS/400 Text-UI works */

2023-01-25T02:05:05Z

How the AS/400 Text-UI works

Mlc: /* Introduction */

2023-01-25T02:00:45Z

Introduction

← Older revision		Revision as of 04:00, 25 January 2023
Line 8:		Line 8:
	These very same people see an (emulated) AS/400 screen and almost immediately the expected behavior kicks in: Old, outdated, legacy, you name it.		These very same people see an (emulated) AS/400 screen and almost immediately the expected behavior kicks in: Old, outdated, legacy, you name it.

	Seen from another point of view, the AS/400 is commonly perceived as ultimately boring. That is because the AS/400 is mostly running stuff considered boring (by geeks). Commercial IT at ~~it's~~ best<ref>Or worst.</ref>: Warehouse management, personnel administration, tracking account movements, to name a few. Stuff that makes sure civilisation as we know it ~~won't~~ collapse, because money stops flowing, carriage of goods ceases, personnel isn't directed to where needed.		Seen from another point of view, the AS/400 is commonly perceived as ultimately boring. That is because the AS/400 is mostly running stuff considered boring (by geeks). Commercial IT at its best<ref>Or worst.</ref>: Warehouse management, personnel administration, tracking account movements, to name a few. Stuff that makes sure civilisation as we know it won’t collapse, because money stops flowing, carriage of goods ceases, personnel isn't directed to where needed.

	Then, there are also some people who argue that by keeping the ''green screen'' alive, the '''perceived''' outdatedness of the system to others is even more increased. They emphasize that this is doing great harm to the IBM i platform at large, because all effort to convince people that it's not about green screens anymore, is negated. So, interestingly, ~~they're~~ not appalled against green screens because they don't like them themselves, but because they care about '''other people's perceptions''' over reasonable facts that green screens still have their use cases.<ref>Weird? I think so, also.</ref>		Then, there are also some people who argue that by keeping the ''green screen'' alive, the '''perceived''' outdatedness of the system to others is even more increased. They emphasize that this is doing great harm to the IBM i platform at large, because all effort to convince people that it's not about green screens anymore, is negated. So, interestingly, they’re not appalled against green screens because they don't like them themselves, but because they care about '''other people's perceptions''' over reasonable facts that green screens still have their use cases.<ref>Weird? I think so, also.</ref>

	== The Best of both Worlds ==		== The Best of both Worlds ==

PoC: +Link

2022-10-25T21:34:26Z

+Link

← Older revision		Revision as of 23:34, 25 October 2022
Line 65:		Line 65:
	* AS/400 forms and menus are built from tiny chunks of data compared to graphical UIs. So they can be transferred and displayed very fast. In environments where client and server are connected through high latency networks, GUIs perform poorly because of lagging response from the UI. Also, GUIs graphical representation must be built by program code running in part on the displaying client's CPU and GPU. Just displaying characters on a CRT can be done with comparatively tiny resources (a few kiB of RAM, and a processor clocked in the single-digit Megahertz range).		* AS/400 forms and menus are built from tiny chunks of data compared to graphical UIs. So they can be transferred and displayed very fast. In environments where client and server are connected through high latency networks, GUIs perform poorly because of lagging response from the UI. Also, GUIs graphical representation must be built by program code running in part on the displaying client's CPU and GPU. Just displaying characters on a CRT can be done with comparatively tiny resources (a few kiB of RAM, and a processor clocked in the single-digit Megahertz range).

	The only feature the AS/400 UI itself lacks is [[wikipedia:Cut, copy, and paste\|Copy & Paste]]. So by utilizing a terminal emulator on current GUI based desktop systems to connect to the AS/400 terminal session, one can benefit from the best of both worlds. Also, one may connect a PS/2-Mouse to an IBM ~~3486 terminal~~, also providing facilities for selecting and duplicating text.		The only feature the AS/400 UI itself lacks is [[wikipedia:Cut, copy, and paste\|Copy & Paste]]. So by utilizing a terminal emulator on current GUI based desktop systems to connect to the AS/400 terminal session, one can benefit from the best of both worlds. Also, one may connect a [[Using the Mouse on a Hardware Terminal\|PS/2-Mouse to certain IBM terminals]], also providing facilities for selecting and duplicating text.

	== Footnotes ==		== Footnotes ==

PoC: reworded slightly

2021-02-25T12:30:38Z

reworded slightly

Show changes

← Older revision		Revision as of 04:05, 25 January 2023
Line 23:		Line 23:

	== How the AS/400 Text-UI works ==		== How the AS/400 Text-UI works ==
	The AS/400 was created as a business aid. This comes down to efficient handling of structured data that has to be entered, processed, stored, reviewed and maybe printed. The system was designed to help people interact in a reasonably user friendly way with it with the then state of the art technology: Character based interfaces utilizing a ~~Keyboard~~ for command and data input, and a CRT ~~Screen~~ for immediate display of the ~~system's~~ responses.<ref>Keep in mind that commercial and scientifical computing relied on punched card decks for input and paper prints for output right into the 1970s: Classical Batch Processing.</ref> But this ~~doesn't~~ automatically equate to a command line interface.		The AS/400 was created as a business aid. This comes down to efficient handling of structured data that has to be entered, processed, stored, reviewed and maybe printed. The system was designed to help people interact in a reasonably user friendly way with it with the then state of the art technology: Character based interfaces utilizing a keyboard for command and data input, and a CRT screen for immediate display of the system’s responses.<ref>Keep in mind that commercial and scientifical computing relied on punched card decks for input and paper prints for output right into the 1970s: Classical Batch Processing.</ref> But this doesn’t automatically equate to a command line interface.

	The AS/400 has a unique feature that distinguishes it from other character based systems, like Unix: The whole UI revolves mainly around forms and menus, accompanied by static text. The layouts of these screens are somewhat standardized. AS/400 screens are very recognizable because of this.		The AS/400 has a unique feature that distinguishes it from other character based systems, like Unix: The whole UI revolves mainly around forms and menus, accompanied by static text. The layouts of these screens are somewhat standardized. AS/400 screens are very recognizable because of this.

	[[File:Main-menu.png\|thumb\|right\|German Main Menu after Signon.]]		[[File:Main-menu.png\|thumb\|right\|German Main Menu after Signon.]]
	The classic AS/400 green screen consists of numbered menu items with an input line beneath. One may enter a number and press <code>Enter</code> to pick a menu choice. Or someone may enter a command with accompanying parameters into the same space, if one knows what to enter. If one ~~doesn't~~ know the exact parameters and allowed values of a command, a keypress of <code>F4</code> invokes a full screen form for the requested command, aiding the user in choosing the right parameters for the desired action to be taken.		The classic AS/400 green screen consists of numbered menu items with an input line beneath. One may enter a number and press <code>Enter</code> to pick a menu choice. Or someone may enter a command with accompanying parameters into the same space, if one knows what to enter. If one doesn’t know the exact parameters and allowed values of a command, a keypress of <code>F4</code> invokes a full screen form for the requested command, aiding the user in choosing the right parameters for the desired action to be taken.

	Sometimes, choosing a menu item reveals another menu. Sometimes a form with text input fields is displayed for the user to fill in needed parameters, so the command may be run with the desired outcome. Rarely no parameters are supported and the command just runs.		Sometimes, choosing a menu item reveals another menu. Sometimes a form with text input fields is displayed for the user to fill in needed parameters, so the command may be run with the desired outcome. Rarely no parameters are supported and the command just runs.

	For every editable field on the screen, the user is allowed to place the cursor there and again press <code>F4</code> to be presented with ''another'' screen, listing allowed values for this particular parameter.<ref>Interestingly, there are situations when you are forced to enter data from your (brain based) memory into a field instead of the system letting the user choose from available choices on another <code>F4</code>-invoked screen. A notable example is when you want to create a ''line description'' configuration object, ~~you'll~~ need to do a manual lookup of available hardware IDs before.</ref>		For every editable field on the screen, the user is allowed to place the cursor there and again press <code>F4</code> to be presented with ''another'' screen, listing allowed values for this particular parameter.<ref>Interestingly, there are situations when you are forced to enter data from your (brain based) memory into a field instead of the system letting the user choose from available choices on another <code>F4</code>-invoked screen. A notable example is when you want to create a ''line description'' configuration object, you’ll need to do a manual lookup of available hardware IDs before.</ref>

	If this facility also fails to provide proper enlightenment, one may press <code>F1</code> at any time to invoke a [[wikipedia:Context-sensitive_help\|context-sensitive]]<ref>This means: The shown help text is different for different cursor positions on the screen.</ref> help text, which is almost always surprisingly helpful<ref>Compared to the help texts in early Windows operating systems.</ref>. See [[CL Tricks]] for an overview. These features are unique among text based UIs.		If this facility also fails to provide proper enlightenment, one may press <code>F1</code> at any time to invoke a [[wikipedia:Context-sensitive_help\|context-sensitive]]<ref>This means: The shown help text is different for different cursor positions on the screen.</ref> help text, which is almost always surprisingly helpful<ref>Compared to the help texts in early Windows operating systems.</ref>. See [[CL Tricks]] for an overview. These features are unique among text based UIs.

	The ubiquitous ''command shell'' of Unix, ~~Mac OS X~~, Windows and others is restricted to commands to be entered, together with (sometimes mandatory) parameters. Commands are entered into the last line of the terminal window. Output from commands appears over this line and scrolls to the top until ~~it's~~ out of sight<ref>Depending on the terminal emulator, a scrollback-buffer can be configured to allow retrieval of older output messages within the GUI.</ref>.<br>		The ubiquitous ''command shell'' of Unix, macOS, Windows and others is restricted to commands to be entered, together with (sometimes mandatory) parameters. Commands are entered into the last line of the terminal window. Output from commands appears over this line and scrolls to the top until it’s out of sight<ref>Depending on the terminal emulator, a scrollback-buffer can be configured to allow retrieval of older output messages within the GUI.</ref>.<br>
	Any help for a ~~command's~~ parameters must be invoked by separate facilities (e. g. invoking the command with a [[wikipedia:Command-line interface#Command-line option\|parameter]] to show an usually terse online help, or by reading Unix [[wikipedia:man page\|Man-Pages]]), and manually complete the command line by re-entering the needed command options.<ref>The only other known system with a comparable function is ~~Apple's~~ legacy Unix system ''A/UX'': Double-clicking a command (as opposed to an Application Program) opens a modal graphical display box, helping in completing the command line utilizing familiar graphical UI elements.</ref>		Any help for a command’s parameters must be invoked by separate facilities (e. g. invoking the command with a [[wikipedia:Command-line interface#Command-line option\|parameter]] to show an usually terse online help, or by reading Unix [[wikipedia:man page\|Man-Pages]]), and manually complete the command line by re-entering the needed command options.<ref>The only other known system with a comparable function is Apple’s legacy Unix system ''A/UX'': Double-clicking a command (as opposed to an Application Program) opens a modal graphical display box, helping in completing the command line utilizing familiar graphical UI elements.</ref>

	Concluding: The AS/400 is located somewhere in between GUI and CLI. As one might see now, intuitive user interfaces must not necessarily equate to being graphic (pixel-based).		Concluding: The AS/400 is located somewhere in between GUI and CLI. As one might see now, intuitive user interfaces must not necessarily equate to being graphic (pixel-based).
	* CLIs are unintuitive because their cursors blink at the user, patiently waiting for a command to be entered but hinting no clue what to type.<ref>Entering <code>help</code> within a ''bash'' Linux Command Line prints overwhelming 46 lines of internal commands. The important lines how to actually get more help have scrolled out of the usual 80×25~~-Window~~.</ref>		* CLIs are unintuitive because their cursors blink at the user, patiently waiting for a command to be entered but hinting no clue what to type.<ref>Entering <code>help</code> within a ''bash'' Linux Command Line prints overwhelming 46 lines of internal commands. The important lines how to actually get more help have scrolled out of the usual 80×25 window.</ref>
	* AS/400 menus, forms and GUIs present structured information to the user that (hopefully) guide the user to take the right steps for completing a given task. They ''interact'' with the user.		* AS/400 menus, forms and GUIs present structured information to the user that (hopefully) guide the user to take the right steps for completing a given task. They ''interact'' with the user.