If you start using 'internal' identifiers in your events, your sandbox is leaking. Why go to the trouble of hiding the object types and decoupling everything if you're just going to couple it up again by exposing implementation details in string identifiers?
L. On 2011-08-22, at 9:27 AM, Xavier MONTILLET wrote: > Because he uses sandboxing. > > On Mon, Aug 22, 2011 at 2:49 PM, Dmitry Pashkevich <[email protected]> wrote: >> I may have missed the point but I don't think that event name should contain >> the name of the module or class that fires them. Because when you listen to >> the event you access the object that fires it anyway: >> myButton.listenEvent('toggle', function() {...}); >> myDndManager.listenEvent('drop', function() {...}); >> >> So why should I name events like 'DndManager->drop'? Even if you need to >> dynamically determine the object that fired the event you can always include >> the object itself in event parameters: >> this.fireEvent('drop', this, data) >> >> Also, are you trying to implement the pubsub model or the 'regular' event >> model where one object directly subscribes to events of another object? >> >> -- >> To view archived discussions from the original JSMentors Mailman list: >> http://www.mail-archive.com/[email protected]/ >> >> To search via a non-Google archive, visit here: >> http://www.mail-archive.com/[email protected]/ >> >> To unsubscribe from this group, send email to >> [email protected] >> > > -- > To view archived discussions from the original JSMentors Mailman list: > http://www.mail-archive.com/[email protected]/ > > To search via a non-Google archive, visit here: > http://www.mail-archive.com/[email protected]/ > > To unsubscribe from this group, send email to > [email protected] -- Laurie Harper http://laurie.holoweb.net/ -- To view archived discussions from the original JSMentors Mailman list: http://www.mail-archive.com/[email protected]/ To search via a non-Google archive, visit here: http://www.mail-archive.com/[email protected]/ To unsubscribe from this group, send email to [email protected]
