On Monday, May 5, 2003, at 06:10 PM, Frank Sergeant wrote:
> think a transformer is perfectly appropriate, especially if you
> remember the 'P' in 'PLM' stands for "Pluggable".  I would prefer that
> the domain object (a Patient, a Customer, a Class, etc.) not need to
> know very much about how it is to be displayed and, especially, I would
> not want it to have a dependency on Morphic.
>
Ditto! I guess I wasn't thinking / typing clearly enough. I'm all for the 
MVC/MVP approach but I guess it'd help if we were all a little clearer 
about what we mean sometimes. Terminology has a lot to answer for. It 
depends what you mean by domain object, demarcation and all that.

In the strict MV* world the model is not supposed to know JS about the 
views it may appear in so it would be the responsibility of the presenter/
controller to say that 'hmmm, in this context we need a foo to display as 
a bitmap' and then construct the relevant transformer....oh hell...it's 
happened...in plain text...I've ended up seeing the other guys point of 
view and agreeing with it....good job I never took up law!!!

Ok then, a transformer it is!

What do I care.... *8-)

Sean Charles