Morgen migrated zaobao, another good example:
http://viewcvs.osafoundation.org/chandler?view=rev&rev=5639
Cheers,
Katie
Katie Capps Parlante wrote:
Hi all,
If you haven't been paying careful attention, now is the time to take a
look at Phillip's schema api, before we go ahead and do the full migration.
The original proposal (in particular, check out "How it will work" and
"API Quick Reference"):
http://lists.osafoundation.org/pipermail/dev/2005-April/002690.html
The api is implemented at application/schema.py. ContentItem and
ItemCollection are already using the api, so you can look at those
classes as examples. Bug#3215 has a patch with another example (calendar
content model), and Ted sent the diffs to the dev list for the "Note" Kind.
Note that we are migrating the data definition of Kinds, Attributes, and
Clouds to the python classes associated with the Kinds. Parcel xml will
continue to be supported for creating instances of Items. Also note that
both the parcel loader and the schema api underneath the hood are using
the same repository api to create items. The schema api does enforce
some conventions/correctness issues (e.g. 1:1 mapping between Kinds and
classes).
Its our goal to finish the migration by the next milestone. For the most
part, the dev platform team will handle the migration, but you need to
be aware of some of the issues during the transition. Phillip will send
more details about the migration.
I for one am looking forward to the change, as this will set us up
nicely to make some other changes (like flattening the package/parcel
hierarchy, cleaning up some tangled dependencies, etc.)
Cheers,
Katie
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev