|
Don, I have written my fair share of green screen pseudo-GUI programs. Scroll bars, pop-up windows, etc. Functionally, they are excellent and user friendly. But the browser (and M$ Windows) look and feel is what the current computer user base is used to. Even died in the wool green screen operators are almost always comfortable with a browser. Faking it with the current 5250 capabilities just won't cut it. -mark
Mark: is there any reason why you can't create a GUI using existing keywords in DDS for example a text box in a Windows application is nothing more than a window with an i/o field which can be created in DDS with the key word Window. I know it takes a bit of typing as opposed to just dragging an object onto the screen from a toolbar, but the result is the same and you can use the mouse, and have Pushbuttons and so on... JMHO ****************************************** Don Wereschuk ISD - Programmer/Analyst Simcoe Parts Service Inc. Phone: 705-435-7814 Ex: 302 Fax: 705-435-6746 mailto:dwereschuk@xxxxxxxxxxxxxxx ****************************************** "Save the Cheerleader - Save the world" - Hiro Nakamura -----Original Message----- From: M Lazarus [mailto:mlazarus@xxxxxxxx] Sent: Monday, December 11, 2006 2:30 PM To: Midrange Systems Technical Discussion Subject: Re: Saving the System i: Fight Rather Than Switch Trevor, Having an HTTP server does NOT match my definition of GUI. I want to be able to (at least start to) GUI'ize my applications by using the EXFMT keyword (maybe w/ some extensions) and not have to have multiple "threads" within the program whether the client is a browser or green screen. This would make a basic browser session within reach of the average RPG programmer. I believe that it would be used FAR more than anything that is available now, in short time - giving the applications programs a large facelift. More sophisticated techniques could be added later, depending on the user's programming proficiency and the capabilities IBM is will to build in. I'm sure that they could tap into many existing routines to get the job done, so it would be a "from the ground up" effort. -markMark, Most people here know my thoughts on this. GUI can improveproductivity by30 to 80 percent. And, it costs MORE for green training in today'smodernworld. Data entry is human-error-prone outdated and can be replaced by myriads of choices. Green screen is simply kept for familiarity and resistance to change. I think that the System i can ALREADY be defined as matching the GUI definition you have - it has an HTTP server. I think it is YOUR applications that are not up to speed. That is what is giving the System i the badrep- not the OS.. Trevor ----- Original Message ----- From: "M. Lazarus" <mlazarus@xxxxxxxx> To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> Sent: Monday, December 11, 2006 12:16 AM Subject: Re: Saving the System i: Fight Rather Than SwitchTrevor, For the record, from a practical, business data entry standpoint, I don't think that a GUI has a major advantage over green screen (the exception being navigation.) In fact, it may be a hindrance. But, when it comes to identifying a screen / panel as being modern of old, a half decent GUI will look and fell more comfortable to the average user and manager and person in a software purchasing position. Enhancing an application is a lot different than making it a crucial part of your application. If I require a third party GUI application to market together with my software, then it's usually a non-starter. It might be OK as an optional component. BUT, and here's the key, you can throw as many 3rd party GUI vendors as you out there into the mix, but the system won't be known in the marketplace as having a native GUI. As far as the name is concerned, if IBM was truly pushing the brand name - AND added the modern, very visible components, then I think that it would make a difference. Anything else and it doesn't make much difference. -mark-- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.-- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.