Since I started this whole discussion I guess I should contribute with my thoughts without just saying "its stupid" :P.
Forcing themers to include their own version of jquery is imho stupid since we’re already having a version. Relying on google is also imo stupid. Gmail, for example, have been down more then once the last 6 months. If Habari will include jQuery for core-admin stuff we should make it simple for themers to use it, hence not renaming it and so one. I also think we should strongly suggest themers/plugin-creaters to use the include jQuery. I’ve seen pages use jQuery, mootools and xx for different stuff. Imo that is really stupid. Since most people now have fast internet connections and the libs are small it’s not a big deal but the less files loaded the better. We should also make it clearer how the stacks work. Right now it’s possible to end up with multiple versions of jQuery, from theme and plugins. That’s not a good situation either. Different plugin authors load their jQuery using different names, and in different places (for speed all js should be loaded in the footer for example…). This is imo something that should be standardized, the wiki should explain where and how stuff should be loaded. Or at least suggest how it should be loaded. I’m not saying that Habari should force writers to use jQuery and only load stuff in the footer/header. I’m just saying it should be suggested. On 28 Apr, 00:32, Sean T Evans <[email protected]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > > > > Blake Johnson wrote: > > On Apr 25, 11:45 am, Owen Winkler <[email protected]> wrote: > >> Plugins should be tagged for specific versions of Habari, and when we > >> reach Habari 1.0, we will standardize on a single version of jQuery (we > >> won't change jQuery versions until 2.0) so that plugins don't have a > >> moving target. > > > Don't you think that this should depend on the amount of time between > > releases? You are completely right that it will not be possible to > > allow plugins to load their own version of jQuery within the admin > > (they can do whatever they like on theme pages). I also feel that it > > is not unreasonable to update the jQuery version which ships with > > Habari on an annual basis. > > > On a related note, we probably should change the way we ship jQuery > > UI. Previously, we included individual files for each component > > (ui.slider.js, ui.sortable.js, etc). When I upgraded the version of > > jQuery UI in trunk, I changed this to a single compressed file. This > > currently also has a version specific name: jquery- > > ui-1.7.1.custom.min.js. Perhaps this should just be renamed jquery- > > ui.js? > > > --Blake > > Our stated release policy is that major version numbers should maintain > API compatibility. In my mind this means that we don't change things > (even third-party things) that will break themes and plugins. Within a > major number, we keep backwards compatibility. > > - -- > Sean T. Evans > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (GNU/Linux) > Comment: Using GnuPG with Mozilla -http://enigmail.mozdev.org > > iEYEARECAAYFAkn2Mo0ACgkQmQpMBUWJpdtAnwCg9AYnXw23fhOT8YAflTE1Y61V > 3p8AoLyTUAdQ5YRBsU6FMuwTb21MsLZU > =jWl+ > -----END PGP SIGNATURE------ Dölj citerad text - > > - Visa citerad text - --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
