> 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.
Ralf, if you still feel strongly about this I suggest that you raise a
bug report about it.