On Wed, Dec 16, 2009 at 15:53, Jean-Noël Rivasseau <[email protected]>wrote:
> What do you mean, redesign (more exactly, where ? :) > I meant that you would need to either redesign those classes that have private variables you need access to, or arrange to not need access to privates. Privates are just that -- private -- and are not intended to be futzed with by any code outside of the class in which they are used. (It would be nice, though, if mixins could be written to have access to them.) > What I will do is try to come up with an acceptable patch to the original > class that will allow me to do exactly what I want. I hope you guys can > apply it once reviewed. > If the privates are in a core qooxdoo class and you can justify a need to have them available to subclasses, it would be a backward-compatible change to make them available (probably via getters and setters). Yes, please show what you need access to and explain why. Cheers, Derrell
------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
