[Building Sakai] Javascript Libraries

[Aaron Zeckoski]

If you (or anyone really) are doing anything to up-convert in the
jQuery 1 series now or soon then you should be targeting 1.10 and not
1.9. The http://jquery.com/upgrade-guide/1.9/ and migrate plugin both
still apply but you get the newest and best fixes in 1.10 (and
eventually 1.11 etc.)

That said, there is no way in the world I would ever be using a
non-specific version of jQuery as a tool developer, core developer, or
developer in general. I don't think anyone else should either.
Unfortunately it is a reality of how jQuery is run and versioned and
sorta a lesson in minor vs major versioning and API stability.

I don't think it is worth trying to have a "portal" or "centralized"
version of jQuery that is non-specific. Freezing the version seems OK
but not at a 1.9 version and depends on what kinds of fixes the jQuery
guys come up with to deal with the ever changing browsers.

-AZ


On Mon, Jan 13, 2014 at 10:00 AM, Charles Severance <csev at umich.edu> wrote:
> Unfortunately the problem is that as JQuery goes through its 1.x and 2.x
> versions, they keep finding "better" ways of doing things and so they break
> old ways of doing things.  So an upgrade from JQ 1.6 to 1.9 will likely
> break several things.
>
> Interestingly, there always seems to be a trivial workaround for their
> removed features - but they don't want to keep the old way working.
>
> So having one central JQuery version would be a great idea - but then when
> we upgrade it - stuff will break all over the place across core and conrtib.
> I did just a bit of experimenting with this when I was playing with removing
> iframes - and it is quite frustrating.
>
> We should come up with a central place to manage this for those tools that
> are willing to stick with the same version as portal - currently  jQuery
> 1.9.1 and jQuery-UI 1.10.3 as Sam mentions and then me really mindful when
> we change the version.
>
> I have a feeling this will come to an even more painful head when some Sakai
> tool decides it loves JQuery 2.0 and we don't have frames any more and then
> we will break a *ton* of stuff.
>
> If it were up to me, once we get to JQuery 1.9.1 across the core, I might
> suggest that we freeze the JQuery version for a year or two.
>
> I so wish JQuery would give us a set of backwards-compatibility libraries at
> the cost of a little more code.  But they are like "WE ARE JQUERY - YOU WILL
> BOW BEFORE OUR GENUIS".
>
> /Chuck
>
> On Jan 13, 2014, at 9:07 AM, Jaques Smith <jaques at opencollab.co.za> wrote:
>
> Hi All,
>
> Is there some plan to manage js lib in Sakai? Currently there are 8 (quick
> count) jQuery lib in library alone.
> I'm also not sure how I should link to these from my tools since I guess
> they may change (be removed or updated, new versions added) over time.
>
> Regards,
> Jaques
>
> ________________________________
> See OpenCollab email disclaimer at
> http://www.opencollab.co.za/email-disclaimer_______________________________________________
>
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org
> with a subject of "unsubscribe"
>
>
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org
> with a subject of "unsubscribe"



-- 
Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile