on 4/15/00 2:31 PM, dave bryson <[EMAIL PROTECTED]> wrote:
> 1. Put the information I described above in a database so it can be
> accessed/configured remotely. Or even take it one step farther and put
> the entire page in a database. Modify the Template Provider to grab
> the file from the DB instead of the disk. HTML authors can
> upload/manage files remotely. The name of the template becomes the
> keyed value in the database. For HTML authors, adding files could
> be as easy as FTPing them.
Experience has said that mixing a database with this is a mess. I tried to
do this on a project for Ascend back in 1998 or so and it didn't work out
well at all.
> 2. Pass the information I described above around via the session.
> For pages that contain no dynamic information have one screen
> (WMStaticScreen) that you the can pass many templates to. The only
> thing an HTML author needs to now then is a.) what screen the template
> belongs to and b.) they must set the template variable somewhere in
> the page.
Kinda better...but not making me happy yet.
> 3. Use the folder layout that John M. has in FreeMarker. This means
> that templates and Screen are laid out in a similiar structure. So the
> system looks up a best match between a Screen and Template from
> the template value passed. Other variables are passed around
> with the session.
+1 (note that John came up with this idea of functionality sitting in a
discussion with me him and Frank. ;-) )
-jon
--
Scarab -
Java Servlet Based - Open Source
Bug/Issue Tracking System
<http://scarab.tigris.org/>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
