Hello Huseyin, thank you for your interest in the contribution, I am really happy someone is actually using it.
The problem with the shortcut commands is that they have to be hardcoded into the 'dialog' namspace object. There is no way (that I know of) that when loading a class file, some default action is triggered that would allow to add static properties to the namespace object. This would allow to add the shortcut methods 'pluggable', i.e., add them on a class basis rather than batch-create them, which creates a maintenance problem. One can add arbitrary code to the class file after the class definition, but this code will be thrown out when the "build" version is compiled. How it works in the trunk is that you have to call the static method dialog.Dialog.init() to make the shortcut commands available. I wish there was another way - maybe someone has an idea. Thanks, Christian -- View this message in context: http://n2.nabble.com/predefined-modal-dialogs-tp4750559p4755310.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
