Hi!
The setup handlers for adapter based import / export are just
boilerplate. I'd like to move the complete responsibility for setting up
tools to importToolset / exportToolset.
toolset.xml already contains all the necessary information if we use the
ID of the tool for computing the file
yuppie wrote:
The setup handlers for adapter based import / export are just
boilerplate. I'd like to move the complete responsibility for setting up
tools to importToolset / exportToolset.
toolset.xml already contains all the necessary information if we use the
ID of the tool for computing
Florent Guillaume wrote:
yuppie wrote:
- import/export of selected tools from a bigger profile: don't think
we really need that
What do you mean by i/o of selected tools from a bigger profile ?
Right now each tool has its own import step and export step. The
'Import' and 'Export' tab of
The patch I propose to include is:
http://mail.zope.org/pipermail/cmf-checkins/2005-November/007137.html
Could some Plone folks please test that switching to
CMF/branches/efge-1.5-five-compatible instead of CMF/branches/1.5 doesn't
cause problems in Plone ? This patch just changes the order of
Could folks having old CMF branches clean them up ?
See http://svn.zope.org/CMF/branches/
This seems to concern: ajung, andrew, chrism, chrisw, gregweb,
jshell, mj, regebro, shane, sidnei, slinkp, tseaver, yuppie.
Florent
--
Florent Guillaume, Nuxeo (Paris, France) Director of RD
+33 1 40
Hi Florent!
Florent Guillaume wrote:
yuppie wrote:
- import/export of selected tools from a bigger profile: don't think
we really need that
Right now each tool has its own import step and export step. The 'Import'
and 'Export' tab of the setup tool allow to select single steps and run
them
