Hi, > Well, let me first explain the "let's break the API" point of view, in > this specific case. > A lot of macros are playing tricks to get the informations that are now > provided by the formatter (and the formatter.context), so I think it > usually makes sense to _really_ upgrade them.
I think most people would agree. However (and this is a very important point) from the admin point of view, breaking down a whole site for the sake of API improvement is not worth it. There are a lot of macros available out there, and failure in macro execution not only remove some nice features from existing Wiki pages, but also make some pages hardly usable - knowing that when a macro fails, a quite large red box is rendered in-place. We should try to make upgrades "smoother" as Trac is now widely used. I think open source aficionados are likely to forgive this kind of glitch, while it is less acceptable for enterprise-grade installations. I hope we can provide an adapter for the old macro API before releasing 0.11 (+ the warning in log files to ask admins to upgrade the macros). Cheers, Manu --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
