whit wrote:
I remember some discussion of this in the past.
Transitionally, it would be helpful to be able to register local
utilities to a tool name, and then have getToolByName spit out a
deprecation warning and return an appropriate object.
Why a deprecation warning and not just do it?
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
howdy lennart!
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
whit wrote:
I remember some discussion of this in the past.
Transitionally, it would be helpful to be able to register local
utilities to a tool name, and then have getToolByName spit out a
deprecation warning and return an appropriate object.
thoughts? comments? does this exist somewhere
