On 1/17/06, Raphael Ritz <[EMAIL PROTECTED]> wrote:
> It was the promise that 'getToolByName' would always just do
> the right thing (TM) so that add-on developers would not have
> to worry. So why deprecating that now?
Because that promise has been completely revoked, since add-ons
developed for old versions of CMF will not work on Zope 3 anyway. ;-)
On 1/17/06, Rocky Burt <[EMAIL PROTECTED]> wrote:
> Hmm... I'm not sure this is useful unless we map standard utilities to
> the equivalently functioning tool (which I don't think is a good idea).
Right, any tool that now exists must directly map unto a local
utility, and that local utility must also have the same API.
If we in CMF 2.0 feel that most tools should be made into utilities,
we could register the utilities with a name, and use the old tool
name. getToolByName could then both try local acquicistion, and do a
query for a generic interface (ICMFTool?) with the name.
The other option is to keep the tools, but also register them as
utilities. That would probably need some changes in the utility
registration, though, from the primitive implementation that is in
Lennart Regebro, Nuxeo http://www.nuxeo.com/
CPS Content Management http://www.cps-project.org/
Zope-CMF maillist - Zope-CMF@lists.zope.org
See http://collector.zope.org/CMF for bug reports and feature requests