On Mon, 4 Sep 2000, Jon Stevens wrote:
> WMSiteScreen.doBuild(data) -> TemplateScreen.doBuild(data) ->
> WMSiteScreen.doBuildTemplate(data) -> FooPage.doBuildTemplate(data, context)
yep - I get that but wouldn't just be simpler to do
TemplateScreen.doBuild(data) ->
WMSiteScreen.doBuildTemplate(data) -> FooPage.doBuildTemplate(data, context)
> When FooPage is done executing:
>
> TemplateScreen.doBuild(data) executes WMSiteScreen.buildTemplate(data) and
> returns the results.
>
> Yes, it is complicated, but gives a HUGE amount of flexibility for FooPage
> to override WMSiteScreen and TemplateScreen functionality while still
> allowing code to auto-call itself.
yep the functionality is invaluable :P. Templates are great
once you start to get your head around how turbine uses
them them :P
> If you have a suggestion for how to make
> this cleaner with the same amount of functionality, please suggest it.
It *looks* like you can just completely and utterly delete
protected ConcreteElement doBuild(RunData data) throws
Exception
{
return super.doBuild(data);
}
from WMSiteScreen and get identical behaviour. Then again I
only started recently playing with it - so I could be
completely wrong :P
Cheers,
Pete
*--------------------------------------------------*
| Latrobe University, | Does the name 'Pavlov' |
| Bundoora, Australia | ring a bell ? |
*--------------------------------------------------*
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
