On 28/11/2010 09:22, nagylzs wrote: > In qooxdoo, I only see one way to do it: let the login window call back > another method (or event handler) in the main application. But I do not like > the idea because I'll be using hundreds of modal windows. Maybe I missed > something. > Hi,
What you could, and probably should do in this case is create an abstract class/mixin which listens to modality events and blocks what should be blocked upon reception. That way, your code will be manageable even with hundreds of modal windows. :) Good luck with qooxdoo. As Stefan pointed out, you learn to like it when you begin to understand the flexibility this event-based programming style gives you. Cheers, -- Joffrey Fuhrer NOVLOG Intern ------------------------------------------------------------------------------ Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
