On 4/9/06, Brian Beck <[EMAIL PROTECTED]> wrote: > > I don't see why there isn't just a <script> line in master.kid, with > "comment out this line to include MochiKit on all your pages." I just > don't see "include-MochiKit-or-not" as configuration-y as all the other > options. IMO a <script> line would make it much clearer what's > actually going on, not to mention it would make the template more > 'portable,' if you get what I mean. > > Let's say there's a default style.css provided. It'll be a <link> line > in master.kid, right? How about a default_css_all=True line in app.cfg > to be more synonymous with mochikit_all? See where I'm going with this? > But that's just a dumb strawman...
My next screencasts might make this more clear. These will definitely come before the end of the week, or I'm in big trouble. Let's say you're using the AutoCompleteField widget. That widget requires MochiKit. Just using that widget implies that you need MochiKit. But, if you're already using MochiKit you don't want to include *two* references to it. The same can be said for taking advantage of other JavaScript libraries. (You can easy_install Lightbox right now and you'll get Lightbox and Scriptaculous, ready to run... if you use Lightbox, Scriptaculous is automatically included.) Widgets can also include their own CSS. As Jorge mentioned, though, CSS is project-specific more than something like MochiKit is. I think mochikit_all is a nice convenience for folks who are doing a very ajaxian interface. Kevin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
