Thanks Tobie! That is a very nice way of doing it.
Many thanks to you and the prototype team for making something, for free,
for everyone to use and putting up us (well, me). :-)
On Tue, Oct 6, 2009 at 9:57 AM, Tobie Langel wrote:
>
> Jim, Ngan.
>
> This is already possible with our current eve
Jim, Ngan.
This is already possible with our current event system using the
`document` object as broker.
Please see a basic, untested implementation here:
http://gist.github.com/203193
If you ant to discuss this in more details, please do kindly start
another thread.
Thank you.
Tobie
--~--~-
Sorry for getting off topic, but I completely agree with Jim. I'm currently
writing a complicated WYSIWYG editor and one of the annoyances I'm faced
with is the fact that only elements are able to fire events. This makes my
Models use the window.document element to fire/observe events.
On Tue, O
On Tuesday 06 October 2009 08:09:21 Tobie Langel wrote:
> Finally, Sam is working on a new API for event delegation in 1.7 /
> 2.0. If changes are to be made, they should be discussed once he's
> posted his initial implementation.
If I could suggest...
The biggest problem with events at the mome
Hi.
Please allow me to clarify the issue here.
Event#element was deprecated because of it's inconsistency with the
rest of our API (which systematically uses verbs for method names).
There were two options for renaming this method: 1) add an
Event#getElement method or 2) reuse the existing Elem
