On Sat, 15 Apr 2000, you wrote:
> -1. I don't want to have to make someone edit a single file (or any files)
> outside of the system in order to define new pages.
>
> The example above would not work for a distributed environment at all with
> multiple people adding pages to the system. It also would not work for dummy
> HTML designers who simply want to add a new .wm file to the system to make
> them edit something like this. We *need* to simplify things for these people
> otherwise this software isn't going to fly...
For now, I see three options to handle this:
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.
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.
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.
2 & 3 are really close to the same. The configuration is done in the
template itself via hidden fields, get/post/path info.
--
Dave
[EMAIL PROTECTED]
your flame > /dev/null
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
