Hi Lukas,
Thanks for the info. It is indeed more complex than it seems.
Would it help if a description has a unique name within a MAContainer?
So a container would have an ordered dictionary of children instead of
an ordered collection.
Jan.
On Mon, Sep 19, 2011 at 7:24 AM, Lukas Renggli <
renggli@gmail.com
<mailto:
renggli@gmail.com>> wrote:
Uniquely identifying descriptions is a much harder problem than it
looks like: descriptions evolve, change, get extended and refactored.
At ESUG in 2006 there was a longer discussion about this problem: The
question was how to identify descriptions that were dynamically
created and edited by users in different images and stored to an OODB.
The only reasonable solution was to use UUIDs.
It is easy to programmatically add UUIDs, but ideally they should also
cover the #description* methods.
Lukas
On 19 September 2011 07:02, Yanni Chiu <
yanni@rogers.com
<mailto:
yanni@rogers.com>> wrote:
> On 18/09/11 8:05 AM, Jan van de Sandt wrote:
>>
>> I don't like these options for identifying a child description
because
>> they depend on properties that are used for other things. I am
thinking
>> about adding an some kind of 'name' property to the description
>> hierarchy. I am curious how others have handled this issue.
>
> I use both methods, and don't like either method.
>
> In some cases, I had to use the label. IIRC, it was because it was a
> chain'ed accessor.
>
> ______________________________
_________________
> Magritte, Pier and Related Tools ...
>
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>
--
Lukas Renggli