The mixin constructor is called _after_ the normal constructor rather than before. This is the wrong default.
Why? Because the mixin can make no assumptions about the class it's mixed in.. so it won't be calling or setting properties other than its own. But the class using the mixin knows its using the mixin. It wants to use the mixin in the contructor, but it can't. This isn't easily overcome with using inheritance when the ordinary qooxdoo classes, even those not taking any constructor arguments are wrongfully modelled as classes rather than mixins. Perhaps i'm missing something here. Greetings, Ralf Nieuwenhuijsen ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
