On Thu, Jan 12, 2012 at 13:23, thron7 <[email protected]> wrote:
> The problem is that any form of mixin handling is done at runtime, while
> private optimization happens at compile time.
>
> You might want to open an enhancement request to turn these private
> methods in protected methods, so it would be easier to subclass and
> overwrite (You might still have to provide the entire _createRequest
> method, but would then be able to just use the other internal functions
> called from there).
I've had similar problems with mixins in the past. There are appropriate
times to patch a function that uses privates, and the only way to
accomplish that at present is to copy in large portions of the class being
patched.
One possible feature enhancement would be command line options to the
generator, or a new type of entry in an application's config.json file,
that specify specific privates in particular classes which should not be
optimized. That doesn't sound like a trivial piece of work, but may be a
good alternative.
Derrell
------------------------------------------------------------------------------
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
