On 07/09/2010 10:22 AM, panyasan wrote: > > 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?
Sounds good to me. I think we've both been tricked into believing it works without the #use if you just add a call like 'dialog.alert()'. But thinking about it this can't work, and I tested it on a file where I also had used 'new dialog.Alert()' before, and then forgot to re-run the generator. So the code executed dialog.alert() faithfully, but the dependencies were still in from the 'new dialog.Alert()' code :-(. Re-running generate.py source showed Nick's problem. I would still appreciate a bug in this matter, as I feel the dependency handling of name space symbols should be revisited. Currently, top-level name space symbols are auto-#ignore'd, and the tendency is to extend this to sub name spaces too. But I'm not so sure about this any more... T. ------------------------------------------------------------------------------ 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
