set() is a wrapper around the setPropName functions. This means that is
is slower by nature - but I don't know directly how much slower. The
translation from the lowercase propertyName eg. width => setWidth could
be the major performance impact of the setter.
Sebastian
Dietrich Streifert schrieb:
> Hello List,
>
> I have a big widget stack with more than 120 input widgets (textfields,
> radiobuttons,comboboxes,checkboxes).
>
> Currently all properties which can not be set at instatiation time are
> set using the set method:
>
>
> instance1.set({top:10,left:10,width:100,height:20,prop1:"val1",prop2:"val2"});
>
> Which can also be done by calling
>
> instance1.setTop(19);
> instance1.setLeft(10);
> instance1.setWidth(100);
> instance1.setHeight(20);
> instance1.setProp1("val1");
> instance1.setProp2("val2");
>
> Is there a difference in performance of using the first or the second
> method?
>
> Thank you for your comments.
>
> Best regards.
>
-------------------------------------------------------------------------
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
