Tips.js from mootools-more uses "tip:title", "tip:enter" etc. as the
keys. Imho, its a good idea to use a namespace or unique name, because
more than one script could have the idea to store an "event" key. If
you just need one key and its named "fooslideshow" with your plugin/
class name its not worth using "fooslideshow:slideshow".
just my 2ยข
On Feb 9, 2009, at 18:51, nwhite wrote:
I have been finding that 'store' is so convenient to use when
dealing with DOM centric scripts. It makes it extremely simple to
store data on an element without having to setup array indexes or
hashes. However I see a potential pitfall with this approach. One of
the great things about Mootools is its ability to keep the namespace
clean with the use of classes. However, over use of 'store' could
result in namespace collision.
When writing classes is it best to avoid the use of store? If one
does use it in there classes should it be named spaced with a class
prefix?
Thoughts?
--
Jan - MooTools comitter
twitter/blog: http://kassens.net