I added another convenience method to the snipped which constructs a form for quick data input.
http://qooxdoo.org/documentation/0.7/snippets/asynchronous_user_interaction But Sebastian is right, a class like this is hard to maintain, this should be split in separate classes. A mixin could provide easy access to the dialogs via methods. Volunteers? (Depending on whether people acutally need these features) C. Christian Boulanger schrieb: > Yes, a dialogue package (qx.ui.dialog ?) with different kind of > > (self-disposing) widgets would certainly be very helpful. However, I am > already off to other things, so maybe someone else likes to pick up here... > > Christian > > Sebastian Werner schrieb: > >> Good idea. However I would prefer a static class with these method or >> even better: Write a class for every method (inform, alert, confirm, >> ...) you have created. Every class extends qx.ui.window.Window (or >> create a basic Dialog class for all stuff currently in _createWindow). >> >> Just my 2 cents. >> >> Sebastian >> >> >> >> blattgold.cb schrieb: >> >>> Hello, >>> >>> wanted to let you know about a new snippet: >>> >>> Asynchronous (Non-Blocking) User Interaction >>> >>> JavaScript’s commands to interact with the user (alert, confirm, >>> prompt) are extremely limited and they have a very nasty side-effect: >>> they block the UI and all javascript processes, such as redrawing the >>> layout, rpc requests, etc. >>> >>> Here is a mixin for qx.application.Gui that provides the following >>> methods: >>> >>> * >>> inform : inform the user >>> * >>> alert : warn the user >>> * >>> confirm: let the user confirm something >>> * >>> offer : give the user a set of choices >>> * >>> prompt : let the user enter some text >>> >>> All functions are non-blocking and therefore require a callback >>> function that is called when the user has reacted to the information >>> presented. >>> >>> http://qooxdoo.org/documentation/0.7/snippets/asynchronous_user_interaction >>> >>> >>> I was hoping for a long time someone else would be writing this mixin >>> ;-) but now I needed it for my application because the >>> alert/prompt/confirm functions caused a lot of problems for timeouts >>> etc... >>> >>> Feel free to improve the code.... >>> >>> Enjoy, >>> Christian >>> >>> ------------------------------------------------------------------------- >>> >>> This SF.net email is sponsored by: Microsoft >>> Defy all challenges. Microsoft(R) Visual Studio 2008. >>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >>> _______________________________________________ >>> qooxdoo-devel mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel >>> > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
