on 4/15/00 8:39 PM, dave bryson <[EMAIL PROTECTED]> wrote:
> 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.
yea! I'm glad you "get it". ;-) I think this is some of what I was trying to
get at when I said what I said in the STATUS document a while ago...
> 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).
:-) Exactly. Did you look at my SelectorBox element that I added to
org.apache.turbine.util.webmacro? Lets work towards something like that. I
think it should be pretty easy to come up with something good. We can have a
"link" object that gets passed into the Context. That object's toString() is
able to new A().
> 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.
Yes...this is something that won't really affect designers working with
things now in their own systems so we can hold off on perfecting it until we
get things all sorted out and the new ground charted. ;-)
> 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.
:-) I'm here responding to all the emails as quickly as I can. :-)
Maybe we should have a Turbine Developers Summit in the Bay Area and bring
all the interested people into one room for a day or two...
-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]
