Before I release the next stable version of the dialog package, I plan to split up the wholesale definitions of the shortcuts in the defer key of dialog.Dialog and move them to the defer keys of the respective dialog widgets. I think that this is a cleaner way and allows a more "plug-in"-like behavior, where the dialog.Dialog widget does not need to know about the implementation of individual widgets that derive from it.
This will mean, however, that you will have to explicitly declare a compiler hint, for example #use(dialog.Alert), if you want to use dialog.alert(), or batch include all of them by declaring #use(dialog.*). I think that makes most sense. Any opinions on that? C. -- View this message in context: http://qooxdoo.678.n2.nabble.com/Cannot-get-the-Dialog-contrib-or-any-libraries-to-load-tp5266735p5273449.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
