actually this has been the case from both "sides". we tell you we dont like your suggestions, and you tell us you dont like ours. so lets be fair.
I don't know. I have the feeling that I suggested different options. A separate component would be the best solution imo, as in that case it would be a WebComponent rather then a WebMarkupContainer (like I said in my 3rd reply). But then you'd have a whole bunch of them, which Johan doesn't like to much. Just trying to see whether we could find a solution that would satisfy us all.
(I can live with the labels > personally, but having to answer this question regularly is a good > indication to me there is room for improvement). i think this has a lot more to do with people not being used to working with component frameworks then anything else. 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.
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. Eelco
