On Thu, Apr 9, 2009 at 17:55, Greg Brown <[email protected]> wrote:
>
>>(*) The Component#Attributes mechanism looks fragile.
>>What if I want to extend TabPane and add my own attributes?
>>It seems like this mechanism could be less fragile and more type-safe by
>>hand-coding Maps into the relevant sub-classes.
>
> I wouldn't characterize it as fragile - but it isn't all that pretty, I'll 
> give you that. I'll have to give some thought to the subclassing question.
>
>

Now that I look at it again, the attributes mechanism and the new
userData-map stuff are pretty similar.
It looks like they could perhaps be collapsed into one mechanism.

Reply via email to