The following supporters have open issues assigned to them in this collector
(http://www.zope.org/Collectors/CMF).
Assigned and Open
mhammond
- Windows DevelopmentMode penalty in CMFCore.DirectoryView,
[Accepted] http://www.zope.org/Collectors/CMF/366
Pending / Deferred Issues
Summary of messages to the cmf-tests list.
Period Sun Nov 12 12:00:00 2006 UTC to Mon Nov 13 12:00:00 2006 UTC.
There were 8 messages: 8 from CMF Unit Tests.
Tests passed OK
---
Subject: OK : CMF-1.5 Zope-2.8 Python-2.3.6 : Linux
From: CMF Unit Tests
Date: Mon Nov 13 06:20:20 EST
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10 Sep 2006, at 16:08, Tres Seaver wrote:
Rocky Burt wrote:
On Sat, 2006-09-09 at 21:57 +0100, Martin Aspeli wrote:
Hi guys,
philiKON pointed out something interesting to me the other day - we
could actually register the existing tools as
I am experimenting with that right now, but my z3/Five-Fu ran low
again ;) My problem: calls to zope.component.getUtility
(interface_class) never return anything. Here's the top part (the
bottom is just the old way) of my CMFCore.utils.getToolByName:
Yay!
def
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Now, you can do this with GenericSetup as well, thanks to Hanno. See
http://svn.plone.org/svn/collective/GSLocalAddons/trunk/
The test is informative:
http://svn.plone.org/svn/collective/GSLocalAddons/trunk/tests/
test_components.py
Hanno said
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jens Vagelpohl wrote:
On 13 Nov 2006, at 16:22, Jens Vagelpohl wrote:
I have to run off right now, but a quick look over GSLocalAddons
suggests it should be part of the main CMF Default GS profile, and
doing it with GenericSetup certainly is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13 Nov 2006, at 22:35, Tres Seaver wrote:
My new handler for the component registry is all set up and
registered correctly, and the various import step that calls
importVarious is set as a dependency for the component registry
import step. The
