Our story for re-using content types

Martin Aspeli <optilude...> writes:

> Let's say I have a content type Staff that holds some
basic contact details,
> and another type Project. Staff can be a member of the
project, and this is
> modelled with a reference from Project -> Staff
called projectMember.
> 
> I may build some clever functionality into Staff and
Project, but any
> organisation wishing to use this product will probably
want to manage their
> own metadata and view templates for staff information
and project
> information. The problem is - how do they re-use this?


Hopefully this is related --

Since hearing Alan R. say that one should always program
defensively and
redefine classes:

  from Bluh import ClassA
  
  def MyClassA(ClassA):
      pass

...this made me how to actually do this in practice. What
happens to:
  * all the installation code you use for ClassA
  * how meta_type, portal_type, archetype_name of the
classes work, how they
show up in add menus (both? by waht name?)
  * any other interactions between ClassA and other portal
objects (e.g., if it
looks up info in a property sheet, or a vocabulary manager,
etc.)


How does all of this get managed in a clean way? Seems like
a combination of
good standardized coding practices to allow redefining
easily, plus some changes
in Archetypes.


Peace,
George



-------------------------------------------------------
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
_______________________________________________
Archetypes-devel mailing list
Archetypes-devellists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/archet
ypes-devel