|
Trevor,What I meant was that at the very least, the "native GUI" should be able to output to a standard browser, which at its base recognizes HTML. Of course it can and should be taken up several notches.
-mark At 12/11/06 12:41 AM, you wrote:
Mark, You have the terms GUI and HTML mixed up. HTML is a TEXT markup language and not a GRAPHICAL language. Sure, it can align graphic objects, but it provides a very poor/thin GUI experience. Trevor ----- Original Message ----- From: "M. Lazarus" <mlazarus@xxxxxxxx> To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> Sent: Sunday, December 10, 2006 1:41 PM Subject: Re: Saving the System i: Fight Rather Than Switch > James, > > Today, a native GUI would have to map to HTML in a browser. > > -mark > > At 12/9/06 09:46 AM, you wrote: >>Tom Liotta <qsrvbas@xxxxxxxxxxxx> wrote: >> >> > I have no idea what this means. How do you 'integrate >> > the GUI' on any large multi-user system? >> > >> > I mean, do you add a GPU each time you add a user? Or >> > buy a new monitor/keyboard/mouse to plug into a kind of >> > "brick" with an Ethernet port leading back to the System >> > i, like a net-station? Or the 5292 graphics workstation? >>. . . >> >>Given the directions terminal evolution was going when IBM >>stopped 5250 data stream development at the 3489, I would >>say that at least the rudimentary building blocks of a >>native GUI were already there: IBM simply never bothered >>to provide the tools for developers to access the power >>hiding in the InfoWindow II series terminals. >> >>I stand by my previous comment that if they'd simply >>provided adequate tools to develop for the InfoWindow II, >>and had continued to develop the interface, we'd HAVE the >>bloody native GUI! >> >>-- >>JHHL
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.