At 04:02 PM 3/8/2006 -0800, Alec Flett wrote:
John -
How do you handle when who/about/date are different types? For instance, I
think 'who' on some objects is a refList of EmailAddresses but on other
objects (Note?) it is a EmailAddress object.. or I could imagine it
eventually being a string too.
One solution I could imagine is putting separate, localized 'who'
attributes on a per-Kind basis (so that e-mail addresses could have its
own 'who' that is a refList of EmailAddresses and Notes could have just a
single EmailAddress object.)
But if we're talking about a scheme like this, it seems like it would make
sense to just bake this into the schema layer, rather than implement
onValueChanged on each of the respective PIM Kinds. Maybe pje can shed
some light here?
If I understand correctly, the idea here is to make them *fixed* types:
strings for who and about, and some date-time type for the date. The
onValueChanged is there to handle the necessary subclass-specific conversion.
To put it succinctly, the who/about/date attributes would part of an
interface defined by osaf.pim, which content items are required to implement.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
