Wichert Akkerman wrote:
- getToolByName gives us a lot of deprecation warnings. We can do two
things: undeprecate getToolByName in plone 3.0, deprecate in 3.5 and
remove in 4.0. Or fix all getToolByNames in 3.0. This is doable with
some effort.
The last one is a decision that we need
- Consider some kind of compitability alias mechanism, so that when
people keep using getToolByName(context, 'portal_types') we translate
that to getUtility(ITypesTool), for as long as we need to (but still
warning).
+1... I mean chrissakes.. getToolByName was supposed to be future
On Thu, 08 Mar 2007 15:02:01 -0800, whit
[EMAIL PROTECTED] wrote:
+100 and someone should blog or write a tutorial about these changes
and how to utilize them.
I'm collecting stuff for the how to update your product for Plone 3 part
of the migration manual that we will send product
Previously Alexander Limi wrote:
On Thu, 08 Mar 2007 15:02:01 -0800, whit
[EMAIL PROTECTED] wrote:
+100 and someone should blog or write a tutorial about these changes
and how to utilize them.
I'm collecting stuff for the how to update your product for Plone 3 part
of the
On 3/8/07, whit [EMAIL PROTECTED] wrote:
- Consider some kind of compitability alias mechanism, so that when
people keep using getToolByName(context, 'portal_types') we translate
that to getUtility(ITypesTool), for as long as we need to (but still
warning).
+1... I mean chrissakes..
Previously Alec Mitchell wrote:
On 3/8/07, whit [EMAIL PROTECTED] wrote:
- Consider some kind of compitability alias mechanism, so that when
people keep using getToolByName(context, 'portal_types') we translate
that to getUtility(ITypesTool), for as long as we need to (but still
