home contents changes options help subscribe edit (external edit)

This powerful ZopeProduct provides a framework for the development of new content types in Plone. It allows schema driven automatic form generation, simple integration with rich content types, and a lower entry bar to the complex requirements Zope places on new content objects.

http://plone.org/documentation/archetypes
home
http://plone.org/documentation/archetypes/documentation
documentation
http://plone.org/documentation/archetypes/documentation/old
more documentation
http://sourceforge.net/projects/archetypes
sourceforge project
http://svn.plone.org/view/archetypes
browse SVN
http://sourceforge.net/tracker/?group_id=75272&atid=543430
bug tracker

http://docs.neuroinf.de/programming-plone/ate - Customizing Archetypes tips

Archetypes 1.2 API Documentation on ZDP

Archetypes 1.2 API Documentation on ZDP (Created using epydoc)

Archetypes 1.2 UML Documentation on ZDP

Intro to Archteypes (ZopeMag)

Video about Archetypes can be found here: http://plone.org/events/conferences/1/video/index_html/view?searchterm=profile

CPSSchemas does something similar.

Archetypes and Zope 3

Martijn Faassen wrote:

 Zope 3 has a schema/forms system. With Zope 3 you can define object
schemas, much like you do with archetypes as I understand it. Zope 3 also
has a form system, where widgets (views for schema fields) are associated
with fields to render them as HTML. It also can do input validation.

 Five already makes some of that machinery available for use in Zope 2,
though more is to come.

 In many ways Archetypes offers a lot more power than Z3 schema/forms,
especially in the area of sophisticated types of fields. Schema/forms is
extensible however, and there's no reason why it couldn't grow to support
this.

 Zope 3 schema are just a kind of Zope 3 interface, and these bring with
them all the other parts of the Zope 3 component architecture, like
adapters and the view system. This is a very flexible system allowing you
to add new functionality to existing content objects without having to
modify them. With Five, that works in Zope 2 too.

 Eventually there could be a migration where Archetypes-based objects
first grow Zope 3 interfaces, and thus gain the previously mentioned
flexibility. Next up, there would hopefully be a further convergence
between archetypes schemas and Zope 3 schemas, where archetypes schemas
might start to look more and more like Zope 3 ones. I'm not sure what how
that would go, but perhaps Sidnei has more ideas.



subject:
  ( 34 subscribers )