> From: John McNally [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, January 30, 2001 7:57 PM
> To: Turbine
> Subject: Re: disabling further processing from action?
>
> A template is a lot of html/xml with some simple (hopefully)
> programming
> constructs thrown in. Types of templates that are supported to one
> degree or another are Velocity,WebMacro,JSP,FreeMarker.
>
> In turbine there are layout, navigation, screen templates. A response
> will be constructed using a layout template which will contain
> placeholders where the results of navigation templates and a screen
> template will go. (If one does not want to use Turbine's
> layout/navigation/screen page model, it can be set up to use only
> templates that would be considered type screen.)
>
> There are java classes backing the types of templates. The
> base classes
> that these would derive from are Layout, Navigation, and
> Screen. These
> classes can be used separate from a template system, but when
> used with
> a template system their primary use is to stuff objects into a context
> for use in the template; they might also enforce some security
> policies. It is possible as the template support evolves
> that the need
> for these classes may be removed.
>
> I think one source of confusion is the difference between the "screen"
> and "template" keywords when used in links. The "screen" keyword
> references a Screen (java class). This is almost never necessary when
> using a template system, but could be used for example if the response
> will be binary. So a link to a tarball download which is to
> fall within
> Turbine's security/session management would probably use the screen
> keyword.
>
> The template keyword refers to a "template screen", the template that
> contains the primary content for the response (as opposed to
> a template
> navigation). The java classes associated with the template will be
> assigned according to the directory and package structures of the
> application.
>
> So to summarize:
> As far as the url parameters go
> screen = java Screen class
> template = template screen file
John, great summary. This should be added in the xdocs somewhere.
--
Gonzalo A. Diethelm
[EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
