On Tue, May 25, 2010 at 10:02 PM, Fabien Potencier <[email protected]> wrote: >> It looks like I should put my two cents: I'm with Jordi, too. Many web >> developers use JS, while not as many use Cocoa. Why adopt a model that >> is counter-intuitive to the target audience? > > I don't get the "counter-intuitive" thing? What is counter-intuitive > exactly?
To be honest, after using it for a little while I got used to it, which is also partly why I wanted to drop the matter. But I think the initial problem comes from notifyUntil mostly, that is basically a passive way of dispatching an event until someone returns false. I very much prefer the ECMA model that, with stop(Immediate)Propagation, has a much more explicit way of implementing the "until" feature. You can grep your code and find out very easily, while a return false could be trickier to find. Also I like the preventDefault feature, in some cases I think it can be really useful (i.e. if you got plugins and want to allow plugins/hooks to override default behavior completely rather than just extend), and as far as I know there is no standardized way to do it at the moment, you could of course store something on the event object. Cheers -- Jordi Boggiano @seldaek :: http://seld.be/ -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" 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/symfony-devs?hl=en
