-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Florent Guillaume wrote:
> Can I fix the "pretty" xml exporter to use standard identing? (2 spaces
> for tags, 4 for attributes)
+1
- --
===
Tres Seaver +1 202-558-7113
Can I fix the "pretty" xml exporter to use standard identing? (2
spaces for tags, 4 for attributes)
Florent
--
Florent Guillaume, Nuxeo (Paris, France) Director of R&D
+33 1 40 33 71 59 http://nuxeo.com [EMAIL PROTECTED]
___
Zope-CMF maillist
I don't want to start another flamewar, but can I bump down the log
levels of CMF's exportimports a bit ?
INFO is too much.
DEBUG or BLATHER ?
I can add a blather method in GenericSetup.context.Logger.
Florent
--
Florent Guillaume, Nuxeo (Paris, France) Director of R&D
+33 1 40 33 71 59
On 13 Dec 2005, at 15:55, Florent Guillaume wrote:
I'd like to make the Properties tab go first, before Contents, in
the setup_tool. Opinions ?
Not sure it really matters... +0 from me, if you think it's
important, go ahead.
jens
___
Zope-CMF
I'd like to make the Properties tab go first, before Contents, in the
setup_tool. Opinions ?
Florent
--
Florent Guillaume, Nuxeo (Paris, France) Director of R&D
+33 1 40 33 71 59 http://nuxeo.com [EMAIL PROTECTED]
___
Zope-CMF maillist - Zo
Hi Florent!
Florent Guillaume wrote:
On 13 Dec 2005, at 12:50, yuppie wrote:
I'd propose to implement an update mode for list properties and to add
an update file for each allowed container. Something like that:
(Didn't have a look at the code. I guess this currently overwrites t
On 13 Dec 2005, at 11:01, yuppie wrote:
Florent Guillaume wrote:
Also, why is the meta_type information duplicated in typesinfo.xml
and types/foo.xml?
The adapter for the container is responsible for creating empty sub-
objects. So in this case the TypesToolXMLAdapter needs to know the
met
On 13 Dec 2005, at 12:50, yuppie wrote:
Florent Guillaume wrote:
When importing an type information from an extension profile, I'm
finding the need to have it specify in which containers'
allowed_content_types it should be added. I'd like to add a pseudo-
property allowed_container_types for
Hi Florent!
Florent Guillaume wrote:
When importing an type information from an extension profile, I'm
finding the need to have it specify in which containers'
allowed_content_types it should be added. I'd like to add a
pseudo-property allowed_container_types for this. It would have to be
re
When importing an type information from an extension profile, I'm
finding the need to have it specify in which containers'
allowed_content_types it should be added. I'd like to add a pseudo-
property allowed_container_types for this. It would have to be read
and written specially.
It could
Hi Florent!
Florent Guillaume wrote:
CMFCore.browser.typeinfo.FactoryTypeInformationAddView.getProfileInfos
parses all the profiles types/*.xml files to check their meta_type. Why
not check simply typesinfo.xml ?
The CMF 1.5 version of typesinfo.xml doesn't contain the meta_type. My
plan wa
The following supporters have open issues assigned to them in this collector
(http://www.zope.org/Collectors/CMF).
Assigned and Open
efge
- "CMFSetup: provide non-ascii im- and exports",
[Accepted] http://www.zope.org/Collectors/CMF/292
jens
- "Discussion replies removal",
12 matches
Mail list logo