Hash: SHA1

yuppie wrote:
> 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.

- -1, if I understand correctly, because it assumes too much.  I *want* to
make each tool'w setup explicit, rather than guessing at it from the
tool's ID>

> toolset.xml already contains all the necessary information if we use the
> ID of the tool for computing the file names. catalog.xml would e.g.
> become portal_catalog.xml.
> GenericSetup would need some BBB code to handle CMF 1.5 profiles.
> Old-style tool handlers can still have their own registry step.

I would rather avoid making yet another seismic shift to how GS works.

> This would make writing and maintaining tool handlers much simpler. On
> the other hand we loose some flexibility:

Exactly.  Lets work on getting all the handlers done, and generalize later.

> - import/export of selected tools from a bigger profile: don't think we
> really need that
> - handling import dependencies: currently the 'workflow' step depends on
> the 'typeinfo' step. AFAICS we can easily get rid of that dependency.
> Nevertheless I think the refactoring would be an improvement and if
> there are no objections I'll work on this change.

I'll need a lot more detail on the proposal, in particular w.r.t. the
timeframe I'm proposing for a 2.0 release.

- --
Tres Seaver          +1 202-558-7113          [EMAIL PROTECTED]
Palladion Software   "Excellence by Design"    http://palladion.com
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org


Zope-CMF maillist  -  Zope-CMF@lists.zope.org

See http://collector.zope.org/CMF for bug reports and feature requests

Reply via email to