[Zope-CMF] Re: [dev] CMF 1.5 roadmap?

[alan runyan]

>> ...
>> b) It already works with plain CMF.  You just need to plug it in to 
>> the
>> repository and maybe tweak a couple of things like stylesheets.
>
> I found a dependancy on "portal_properties.site_properties"
> CMF's "portal_properties" is only one level.

I think portal_properties would be good to make containerish.
Tres had no problems with changing this as long as backwards
compatibility was kept.  Its a obvious place to put propertysheets
for websites.  Whether or not its a good approach is up for debate.

> There is an additional (small) dependancy on Plone's "FactoryTool".

that could be gotten rid of.

>> ...
>
> Archetypes is quite complex. I needed about 2 days to build an
> Archetypes based "Workspace" type. I met several bugs
> and problems.

AT is complex ;-( it does a whole lot.  But it does drastically reduce
the amount of time spent developing content types in CMF.  Add
the reference engine and you have 90% of what people are
consistently asking for (besides having all content in RDBMS).

> Integrating Archetypes (and CMFFormController and PortalTransforms)
> drastically increases the complexity of the package.

CMFFormController probably should not go in.  PortalTransforms
is a problem.  Not sure what to do about it.

cheers,
alan
>