I just added an example that shows how you could implement a
simple drag handler with Signal:
http://trac.mochikit.com/browser/mochikit/trunk/examples/draggable
Any comments? How can it be better?
Looks great! The only comment I have is that normally I will use
the exported names in the examples rather than the fully-qualified
names. In the majority of use cases (well, mine anyway) the
developer has enough control to assume that these symbols aren't
randomly overwritten by something else, and the code feels a lot
simpler without fully qualified names.
Now that an example is in place, what are your thoughts on the
general stability/completeness of Signal? Can we wrap this up for
release this weekend perhaps?
Great, I exported now. I'm happy with all of the DOM stuff, but I'm
actually not a big user of the slots mechanism. I'm just starting to
look at it now, and one thing I don't like is the requirement to
registerSignals before connecting them. Dojo doesn't require this,
but I haven't used this part of Signal enough to develop a strong
feeling for or against registerSignals. I think some of the variable
naming need to be cleaned up as well -- aren't slots, observers, and
listeners the same thing?
I'm working on a button example that should make use of other parts
of the Signal API. It'll be a bit more complicated than draggable,
but should show off some nice features.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
MochiKit group.
To post to this group, send email to mochikit@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/mochikit
-~--~~~~--~~--~--~---
