On Fri, Feb 23, 2001 at 09:21:47AM -0800, William Lee wrote:
> Well, based on the fall back rule there's no ambiguity. If there's no
> Index.class in the current directory, it'll fall back to the current
> directory's Default.class.
>
> Note the order of the fall back:
>
> screens.foo.bar.Index
> screens.foo.bar.Default
> screens.foo.Index
> screens.foo.Default
> screens.Index
> screens.Default
Okay, you had already answered my question and I didn't read properly -
sorry.
> Doing this will actually let you do two things. If you want your Index
> to fall to the parent's Index, then you just don't put the Default class
> in the directory. If you want to share the default in the current
> directory, then you'll put the Default class in the current directory so
> it can fall back to it.
So okay, that will work. I'm still a bit worried about the possibility
of invoking a screen class by accident (you have a template
"foo/Index.vm" and it doesn't have a scren class, and then your top level
Index.vm does have a class, and that class gets invoked for foo/Index.vm
even though you didn't mean it. Seems like too much magic to me (at
least if you have a class called Default it's pretty obvious that it may
get invoked for a variety of reasons...)
--
Sean Legassick
[EMAIL PROTECTED]
Ek is 'n man: niks menslik is vreemd vir my nie
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
