Subject: Special session -- IRC Office Hour - Part II, Wednesday, 14 September 2005, 11AM PDT - msg#00080

Previous Message by Date: (click to view message preview)

README: parcel.xml is dead; update personal/certs parcels!

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

Next Message by Date: click to view message preview

Re: Special session -- IRC Office Hour - Part II, Wednesday, 14 September 2005, 11AM PDT

At 04:15 PM 9/13/2005 -0700, Pieter Hartsook wrote: * Phillip Eby is going to give Part II of a clinic on performance profiling for Chandler. Phillip will walk everyone through running profiles (for a test and from the UI), and basic Stats object navigation. Actually, the portions of this that weren't done last week are described here: http://lists.osafoundation.org/pipermail/dev/2005-September/003728.html This week's session will be to do hands-on analysis of your favorite performance use cases. We recommend uploading your Events.prof or profile.dat files as attachments to Bugzilla tickets, so that we can all download them and follow along. We won't have time to do from-scratch analysis of your use cases, so come prepared with specific questions/problems that you'd like to delve into. Thanks. _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Dev" mailing list http://lists.osafoundation.org/mailman/listinfo/dev

Previous Message by Thread: click to view message preview

README: parcel.xml is dead; update personal/certs parcels!

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

Next Message by Thread: click to view message preview

Re: Special session -- IRC Office Hour - Part II, Wednesday, 14 September 2005, 11AM PDT

At 04:15 PM 9/13/2005 -0700, Pieter Hartsook wrote: * Phillip Eby is going to give Part II of a clinic on performance profiling for Chandler. Phillip will walk everyone through running profiles (for a test and from the UI), and basic Stats object navigation. Actually, the portions of this that weren't done last week are described here: http://lists.osafoundation.org/pipermail/dev/2005-September/003728.html This week's session will be to do hands-on analysis of your favorite performance use cases. We recommend uploading your Events.prof or profile.dat files as attachments to Bugzilla tickets, so that we can all download them and follow along. We won't have time to do from-scratch analysis of your use cases, so come prepared with specific questions/problems that you'd like to delve into. Thanks. _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Dev" mailing list http://lists.osafoundation.org/mailman/listinfo/dev