RE: Green screen to GUI

VARPG started with OS/2 and limited memory.  The goal was to build a client
that would fit on a floppy.  That meant a runtime environment  for each desk
top, and then a small set of files for each application.  Times have changed
but i am not sure the IBM mind set has.

You are right, it is a thick client.  Here is the solution that I used &
liked.    I had success with building the application and the runtime as one
unit (usually under 20 megs) and installing them as a package on either the
server or each desktop.  That solved a whole set of problems and made
deployment relatively simple.
 
That meant a lot of redundacy for the runtime piece, but it solved version
problems and instalation problems.  With the application on the server I
could just e-mail a shortcut to each user, and they could drag the shortcut
onto their desktop and click it and they are up and running.

Remember, we already own this product.  Its bought and paid for.

---------------------------------
Booth Martin
http://www.martinvt.com
---------------------------------
-------Original Message-------
 
From: Midrange Systems Technical Discussion
Date: 09/21/05 13:04:06
To: midrange-l@xxxxxxxxxxxx
Subject: RE: Green screen to GUI
 
Martin,
 
Can you elabotrate on that?
 
I used to try it with the book written by  B. Meyers and J. Sutherland
(VisualAge For RPG by Example) five years ago.
What I recall it generated a lot of nested directories per project and the
results of one project can not be combined with another project.
 
If this is so (and is still the case), then I think it is a very thick
client sided software, difficult to distibute on your own network, not to
mention to provide it as a commercial solution.
 
I agree,  using a tabbed notebook you can combine multiple green screens in
one GUI screen, given it a more organized look and feel.
 
Regards,
Carel Teijgeler.