Korhonen, Kalle wrote:
For Grant.. Yeah, the component would render either an input component or an output component, e.g. editableText would render either inputText or outputText.
Kalle
This is the opposite of what Martin said:
Kalle's suggestion would be leading to a whole new bunch of components - still there would be one fixed underlying component.
I would have to say that I would be very much against any component that "mutates" into something else and can not be manipulated consistently through binding. Unless someone can assure me that this will not be the case, I'm veering in the direction of a negative vote on both suggestions.
Having said that, I think Sean's suggestion for getting the code into the sandbox is a good one. That would enable me to test the underlying component's consistency for myself.
