On 10/25/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> > we have a link component - it serves as a container for other components. > if you want to display something inside that component you have to add > another component to do that - eg a label. Sometimes little things make a big difference. I only have to get back to SimpleAttributeModifier vs AttributeModifier to 'prove' that, as that only saved what, the creation of a model.
and i will take the fall for that one. in retrospect i shouldve put it in extensions. maybe i should fix that mistake in 2.0? but SimpleAM is a bit different story. another thing that bugged me about AttributeModifier was that boolean in the constructor which i could never remember which way it worked - in 2.0 we can make it an enum. so SimpleAM was a bit more then just convinience - it really was a simpler version of the full attributemodifier. it also lacks a lot of the methods that the full version has. its like dataview - you can argue that is a convinience because you can do the same with a listview - but its just not the case.
i am for adding convinience subclasses for this. yes not as pretty but it is > how component oriented frameworks work. Yeah, that's probably the best option then.
this would be my vote. -Igor Eelco
