on 5/6/2000 3:06 PM, John McNally <[EMAIL PROTECTED]> wrote:
> The "default" way of specifying a specific layout template for a screen
> template is to give them the same name. Why do you want to override this
> behavior in the Screen?
Because what if you want to have the layout change based on a value
retrieved from the database or GET/POST data or or or?
> A caching system would be good.
I agree. :-) We should generalize it though. Right now, we have that tree
walking code duplicated in about 20 different places...ok...well I'm
exaggerating, but you get the point...;-)
BTW, I just finished my first Action/Screen system using the new
WMSiteLayout stuff...it kicks ass...I made it so that Actions can now get
the WebMacroContext and stuff things into it. My Screen is about 5 lines of
code and my Action handles everything the screen sends to it. Cool.
-jon
--
Java Servlet Based - Open Source | Collab.Net
Bug/Issue Tracking System |
<http://scarab.tigris.org/> | <http://Collab.Net/jobs/>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
