So just to be extra clear about this: this module explicitly requires you to call signal(...) in order to have the event dispatched?
Why? This is a significant backslide in end-user ease-of-use from either the Dojo AOP event system or the netWindows sigslot system, and I'm having a hard time seeing what gain there is to requiring the developer to do more work. Regards On Monday 19 December 2005 4:46 pm, Jonathan Gardner wrote: > On Friday 16 December 2005 18:45, Bob Ippolito wrote: > > If you implement something that doesn't suck with docs and tests, > > and are willing to contribute it under the same license terms of > > MochiKit, then I'll take it. > > I've attached a diff (made from 'svn diff') of my stuff. I don't know > how google groups will handle it... > > I don't know if the docs are formatted correctly. My experience with > ReST began today. I couldn't build the docs because I couldn't get a > good version of docutils. > > I'm going to start using this right away so any bugs that testing > didn't uncover should be revealed shortly. > > Please rip this to pieces and I'll try to incorporate suggestions > ASAP. -- Alex Russell [EMAIL PROTECTED] BE03 E88D EABB 2116 CC49 8259 CF78 E242 59C3 9723 [EMAIL PROTECTED] F687 1964 1EF6 453E 9BD0 5148 A15D 1D43 AB92 9A46
