on 6/11/01 1:06 PM, "Gary Lawrence Murphy" <[EMAIL PROTECTED]> wrote:
>
> Here's the naiive plan for my webapp:
>
> 1) I have an index page that may return one of two XML pages
> depending on the GET data. With no data, it uses Index.vm and
> the default page layout with headers, footers and nav just like
> in the TDK.
>
> (this is to support legacy interfaces, so there's no option of using
> actions; the page select must be driven by the data requested)
Actions can be specified at any time by placing the information into the
query string.
> 2) If the first case parm is defined, it uses Index.doBuildTemplate and
> calls data.setLayoutTemplate("Page1.vm") which only has one line that
> invokes a Page1Screen.vm; this lets me re-use the screen later.
>
> - Will this cause Turbine to run a
> APP.module.screens.Page1.doBuildTemplate() method or does it only
> run the Index.doBuildTemplate() ?
>
> If it doesn't call the Page1 method, I suppose I can just call it
> myself directly, but is there a better way to do page chaining?
Screen modules should not be chained. It is a design reason. Generally, you
can always come up with another solution to chaining two Screen Modules
together that ends up being a cleaner design in the long run.
-jon
--
"Open source is not available to commercial companies."
-Steve Ballmer, CEO Microsoft
<http://www.suntimes.com/output/tech/cst-fin-micro01.html>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
