> The new properties are not yet ready. The development of them
> continue next week. Following our current plan they will be part of
> 0.7. The current property are not the fastest solution in some cases.
> The new system will try to enhance the performance of the property by
> a great extend. (Mainly runtime performance, e.g. value set, get,
> validation, etc.)
I had wondered about another optimisation of the size of property code. There
is presently the "set" method that takes a dict of properties and values, but
the string optimiser can't touch the keys of the dict.
How about methods "s" and "g" which take, as first parameter, the name of the
property as a string? Then the string optimiser can kick in.
We could automatically translate from the long form e.g. setReadOnly(false) to
s("readOnly", false) and then to s($[123], false).
Hugh
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
