RE: A design philosophy question

--
--
[ Picked text/plain from multipart/alternative ]
Well given that the BL programs are already in place Joe then the answer is
quite simple.

One program with the screens designed within it.  No work is being done at
the green screen level except to populate a few data structures.   There'd
be what? Maybe 5 lines of code per format?  Each screen would call the
appropriate BL program.  Each screen would have an exfmt, a call/with parm,
and a repeat-or-go-forward decision.  There'd be... maybe 40 to 80 calc
lines total for the program?  Maybe 8 hours work?

I'd think the binding questions would only be significant at the BL layer
and below.

(I was not suggesting that you GUIize the project, but today we can no
longer afford to touch the data from the user interface level.  The
development costs are just too high, and user interfaces are in too much
flux.) That is my experience at least.)

---------------------------------------------------------
Booth Martin   http://www.MartinVT.com
Booth@MartinVT.com
---------------------------------------------------------

-------Original Message-------

From: rpg400-l@midrange.com
Date: Sunday, September 29, 2002 02:35:02 PM
To: rpg400-l@midrange.com
Subject: RE: A design philosophy question

> From: Booth Martin

>

> The horizontal layers I think of at first blush are:

> Top: GUI interface, only. No data files touched.


Booth, thanks for your input, but I respectfully decline the GUIzation of
this project. Forget the issue of UI/BL separation. Assume that's being
done. Assume now that I want a multiple panel green screen interface, NOT a
GUI interface. Then revisit the questions.

This has nothing to do with C/S architecture. This has to do with designing
a green screen interface, which is still occasionally required.

Joe
--
[ Content of type image/gif deleted ]
--