> >
> > In the TODO list it mentions a "better thought-out/executed" Webmacro
Service.
> > IMO, the service is pretty close. Here the two areas I plan to look
at/work on:
> >
> > 1. Update the handleTemplate so it returns something other than a String
> > (something buffered).
> >
> > 2. Work on a default Layout for Webmacro pages. IMO, standard headers
and
> > footers can
> > be handled via Webmacro. In others the page author can add a #parse
include
> > statement
> > to his page for the standard header as opposed to defining one in the
> > navigations.
Why is it better to have WebMacro screens include their headers and
footers? I think it is much better to let Turbine handle assembling the
various parts of the page. Jon, I thought you said that using nested
templates significantly reduced WM's performance. Is this not what the
#parse include statement is doing? Besides Turbine already has a pretty
good system, I would say to not use some WM specific way of doing something
when the standard Turbine way of doing it is just as good. Of course, if
someone wants to build their application using #parse in their screens and
not using layouts they can do so, but I would prefer it not be done in the
standard distribution.
> >
> > I'm also thinking about having the Service use the
rundata.setOut(PrintWriter)
> > - thoughts?
I assume the reason is to start the response stream asap, or is there some
other reason. Building the page using the ECS Document, allows various
modules to add code (e.g. javascript or css) to the <head> tags in a
straightforward manner. It also makes error handling cleaner. Are you
going to build so that one can have the option of using it the way things
are now?
John McNally
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
