Re: Our story for re-using content types

Martin Aspeli wrote:
> Hi guys,
> 
> This has been bugging me for a while, so I thought I'd take it up
> face-to-face. Re-using content types that are part of more complex
> relationships can be fairly difficult. I'd like to discuss what options we
> have, and how to approach this in the future.´


There is a common and logical pattern that isn't very well supported in 
Zope. Example:

Often you need to add contact info to a members home folder. So either 
you make a new member folder with its own schema. Or you add a contact 
object in you home folder.

The problem is that the it can get any id. Which is hard to script well. 
Or you can give it a special id (which is hard in AT). But it can still 
be deleted/renamed. Unless you protect the id.

But that means that the  member folder has to know about the contact 
object. Again we are back at a special content type.

I think what is needed, is some way to describe a containment 
relationship/hierachy. That doesn't touch the objects themself, but 
shows up as new content types.

So you can define that the "myMemberfolder" has "Folder" as top level 
folder and some kind of defined hierachy of subobjects with specific ids.

Another problem is that this hierachy should not show up in the normal 
navigation view, as users would not be able to delete them. They should 
be more like "actions"

-- 

hilsen/regards Max M, Denmark

http://www.mxm.dk/
IT's Mad Science

Phone:  +45 66 11 84 94
Mobile: +45 29 93 42 96



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642