I am tyring out WebMacroSitePage. It works great. Good
jobs guys!
Some variables ("data","link","title", etc.) are
automatically stored in the context (to make things
better). I am a little concerned about the naming of
any vairable that may be put by the underlying code
(i.e. TurbineWebMacroService). If new variables get
added in the core code (TurbineWebMacroService) in
future, it may collide with a name used by an existing
Screen.
For an example, I may use a name "foo" in my screen
'Bar', and use the variable "$foo" in the template
Bar.wm. However, in future if someone adds "foo" as a
reserved variale in the context, I am in trouble, I
will have to change either my code or override the
default code.
A possible solution would be to make a rule on how I
may name my variables and/or how the core system may
name the variables.
Just my 2 cents ...
Thanks ...
-shovon-
__________________________________________________
Do You Yahoo!?
Send instant messages & get email alerts with Yahoo! Messenger.
http://im.yahoo.com/
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
