[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [wsrp-interfaces] copyPortlet - additional use case
Say the portlet (A) in the page designer use case to be cloned/copied has properties and values: x=1 and y=2. The new copy/clone (B) would initially have the same property values for simple non-computed properties, but what about after:
A.x = 3;
B.y = 4;
What is the expected resultant value of A.y? So far, we have made no assumptions here (the write to A.x could also modify A.y if y was computed from x), but I would expect a copy/clone across registrations to help preserve A.y == 2. If we named the operation "copy" then I would be further encouraged to expect no post copy relationship between A and B, even if the two registration handles happen to reference the same registration, and this would, I think, be expected by Rich's use case, but not our necessarily our 1.0 clonePorlet.
Do we agree that there are such use cases where breaking any relationships between a portlet and its copies/clones is a requirement? If so, then a new copyPortlet operation makes sense (rather than overloading clonePortlet). Computed properties can still take on any value they like, but we would be encouraging producer/portlet property relationships to respect registrations.
From: Goldstein, Scott
If I understand correctly, the only difference between clone and copy is the relevance of the registration. Therefore, I would say that this use case is applicable for both clone and copy. The clone() method, I believe, currently supports this use case due to the requirement of copying the current state from the original portlet to the clone being created. Is this not true for copy() as well?
Could be applicable, I agree. In selecting the use case, focused on requiring two registrations and involving an end user.