>
> 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?
>
OK, How does this sound:
1. WMSitePage finds the Screen for a screen template.
2. Screen.getLayout(data) is called
3. If it returns a name with the default extension from the properties file
(or some standards: wm, fm, html, etc.) assume layout template. If some
String is returned that doesn't meet the above assume a class has been
specified. If the Screen.getLayout(data) returns null use the naming scheme
method, which may finally end in no layout at all
BTW, I mentioned earlier that I think I will want to use the name
association for layout template/Layout in the same way it is used for screen
template/Screen. I was hoping to use the same result that occured for the
Screen just a different Loader, but since the naming between a layout and
screen template it may have to perform its own tree walking.
> > 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...;-)
>
I have to implement the layout stuff on Monday or Tuesday specifically for
FreeMarker, but I will try to generalize things like I suggested a few
emails ago. I've been so busy though, I am having trouble writing general
code, so it could take me a week to alter things. Really wanting to work on
jFT and came into work to do it, but it seems I forgot to check in some code
from home and I don't want to repeat it, so I'm going back home to work on
my 14" monitor.
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
