Ted Leung wrote:
For 0.7 I am taking over the Domain model. Sheila, Mimi and I
talked a bit about known work items related to the domain model. The
notes of our conversation are at <http://wiki.osafoundation.org/bin/
view/Journal/DomainModelIssues>.
Please let me know if you have other domain model issues that are not
on this list.
Ted,
I think there are bugs for a few of these, which are all issues for how
we expect developers to add Kinds to Chandler:
- We don't have a strategy for how developers will participate in
mixing-in with pim kinds. (the wiki page talks about mentions supporting
use cases - maybe we need some for developer uses of the domain model?)
- The notion of supporting different types of the "body" attribute isn't
really workable; Note's "body" pretty much needs to win (and be text)
for all pim types (or note bodies will appear and disappear with stamping)
- Someday mail will be a tenet, and when it becomes one, Implementing "I
want to mail this" by adding MailMessageMixin to the item's superkinds
is too limiting: if the thing you're sending IS the mail message, you
can only mail one item this way, and you can only mail it once (unless
we want to add lots more mechanism to track multiple sendings of an
item). (I bring this up now because we're talking about how invitations
should work.)
...Bryan
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev