Colin was advocating either having them include their own (which is stupid) or calling googles. I am not in favor of either method honestly but I was one of the proponents of having Habari provide plugin and theme developers an up-to-date environment that includes all the tools they need.
On Apr 26, 2009, at 6:39 PM, Michael Harris wrote: > > On 27/04/2009, [email protected] <[email protected]> wrote: >> >> On 26 Apr, 17:52, Colin Scroggins <[email protected]> wrote: >>> Just want to say that I view it as an architecture flaw to have >>> theme >>> developers (plugin is understandable) dependent upon the admin-side >>> jQuery version. This prevents the core Habari project from moving >>> forward as it sees fit, for fear of breaking old work by the >>> community. Theme developers should be encouraged to include jQuery/ >>> UI >>> in their theme directories or use Google's CDN version (http:// >>> code.google.com/apis/ajaxlibs/documentation/), as there is little >>> benefit to the tie to core Habari. >> >> That's probably true. But since Habari include jquery it feels a bit >> stupid to include it in every theme as well. Since themes probably >> wont be version independent anyway updating what is needed when >> Habari >> changes jquery version wouldn't be that hard either. > > Colin was advocating using a CDN (either Google's, which allows you to > specify a version, or the S3 hosted > http://code.jquery.com/jquery-latest.js). That means jQuery isn't > actually included in the theme, and hence not "stupid" :) > > -- > Michael C. Harris, School of CS&IT, RMIT University > http://twofishcreative.com/michael/blog > IRC: michaeltwofish #habari > > > --~--~---------~--~----~------------~-------~--~----~ 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/habari-dev -~----------~----~----~----~------~----~------~--~---
