AT Content Types

Installation

 Please read docs/INSTALL.txt for a list of requirements before installing this
 product. ATContentTypes requires new versions of Python, Zope, Plone and
 Archetypes. Make sure you've updated all products.

Reporting bugs / feature requests

 Please use the bug tracker in the collective at http://sf.net/projects/collective!
 The url is http://sourceforge.net/tracker/?atid=645337&group_id=55262&func=browse
 Please don't mail bug reports to the mailing lists or to a developer unless
 they are in the bug tracker, too.

Comparing CMF types with ATContentTypes

 This is a very roughe and short list of differences between the old CMF types
 and the new ATContentTypes types.
 
  * Archetypes: All types are written with Archetypes and have all features
    default Archetypes based types have like:
    
     o autogenerated edit forms based on the schema
     
     o referenceable
     
     o Easily enhanceable by subclassing or adding fields to the schema
     
     o Transformations like restructured text, python source code
       highlighting, pdf to html, office to html and many more.
     
     o plugable validation of fields
       
  * Clean and documented API.
  
  * Translateable using LinguaPlone.
    
  * Dynamic Views: All types are using the new dynamic view FTI
    that allows you to choose the view template per instance. You can
    configure the templates in the portal_types tool. This features 
    is used to turn an ordinary folder into a
    photo ablum by simple switching to a different view.
    
  * Permissions per type and feature: Every type has its own add permission
    and all features like template mixin have their own modify permission, too.
    
  * Numerous small adjustments and enhancements to all types for example:
  
    o Images can be rotated through the web and have exif informations
    
    o News Items have an image plus caption
    
    o Events have a body text
    
    o Documents have a history tab to show the last changes as an unified
      diff view using the ZODB history. (currently disabled)

What is new in ATContentTypes 1.0

 ATContentTypes 1.0 has a bunch of changes and additional features compared
 to 0.2.
 
  * A related items reference field was added to all types. It can be used to
    add relations between objects, for example a document is related to an event.
    The relations will be shown in a portlet.
    
  * The event type has a body text like document.
  
  * The new item type has a new image field plus a caption for the image.
  
  * Images can be rotated and mirrored through the plone interface. Also there
    are some new methods to get EXIF informations for images.
    
  * The folder type has some new views that are showing the containing images
    like a photo album view.

  * Several new criteria were written for the topic type like portal type
    criterion or reference criterion.
    
  * A tool was added to replace the external methods. It contains some
    additional features, too.
    
  * Each type has its own add permission.
  
  * The type switching was completly rewritten. It's safer and easier but
    it's not possible to have ATContentTypes as additional types any morer.
    ATContentTypes based types are now always the default types.
   
  * The migration from CMF types to ATContentTypes types has some new helpers
    to recatalog CMF or ATContentTypes based types to make sure neither an
    object is missing nor that staled objects are in the catalog. The recatalog
    features are exposed through the tool. In order to sucessfully migrate a
    site you **must** recatalog it using the api or some objects like the
    members folder or topic aren't migrated.
 
  * Several hundreds of unit tests and integration tests were added, existing
    unit tests were improved or fixed. Unit tests are based on ZopeTestCase
    and PloneTestCase.

  * New interfaces were added.
 
  * For developers: Interfaces were moved to a single module interfaces.py and
    schemata were moved to the module of their type classes. E.g. instead of
    importing ATDocumentSchema from content.schemata you have to import it from
    content.ATDocument.
    
  * ZopeX3/Five briged interfaces
  
  * New migration features like savepoints and a catalog patch.


