Re: Appropriate use of Property()

2008-01-30 Thread Bruno Desthuilliers
[EMAIL PROTECTED] a écrit : > Property() can be used to rid ourselves of the extra effort of using > two different methods (getAttrib() setAttrib()) for access of an > attribute without giving direct access to the attribute, NB : properties are for computed attributes, not to "avoid giving direct

Re: Appropriate use of Property()

2008-01-30 Thread Asun Friere
On Jan 30, 5:03 pm, Gabriel Genellina <[EMAIL PROTECTED]> wrote: > On 29 ene, 23:17, [EMAIL PROTECTED] wrote: > > > Property() can be used to rid ourselves of the extra effort of using > > two different methods (getAttrib() setAttrib()) for access of an > > attribute without giving direct access to

Re: Appropriate use of Property()

2008-01-29 Thread Gabriel Genellina
On 29 ene, 23:17, [EMAIL PROTECTED] wrote: > Property() can be used to rid ourselves of the extra effort of using > two different methods (getAttrib() setAttrib()) for access of an > attribute without giving direct access to the attribute, thus making > it more elegant. So, the outsider using my m

Appropriate use of Property()

2008-01-29 Thread noemailplease0001
Property() can be used to rid ourselves of the extra effort of using two different methods (getAttrib() setAttrib()) for access of an attribute without giving direct access to the attribute, thus making it more elegant. So, the outsider using my module accesses the attribute with the syntax 'Object