Brian Beck wrote: > Heck, you could even leave in the option and then add something like > this to master.kid: > > <script py:if="tg.mochikit_all" ...> > > Then I could at least see what the heck it's doing with my markup, and > it's very synonymous with tg_flash. It's not the option itself I'm > against... just what it makes happen in the brains of end-users when > they start thinking about where stuff in their markup is coming from... >
Hi Brian, The basic idea behind mochikit_all is that by being a widget we can leverage the link duplication detection and avoiding putting two or more links to the same MochiKit.js. Before mochikit_all I had an idea (never publicized) of using the master.kid line and a py:match to check for link duplication outside of widgets, I don' recall the algorithm ATM. Even if I don't like it that much it I can see mochikit_all as an acceptable config option that publicize the link between TG and Mochi. ;-) Ciao Michele --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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/turbogears-trunk -~----------~----~----~----~------~----~------~--~---
