Darren Gilroy wrote:
>
> Hi -
>
> It seems to me that my understanding of the screen/layout thing is that the
> following approach would be preferred:
>
> Public class myScreen extends TemplateScreen {
>
> ... Normal implementation here ... or nothing ...
>
> public String getLayout ( RunData data ) {
> ... return your layout instead of the default layout
> ... using whatever logic you desire
> }
> }
>
> If you derive your screens from the myScreen class, I believe that when
> setScreenTemplate is called, and turbine goes on its hunt for the proper
> layout, your getLayout method (above) will be called and return the layout
> you desire.
>
> I am not 100% sure of this result, but it may be worth a try.
>
> Good Luck!
> -best-darr-
>
This will return the name of the Layout module (java class) that will be
executed for myScreen. It is possible to override this for some Screens
like you propose. If the Layout logic is global for the app though you
can just specify a different default Layout in TR.props.
john mcnally
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
