Sebastian Werner <[EMAIL PROTECTED]> writes: > I don't like the solution to be integrated in qx.core.Target. I would > like it better to add specific events to a special event router which > then informs registered objects about any of these events. This is a > lot cleaner than exclude tables and a deep integration in > core.Target. The overhead of many events would be to dramatic. I can > imagine of something like a widget monitor which reacts on all > widgets relevant stuff and for example a IO monitor which monitors > all IO related things. > > What do you think?
Hi Sebastian, That concept sounds fine. I'm not sure I follow where you'd add it, though, if not in Target. If one wants to monitor all, or some very large subset of events, where else could you put it that has access to the information? I expect that in the implementation I checked in last night, the overhead is quite small since it effects only events with listeners if the variant isn't enabled. I am concerned about the overhead when the variant _is_ enabled. I'd definitely like to hear more about how you would implement the special event router. Sounds quite interesting! Cheers, Derrell ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
