Fabian Jakobs <[EMAIL PROTECTED]> writes:

> You only have to list every event of the super class in a mixed qooxdoo
> 0.6/0.7 environment. If addEventListener is called on a new style class if
> will search the inheritence hirarchy for a definition a an event using the
> "events" key. The benefits are:
>
> 1. every event must be defined in the class the event is introduced
> 2. if the developer misspelles the event name, this will be detected and an
> error message just like above will be displayed

Thanks.  I'm working with the bleeding-edge, and, true to form, the blood is
gushing forth.  The triage team just put a red tag on my toe. :-)

Derrell

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to