Thank you Hugh,
but what I wanted is to avoid the overhead which is implied by using
addProperty.
The current implementation of our application uses exactly what you
supposed.
Hugh Gibson schrieb:
In my application I need to add some properties to the whole widget
hierarchie (maybe bad style, but anyway). So I do the following:
We do the same, but take a different tack:
qx.Proto = qx.ui.core.Widget.prototype
qx.OO.addProperty({name : "HTMLName", type : qx.constant.Type.STRING});
qx.Proto._modifyHTMLName = function(propValue, propOldValue, propData)
{
if (propValue) // a value given?
{
this.setHtmlAttribute("name", propValue); // set the NAME attribute - ID
doesn't work in TestComplete
}
else
{
this.removeHtmlAttribute("name"); // no value, so remove attribute
};
return true;
};
We're using the qooxdoo property system without having to hack it at all. See
here for more information:
http://qooxdoo.org/documentation/user_manual/properties#modifying_properties_at_runtime
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
--
Mit freundlichen Grüßen
Dietrich Streifert
Visionet GmbH
-------------------------------------------------------------------------
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
