[Zope3-dev] Re: 'Folders', 'Sites' and customising Y's

[Chris Withers]

Jim Fulton wrote:
>>
>> Y : Plugin Folder
> 
> To me, "folder" is like "workspace" in that it implies that
> you can modify things in it. 

I have plenty of read-only file systems on both windows and unix. These are all 
'folders' so  idon't really agree...

>> X : Software Folder or Workspace Folder (I'm neutral as to which one 
>> is better)
> 
> Well, if we go for "folder" I wouldn't use "workspace" as a modifier,
> as that's really redundant.

How so? a workspace folder is for working in, a plugin folder can be moved 
around and installed elsewhere but not modified...

>> ...and Content Folder for fodlers which store real content.
> 
> Right.

:-)

> A "site" is an ordinary folder that contains a site manager. The site 
> manager
> will contain X's, Y's, and will manage service configurations.  The site
> manager is not one of the containing folders's items, because when you 
> enter
> the site manager, you leave content space.

cool, I think :-)

>> Yes, but this fails to cover the crucial point, IMHO. Someone 
>> customises a Y (how will this work? I'm thinking the 'custom' skin 
>> layer in CMF...) 
> 
> The normal way to customize a Y will be to ininstall (deactivate) some of
> it's configurations and configure components from other Xs and Ys.  When 
> creating
> these other components, they may copy selected components from the Y 
> they are
> customizing.

Hmmm... how granular is 'component'? Down to a single page template or script?

> 1. They get a report of the configuration changes the new version will 
> and won't
>    make.
> 
> 2. They get a report of the components that changed in the update. They can
>    optionally choose to get diffs of components that have changed.

Cool :-)

Chris