-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Alec Mitchell wrote:
> I concur that the globalize stuff is a serious hack and should be
> removed at some point.  However, I don't think 4.0 is the right time
> to remove it considering the huge impact it will have on 3rd-party
> products.  If removing it doesn't result in a significant performance
> improvement (and apparently it does not), then I'd suggest we continue
> to live with it until the "break-everything" 5.0 release.  We didn't
> have a PLIP for this and it would be a major disruption for 3rd party
> developers and integrators.

Any 3rd party developers who want to find out whether their templates
break without the globals can test them easily:  just customize the main
template under 3.3 and remove the following line:

  <metal:block use-macro="here/global_defines/macros/defines" />

Any template which breaks without that line present can be trivially
fixed by adding 'tal:defines' to pull in the names needed.  No need for
any black majyk here.

> Perhaps we could find some clever way to deprecate access to the
> globalized attributes (e.g. make them all lazy lookups and issue a
> warning on first access)?

There is an example of this pattern in the 'ursine_globals' view on the
CMF trunk:


http://svn.zope.org/Products.CMFDefault/trunk/Products/CMFDefault/browser/ursa.py?&view=markup


Tres.
- --
===================================================================
Tres Seaver          +1 540-429-0999          tsea...@palladion.com
Palladion Software   "Excellence by Design"    http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFKejCh+gerLs4ltQ4RAmKRAJ0ea+hImFlLqsc1N+YwYmGa2R8czQCeIifb
jXSsBCCqIHnikyiytjg9ni8=
=p6uU
-----END PGP SIGNATURE-----


_______________________________________________
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team

Reply via email to