on 1/22/01 10:17 PM, "Leon Messerschmidt" <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Just a couple of ideas for the pull model.
>
> At the moment we have a one-one mapping of screen code and template. For
> the pull model we're adding global and session objects to this model (if I
> understand right).
Correct. Global is currently done using the new Pull Service that Jason
implemented. per-request based objects are currently being added at the Page
level so that they are available to the rest of the Modules in the Context
as needed...I call these pre-request objects "System" objects, but I'm not
stuck on the name...
see:
<http://scarab.tigris.org/source/browse/scarab/src/java/org/tigris/scarab/pa
ges/ScarabPage.java?rev=1.1&content-type=text/x-cvsweb-markup>
> Can we maybe further this model by removing the one-one mapping of
> screens-templates. It can be implemented as an AssemblerFactory that reads
> an external mapping file that maps screens to templates.
The mapping may still be needed for security reasons as that would probably
fall into the C portion of MVC. For example, if you want to define security
for a single template or directory (with Default.java) but do not want to
put the checking into a template.
> We can execute the same peace of code for multiple templates.
You can do that with either static methods or defining an object that
several Screens share.
> Another
> possibility is to be able to string screens together and make it possible to
> execute more that one screen for a template.
That is against the Turbine Module methodology. You really are not supposed
to chain screens together. This would be better accomplished by turning the
Screens into Navigations and you already have a way to do that with
$navigation.
thanks,
-jon
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]