If that's the case it'll be nice. I'll have to see if I can change my
existing model into using the "pull" service. Is this going to be in
a12?
Will
Sean Legassick wrote:
>
> William,
>
> We are moving towards "pull" rather than "push" MVC. This means using
> Default screens that stuff a few useful objects in the context, rather
> than template-specific screens that restrict the template engineer to
> being able to write only one template that uses the objects that that
> screen stuffs in the context. Thus it makes a lot of sense to inherit
> the Default screen class from the directory above (it may be the only
> screen class altogether), but not to inherit from template-specific
> screens.
>
> In fact after I've finished my changes to the TurbinePullService which
> will allow specification of global, request-specific, session-specific
> and persistent tools in TR.props, there will be little need to write
> screen classes at all.
>
> Sean
>
> --
> Sean Legassick
> [EMAIL PROTECTED]
> Jeg er mann: Ingenting menneskelig er fremmed for meg
>
>
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
> Problems?: [EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
