Re: Subject: Issue 11 and Issue 12. Message 7 Using #deepCopy, I have trouble understanding

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Re: Subject: Issue 11 and Issue 12. Message 7 Using #deepCopy, I have trouble understanding

Intrader Intrader

On 5/5/2011 2:37 AM, intrader wrote:
 > > I am now thinking of handing the editor a deep copy of the contact
to be
 > > edited, and have the #onAnswer as above.  In the #ifTrue path I would
 > > take all the instance variables of a contact and store them in the
 > > instance variables of the parameter to #editContact
 > That is a good idea, we use a similar pattern in all our UI development
 > (whether it is Seaside or VW clients), however we don't hand over a deep
 > copy.

 > Particularly in VW clients there are system ivars that manage
 > dependencies between the domain class (Contract) and the UI elements.
 > These ivars don't want to be altered during the lifetime of the UI, so
 > instead of handing over copies in editor UIs we would instantiate a
 > Contract *only once* in the UI.
 > ...

Thanks so much for these thoughts and guidance. An earlier system I
implemented in .net used the pattern.

In an earlier post in respoinse to Ladislav, I simply used #copy, but I
think that #deepCopy is better is many instances.


_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc