on 4/18/00 5:58 PM, dave bryson <[EMAIL PROTECTED]> wrote:
> What's cool about what John M has designed here is that Page authors
> can define layout and navigations with templates. More on that later.
Right.
> Screens follow this rule. If there's a one-to-one relationship
> between a screen and a template then they should both have the same
> name. It a template does not match a particular screen, then it will
> be picked up and executed by the WebMacroSiteScreen. John's doc has a
> good explanation of how it works:
Right.
> The templates can be grouped in directories with common layouts.
> Screen modules are then expected to be placed in packages
> corresponding with the templates' directories and follow a specific
> naming scheme.
Ok.
> Note: When one-to-one template to screen relationships are needed,
> developers can extend the WebMacroSiteScreen and override the
> doBuildtemplate() with the particular logic or data. In most cases
> that's all they should need to do.
Ok. So let me get this straight...
URL looks like this:
/servlets/template/Foo.wm
DefaultScreen is: WebMacroSiteScreen
That would cause:
WebMacroSiteScreen to be executed and it would find Foo.wm in which path? A
path relative to the Webmacro TemplatePath property or relative to the path
where the .class files are located?
> Only one Layout module (see WebMacroSiteLayout) is used, since it is
> expected that any dynamic content will be placed in navigations and
> screens. The layout template to be used is found in a similar way to
> the Screen. For example the following paths will be searched in the
> layouts subdirectory:
> /about_us/directions/driving.wm
> /about_us/directions/default.wm
> /about_us/default.wm
> /default.wm
Ok! Perfect. How about making the last option null...in other words...if
/default.wm doesn't exist, just execute the screen and return it. This is
good for development when there is no Layout...
> The content for the screen_holder variable above is created on the
> WebMacroSiteLayout.
...as a result of the execution of the Screen?
> As for navigations, I'm creating a $navigation.setPage() tag so the page
> author can use it as above.
I would name this...setTemplate() or evaluateTemplate()
> I'm also creating the $link.setPage().setQS().setPI(). tag it allows
> authors to link WM pages together. The Link tag sets the
> template variable that's used to look up a screen.
cool...
> Are we on track???
+1. This is great!
-jon
--
Scarab -
Java Servlet Based - Open Source
Bug/Issue Tracking System
<http://scarab.tigris.org/>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
