The Documentation tries to make the point that setAttribute is the One True Way.
If there are other setters, such as for example setX and setWidth, you can use them. But such setters are not always there and really I think the main reason to use them is when you want to override or add a method to them. We do explain that you can sometimes do what you want by setting a slot directly. But then of course you get no event, and that can break thinks like constraints. So, setting slots is like overclocking a motherboard: you can get faster performance, but don't blame me if you set your machine on fire. jrs On May 16, 2006, at 9:07 PM, Henry Minsky wrote: > I'm not sure. I would think that would be transparent to the user, as > long > as they used the setAttribute API. But in reality, its faster to set a > slot > directly in some cases using "foo.bar = xxx" and I'm not sure what our > current 'best practice' is regarding this. I think anything exposed to > the > end user should be via the setAttribute/getAttribute mechanism. > (Anyone want > to chime in here?) _______________________________________________ Laszlo-dev mailing list [email protected] http://www.openlaszlo.org/mailman/listinfo/laszlo-dev
