On Sat, 15 Apr 2000, you wrote:
> +1 (note that John came up with this idea of functionality sitting in a
> discussion with me him and Frank. ;-) )
Now that I've actually taken the time to understand John M's Freemarker
implementation (I should have done that from the start, he's really
put a tremendous amount of thought into this), I think it's the route
to go with WebMacro. IMO, this should be the easiest way for HTML
authors to use the service. In a nutshell, they only need to layout
the template pages in directories that correspond with Turbine -
navigations/
layout/
screen/
and name the templates to correspond to the Screen.
The Service will handle the mapping.
However, I still need to come up with a way to provide the HTML authors
with a link tag that they can pass through Turbine and
turn into a DynamicURI that's stored in the context. In Freemarker,
John has: ${link("http", "/stuff/index.html", "name", "value"....)}
I need to find the best way to do this in WM - maybe via a $variable or
custom context tool ( kind of a full circle to the discussion we had
about $dynamicuri a week ago).
The only other thing I really like to do is integrate both the services
at the DefaultPage level so you wouldn't have to switch between
DefaultPage, FreeMarkerPage, and WebMacroPage. This doesn't look like a
big deal. At the Page level the differences between them could probably
be handle via a properties flag such as "template.service.ext=wm" and
maybe a few others. However I'm relunctant to mess with it at this
stage until it all works well.
I really want to get this right. After reading across a couple of
mailing list and archives, I realize *why* this needs to be really
easy to use. : ) So any input along the way is appreciated.
--
Dave
[EMAIL PROTECTED]
your flame > /dev/null
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
