Summary of messages to the cmf-tests list.
Period Sat Jun 28 11:00:00 2008 UTC to Sun Jun 29 11:00:00 2008 UTC.
There were 9 messages: 9 from CMF Tests.
Tests passed OK
---
Subject: OK : CMF-1.6 Zope-2.8 Python-2.3.6 : Linux
From: CMF Tests
Date: Sat Jun 28 21:34:57 EDT 2008
URL: htt
Hi!
Martin Aspeli wrote:
The GS handlers for portal_types and portal_workflow both require a
single file - types.xml and workflows.xml - that declares the objects,
and a directory full of files - types/*.xml and workflows/*.xml - to
initialise them.
However, in both cases, there is enough i
Am 29.06.2008 um 15:04 schrieb yuppie:
Some tools are ordered containers, the types tool might become
ordered as well. GS always specifies the order of sub-objects in the
container's file.
I suppose you could bundle all the information into a single types.xml
file - like you can with ski
yuppie wrote:
Hi!
Martin Aspeli wrote:
The GS handlers for portal_types and portal_workflow both require a
single file - types.xml and workflows.xml - that declares the objects,
and a directory full of files - types/*.xml and workflows/*.xml - to
initialise them.
However, in both cases, th
Hi!
Martin Aspeli wrote:
yuppie wrote:
Martin Aspeli wrote:
The GS handlers for portal_types and portal_workflow both require a
single file - types.xml and workflows.xml - that declares the
objects, and a directory full of files - types/*.xml and
workflows/*.xml - to initialise them.
Howe
yuppie wrote:
Hi!
Martin Aspeli wrote:
yuppie wrote:
Martin Aspeli wrote:
The GS handlers for portal_types and portal_workflow both require a
single file - types.xml and workflows.xml - that declares the
objects, and a directory full of files - types/*.xml and
workflows/*.xml - to initiali
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Aspeli wrote:
> yuppie wrote:
>> Hi!
>>
>>
>> Martin Aspeli wrote:
>>> yuppie wrote:
Martin Aspeli wrote:
> The GS handlers for portal_types and portal_workflow both require a
> single file - types.xml and workflows.xml - that decl
Tres Seaver wrote:
One point of the types.xml file is that the type name may *not* map
intuitively onto the name of the XML file (people seem determined to
embed spaces in object names, for instance).
Sure. So now we rely on a not entirely obvious convention (space becomes
underscore) and/or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Aspeli wrote:
> Tres Seaver wrote:
>
>> One point of the types.xml file is that the type name may *not* map
>> intuitively onto the name of the XML file (people seem determined to
>> embed spaces in object names, for instance).
>
> Sure. So no
