[Zope-CMF] Compound elements status

[Florent Guillaume]

Max M  <maxm@mxm.dk> wrote:
> Florent Guillaume wrote:
> >Well then it's not a content-management system if you have to have
> >specialized types for subelements, or if you store the subelement in a
> >list instead of a folderish object.
> 
> Yes it is. The "Compund Article" is _one_ element in a content 
> management subsystem. One that that is needed because editing through 
> the web interface sucks.
> 
> If you want to put arbitrary element into the compund object you are 
> really just making a specialized Folder object.

I want to put any Type in the compound object, provided they can obey
certain rules. This means that, in the way I envision things,
subelements could potentially be complete full class Content. Obviously
we have different goals here.

> >I think a worthwile goal, on the contrary, would be to have elements
> >that are as CMFish as possible. The difficult part is of course to make
> >it play well with catalogging, security and workflows.
> 
> I don't understand what you mean. In which regards CMF'ish ??

See above: being real Portal Types, potentially being subject to
workflows, catalogging, etc.


Florent

-- 
Florent Guillaume, Nuxeo (Paris, France)
+33 1 40 33 79 10  http://nuxeo.com  mailto:fg@nuxeo.com