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)
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?
3) in the second case, Page2 must contain a URLEncoded version of Page1,
which would be simple enough if the Page1 was _not_ encoded (just insert
the Page1Screen.vm at the appropriate spot)
- Is there an easy way to hook into the template generate so the
Page2.vm layout will load a _processed_ version of the Page1.vm?
what I plan to do is to have an (as yet unknown) Velocity or
Turbine method called in doBuildTemplate to return a String
containing the expanded Page1 template, then encode this result
and place it in the context hash ... unless there is an easier
way ;)
--
Gary Lawrence Murphy <[EMAIL PROTECTED]> TeleDynamics Communications Inc
Business Innovations Through Open Source Systems: http://www.teledyn.com
"Computers are useless. They can only give you answers."(Pablo Picasso)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
