> In reality, these days, a properly designed application
> should never have
> *any* Java Screen modules other than potentially a
> "Default.java" which gets
> executed for every Screen template in a directory. This is
> called the Pull Model.
Could you expand a little on that? Say you have a read-only
app (where you show the contents of your DB tables, but can't
modify them at all). So, no action classes here. Now, say you
have two screens, SA showing the contents of table A, and SB
showing the contents of table B. The selects and peers used
to retrieve the data are totally different in each screen.
I naturally see two screen classes here, SA.java and SB.java.
If this is not correct, or it is the old-fashioned way of doing
things, how would you do the same with one Default.java screen?
Thanks,
> -jon
--
Gonzalo A. Diethelm
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
