Thanks Igor - that's the approach that I would automatically take. My question was really related to explaining to developers from an MVC background what the process is for getting data from "somewhere" to the view. Nested models as a data tranformation pipeline is the mental model I was going to use. I just need to fit "behaviours as component mutators" in there somewhere and I'll be set!
----- Original Message ----- From: "Igor Vaynberg" <[email protected]> To: [email protected] Sent: Wednesday, 4 August, 2010 9:29:34 PM Subject: Re: Model object string manipulation for reusable situations, or even one off, you can write a simple decorator model -igor On Wed, Aug 4, 2010 at 1:27 PM, Iain Reddick <[email protected]> wrote: > To elaborate a bit - I'm talking about "one off" situations and also > re-usable solutions, such as the aforementioned "to upper" and "to > lower" cases. > > ----- Original Message ----- > From: "Iain Reddick" <[email protected]> > To: [email protected] > Sent: Wednesday, 4 August, 2010 9:19:46 PM > Subject: Model object string manipulation > > What's the cleanest way of doing string manipulation with a component > that uses a String as a model (e.g. a Label). I'm thinking of > mutations such as to uppercase and to lowercase, etc. > > An obvious place is to do it in the model, but I'm interested to hear > what other developer's approaches are. Is there a nicer way of doing > this - via a behaviour for instance? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
