> The problem with a whitelist is that one should be able to use a monitor to > determine what events are being dispatched. In other words, we don't always > know which events are interesting ahead of time. To set up the whitelist, > you > have to already know, so that pretty much defeats that particular purpose. > It > should be possible to get notified of *all* events (even if that incurs some > overhead). If the overhead is significant, the monitoring should be enabled > by a variant, so apps that don't require the monitoring can run at full > speed. >
I can't imagine what I would do with an event I didn't know about in the first place. This kind of thing is sometimes useful for logging or debugging situations, but I just don't see a general need for it. Maybe I'm missing something. Bob ------------------------------------------------------------------------- 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
