> It seems to me that Turbine looks for layout template based on the assumption
> that different screen templates will have different layout templates. (That
> may
> explain why setScreenTemplate() actually changes the layout template)
>
> So, according to way that Turbine looks for templates, if several screen
> templates
> use the same one layout template, they should be grouped together into a
> directory
> and the layout template should be put into a corresponding layout directory.
>
> The drawback of this mechanism is that if a web site use more than one layout
> templates, the screen templates will have to be grouped not according to
> the business
> logic but to the Turbine's logic.
>
> Or, the web site may want to decide which layout template to use at
> runtime, and after
> that, save and restore the layout template every time the
> setScreenTemplate() is called.
>
> Neither is beautiful. I'm expecting Turbine will have a better way to
> handle that.
>
The beautiful thing about Turbine is that if the default service
implementation provided by Turbine is unsatisfactory you can write your
own and plug it in.
john mcnally
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
