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

[yuppie]

Hi!


Tres Seaver wrote:
> yuppie wrote:
>> A second zpt skin? Or modifying the existing one?
> 
> A second one, I think.  We can kill off the old "nouvelle", etc. and 
> replace them with a "slick" skin (or something :).

Who will maintain another skin? I think we should focus on one skin that 
demos the possibilities of CMF. A second skin might make sense to demo 
the skin switching features, but there shouldn't be more than 2 or 3 
files in the additional layer.

>> - What about the 'portal_configuration' tool you mentioned earlier?
> 
> I know there are several rumblings in this direction in the community: 
> for instance, the "DCWorkflowDump project",
> http://cvs.sourceforge.net/viewcvs.py/collective/DCWorkflowDump/ 
> competes slightly with the current tool (which dumps workflow to an XML 
> spec, with supporting scripts).
> 
> I imagine that this would take a day or so to disentangle from its 
> current home.  We could certainly use the tool for other consulting 
> projects here, which might give me some leverage to get resources for 
> the migration.

I'd love to see a tool like that in CMF.

>> - Can we add a DC Workflow instead of DefaultWorkflow by default?
> 
> +1

'Classic', not 'Revision 2'. Right?

>> - I'd like to add Zope 2.7's OrderSupport to PortalFolder. CPS and 
>> Plone already use the order API. But I'm afraid this is controversial.
> 
> I think the controversy died out once OrderedFolder landed in the Zope 
> core.  Can anybody point to links where the controversy was hashed out 
> w.r.t. CMF?

I don't remember a controversy w.r.t. CMF. So maybe this is less 
controversial than I thought. This is what I want to do:

- Add a copy of Zope 2.7's OrderSupport to CMF that is used if we can't 
import OrderSupport from Zope. Can be removed again as soon as Zope 2.7 
or higher is required for CMF.

- Add OrderSupport to PortalFolder.

- Add an UI similar to that of Zope 2.7's Ordered Folder to 
folder_contents.pt.


Cheers,
	Yuppie