On Sat, May 20, 2000 at 02:29:52PM -0700, jon * wrote:
> on 5/20/2000 1:56 PM, Frank Conradie <[EMAIL PROTECTED]> wrote:
>
> > I agree with Shovon's sentiments. What about placing the built-in names
> > inside ONE reserved "class" variable, e.g. $Reserved.Form,
> > $Reserved.Session, $Reserved.xxx
> >
> If anything, I would make it $Turbine...
Yes, if anything.
> I do think a naming convention would be good, but I hesitate to break other
> people's applications (I don't mind fixing Scarab though)...
I can see the benefit of putting all turbine stuff in one object, but I
fail to get _that_ excited about it. After all if you don't know about
an object that gets stuffed in the context by Turbine, your templates
are unlikely to use it :-) And with the exception of screen_placeholder
all the Turbine stuff gets stuffed in the context quite early on, so
it'll be your objects overwriting Turbine ones rather than vice versa.
Having said that I've no objection to fixing up my templates if the
change is made.
--
Sean Legassick
[EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
