>
> I also believe that this method should be deprecated as it isn't used any
> longer in the template system.
>
Some people are still finding a use for this, I think it is best left as
is. Without this method there can only be one Layout.class as defined
in TR.props. Before I got this method working again within the template
system, people were finding all sorts of reasons to need a couple
different XXXLayout.class's. They can be a convenient place to place
things in the context that are relevant to both navs and screens, for
example. Or a place to put a security policy on a section of
templates. These things can be done in other ways, but maybe for some
circumstances this would be the most appropriate.
John McNally
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
