Personal tools
You are here: Home Products Plone Roadmap #28: AT Content Types as default types
Document Actions

#28: AT Content Types as default types

Contents
  1. Motivation
  2. Proposal
  3. Implementation
by Alexander Limi last modified June 11, 2006 - 00:21
Plone should move to Archetypes-based default types to make it easier to extend the built-in types - and to make it possible to leverage some of the built-in features of Archetypes.
Proposed by
Christian Heimes
Proposal type
Architecture
State
completed

Motivation

  • CMF types are ancient, partly bad coded and lacking some import things like accessor/mutator (lot's of values are only available as attributes)
  • Subclassing and enhancing CMF types is very hard
  • Document doesn't support reST, pdf/doc upload etc.
  • ATCT is using the full power of Archetypes and PortalTransform
  • It's very easy to enhance ATCT types

Proposal

Currently Plone 2.0 is using the types from CMFDefault, CMFTopic and CMFCalendar. ATContentTypes (ATCT) is a feature improved reimplementation of the default types using Archetypes.

Implementation

ATContentTypes is a seperate product which depends on Archetypes (>1.2.5). Migration from CMF types to ATCT types is part of the product.

To make ATCT the default types and replacements of CMF types: * ship ATCT with plone and make it a requirement * run the migration of ATCT in the migration of plone * replace the CMF types with the ATCT types * disable the CMF types

Right now (2003-03-31) ATCT is mostly working and I'll publish a first testing beta when AT 1.2.5-rc5 is out.


For any issues with the web site functionality, please file a ticket.

Please consult the policy on plone.org content if you want your content published on this site.

Servers and hosting by