-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Colin Mollenhour wrote: > For example, override the insertion function with one that checks a > counter before calling Element.update manually: Nifty. Continuing the idea, let's do even more: switch "counter" to "updaters", an array (or maybe hash?) containing pending updaters for that element. This way they could be manipulated easily, both internally (by Ajax.Updater methods) and externally (by any picky user) :)
>> IMHO, there's no need for such an "override" parameter. Better yet, >> simply twist Ajax.Updater to behave like this. > I'm not so sure.. Say your insertion is something besides Element.update. > If it is Insertion.Bottom then you may not want any insertions > overridden. That's exactly what I was proposing (it there's an "insertion" provided, then don't bother about replacing old requests). But I can see where you're going... > Rather than having Prototype test which insertion you're using, the > override parameter may be a simpler and cleaner solution. Let the > programmer decide! Good enough, so an "override" with "false" as default would be better. :)) - -- Marius Feraru -----BEGIN PGP SIGNATURE----- iD8DBQFFwhZttZHp/AYZiNkRArLvAKDehUV0o0Or4ifimG58PRfKwT7MIwCfYXiy nVEMkZq3UdZlK6XSWuC2KuU= =gpah -----END PGP SIGNATURE----- --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
