Chandler is no longer using parcel.xml for anything but "personal" or
"certs" parcels. If you have such parcels, please see this page:
http://wiki.osafoundation.org/bin/view/Projects/ParcelLoading
for examples/explanation of how to set up a Python version of those
parcels. Please do this soon, as the old parcel.xml loader will soon be
removed altogether.
In addition, please note that with the departure of parcel.xml, parcels are
now only loaded if one of the following conditions is true:
1. The parcel is the one set by the '--app-parcel' command line option
(which defaults to 'osaf.app')
2. The parcel is used to create items in another parcel's
installParcel(), and that other parcel is loaded
3. The parcel is explicitly loaded using 'schema.synchronize()' in
another parcel's installParcel(), and that other parcel is loaded
4. The parcel is a top-level "plug in" parcel, like feeds, amazon,
flickr, photos, or a personal parcel. (That is, it's a parcel with no '.'
in its name.)
What this means is that if you have a parcel that's not "top-level", or
used by other parcels, it's not going to get loaded at startup. If there's
another parcel that uses it, but doesn't use it during 'installParcel()',
you should add an explicit "synchronize" call to the parcel that uses it,
so that the needed parcel will be loaded at parcel installation time,
rather than waiting until Chandler is already running to load the parcel.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
