As I said in the associated ticket, I agree.

We should keep the same name between versions and simply alert theme  
developers that they (might) need to update their js.

Thankfully, the API doesn't change that much so developers shouldn't  
have to update much.

On Apr 25, 2009, at 11:45 AM, Owen Winkler wrote:

>
> Chris J. Davis wrote:
>> I am in favor of keeping the file named jquery.js and just alerting
>> theme and plugin developer when we update.
>
> I agree.  I think that renaming it during the jQuery upgrade was  
> merely
> an oversight; that Blake did not intend to break plugin compatibility
> while doing this.
>
> As far as jQuery versioning is concerned, I think we should choose a
> single version (hopefully the latest) of jQuery and release Habari  
> with
> that.  We should not include prior versions for a few reasons,  
> including
> most simply that they would bloat the download, and more technically
> that having multiple versions on one page would likely not work well  
> anyway.
>
> 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.
>
> We should also consider allowing for the possibility of easily  
> updating
> the jQuery version via plugin, so if there is a significant release of
> jQuery with more compelling features for plugin authors between Habari
> versions 1.0 and 2.0, they are able to make use of it.  The effects of
> the new jQuery on Habari's core would need to be addressed by that  
> plugin.
>
> The above approach seems reasonable to me, and is how similar  
> projects I
> am familiar with approach the issue.
>
> Owen
>
> >


--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to habari-dev@googlegroups.com
To unsubscribe from this group, send email to 
habari-dev-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/habari-dev
-~----------~----~----~----~------~----~------~--~---

Reply via email to