The following supporters have open issues assigned to them in this collector
(http://www.zope.org/Collectors/CMF).
Assigned and Open
efge
- "CMFSetup doesn't correctly detect DCWorkflow on export",
[Accepted] http://www.zope.org/Collectors/CMF/298
gregweb
- "CMFUid.UniqueId
OK, so, interfaces, and a new base-class (which really isn't a
five-class anyway) should go into CMF, then? The typeinfo (if it even
is the right way to do this at all) and the menu-action mapping stays
in CMFonFive? That makes sense to me.
On 5/25/05, yuppie <[EMAIL PROTECTED]> wrote:
> Hi!
>
>
Hi!
Lennart Regebro wrote:
On 5/24/05, yuppie <[EMAIL PROTECTED]> wrote:
There is already the CMFonFive project, but now that Zope 2.8 ships with
Five I'd like to see basic Five support in CMF itself:
Well you have a point. I see some options:
1. Moving CMFonFive to Zope corps CVS and
