On 10/12/06, Chris <[EMAIL PROTECTED]> wrote: > > Bob Ippolito wrote: > > Your script runs before the body is parsed, so the element doesn't > > exist yet. You need to make sure it executes *after* the document is > > parsed. Every single example uses addLoadEvent or connect(window, > > 'onload', ...) to do this. > > Ahhh I see. > > > No, but there's the wiki. Feel free to start a FAQ: > > http://trac.mochikit.com/ > > Great thanks. > > > > 4. Why don't I need to access the functions with > > > MochiKit.Signal.connect()? What if I create my own function later that > > > overlaps a MochiKit function I am not aware of? > > > > I don't understand this question. > > I guess I'm talking about namespaces. What if I include another library > (e.g. one that does some kind of visual effect I want) and it has a > function called 'connect' also. Won't there be a conflict?
Yes, that's why there's also MochiKit.Signal.connect available for when you do have such a problem. The internals of MochiKit use fully qualified names internally. By default, the public API is exported globally for convenience. It's easier to write code when you don't have to type a bunch of redundant junk over and over. -bob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MochiKit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~----------~----~----~----~------~----~------~--~---
