>
>
>
>  This may cause a lot of pain !
>>
>
> I'm not following you . . .
>
>
I just meant this won't be easy to manipulate generated DOM with java, but
if it's the only way, I can deal with that.


>
>  So, can I conclude that the use of @Property wouldn't be recommended
>> within components ? Because (even with mixins) you may want to have access
>> to some properties of the component...
>>
>
> I'd say that you shouldn't use @Property when you think it's interesting to
> provide access to other classes.
>

Got it.

Once more, thanks for your help.

>
>

Reply via email to