collective/templer.dexterity — pull request #3 by kagesenshi (2012-10-25 00:48:36+00:00)
Title: Better dexterity content type skeleton

Changes:

- I've got rid of the custom content type class usage as it is more flexible to use dexterity.Item/dexterity.Container directly. The original reason i created the custom content class usage back in collective.dexteritypaste (which later become zopeskel.dexterity) was mainly due to I had some Archetype assumption that content class is needed, but after doing several projects on dexterity, i discovered that this is unnecessary. Furthermore, not using custom content class gives the benefit of easier refactoring as the zodb content object is not coupled to the custom content class

- I replaced the SampleView with a default view based on dexterity.DisplayForm and plone.app.dexterity item default view. This makes it easier to immediately customize the default view of the content type. dexterity.DisplayForm also provides a way to easily render existing widgets.

- the buildout is now updated to extend the test buildout from collective/buildout. that way it will always use the latest plone4 release buildout.