[Dev] parcel modularity... not

[Kapil Thangavelu]

hi folks,

i've been experimenting with not loading some of the optional parcels
(zaoboa, stockquote, and demo). however my experiments revealed that
parcels are intimately tied to each other, for example the
view/main/parcel.xml explicitly refers to every parcel present in the
ui, such that disabling the load of say the stockticker parcel, still
causes chandler to barf while parsing the main/parcel.xml due to the
explicit ref, ditto for location.xml. 

i guess i'm wondering if its a design goal for parcels to be modular
units, and if so is it just a bug that things like views/main is
building up a global views as opposed to setting them up and letting the
respective parcels fill them. 

also its not clear if parcels are intended to be discrete units, why the
core parcels are split into many subparcels scattered throughout the
parcel hierarchy.

regarding the issues of loading and unloading parcels i brought up on
irc earlier today, i think the parcel load/unload issue and
corresponding repo items question, is better defined by a different
notion, namely parcel lifecycles, and that currently there is only one
state for a parcel in the application, namely loaded but it would be
nice to incorporate active and inactive as a parcel might dealing with
aribtrary resources outside of content items in the repository.. for
example shutting down a webserver, or deactivating zaobao

cheers,

-- 
Kapil Thangavelu <hazmat at objectrealms.net>       Vision Implemented
objectrealms.net <http://www.objectrealms.net>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.osafoundation.org/pipermail/dev/attachments/20040826/e9a07f99/attachment.bin