is not used any more and exists only for history. Post new tickets on the Github account. n'est plus utilisée, et existe uniquement pour son historique. Postez les nouveaux tickets sur le compte github.

Opened 13 years ago

Closed 11 years ago

Last modified 11 years ago

#806 closed enhancement (fixed)

Update to jQuery v1.4

Reported by: bibo Owned by: laurentj
Priority: normal Milestone: Jelix 1.2RC1
Component: jelix-www Version: trunk
Severity: minor Keywords:
Cc: Blocked By:
Blocking: Documentation needed: no
Hosting Provider: Php version:

Description (last modified by laurentj)

jQuery 1.4 has been released. It has some good perf wins. We should integrate it at first on trunk and if no regressions arise (is jQuery UI compatible?) land it in 1.1branch.

Change History (13)

comment:1 Changed 13 years ago by bibo

  • Owner set to bibo
  • Status changed from new to assigned

jQuery UI 1.6rc5 is now compatible with jQuery 1.3.

Taking the bug. I will upgrade jQuery UI also. And provide only YUI minified version of the file (since this gives the best results associated with gzip)

comment:2 Changed 13 years ago by laurentj

  • Severity changed from normal to minor

no, too late for 1.1. No more change for 1.1. So only in the trunk.

comment:3 Changed 13 years ago by laurentj

  • Component changed from jelix to jelix-www
  • Milestone set to Jelix 1.2

comment:4 Changed 13 years ago by bibo

jquery ui has made some drastic reorg. to its files bundles for v1.7.
A developper is now supposed to serve one js file jquery-ui-1.7.custom.min.js and one optional css file for widget theming.

We can choose which component to include in the js file but the whole library is 190k minified which is huge IMHO. But it's fine to have much less file dependencies. So I propose for jelix to include only components needed by some of jelix features (e.g datepicker, etc.) and the default jquery ui theme in order to keep the file size low.
If a developper needs another widgets or components, he can build his own customizable jquery-ui and he can(*should*) also roll his own theme.

Thoughts ?

comment:5 Changed 13 years ago by laurentj

yes why not

comment:6 Changed 13 years ago by Julien

when downloading jQueryUI, we still have separate .js files in the dev bundle. So we could minify them an pack them in Jelix, and stick with the current behavior.

Having a minimal custom bundle built for jelix needs may cause problem if the developer needs extra features : if I'm loading my own jquery bundle in a page that has a jForm (which require jQuery), I think problems may occur (lib loaded twice, different versions, ...).

I suggest to include the full jQueryUI (and the packed-in jquery base lib) in Jelix, minified in a unique file. Keep in mind that this file will be cached by the browser, so yes, 200Ko is huge, but only once ;)

comment:7 Changed 12 years ago by laurentj

  • Description modified (diff)
  • Summary changed from Update to jQuery v1.3 to Update to jQuery v1.4

Jquery 1.4 is released.

comment:8 Changed 12 years ago by laurentj

  • Milestone changed from Jelix 1.2 beta to Jelix 1.2

comment:9 Changed 11 years ago by Litchi

Elle en est ou l'intégration de jquery 1.4 / jquery UI 1.8? Qu'est ce qu'il reste a faire?

comment:10 Changed 11 years ago by bibo

Hello I'm late on this one. Sorry ;-) But I think i can make a patch for the end of week.

comment:11 Changed 11 years ago by laurentj

  • Owner changed from bibo to laurentj
  • Status changed from assigned to new

I take it

comment:12 Changed 11 years ago by laurentj

  • Documentation needed set
  • Resolution set to fixed
  • Status changed from new to closed

fixed. I updated jQuery, jQuery UI, markitup, the plugin include, and removed date_input:

For jQuery UI, as before, I installed only minified version of all components. So you can load only component you need.

If you want to use an other version of jQuery/jQueryUI, you can set the new option jqueryPath into the configuration file.

Note: See TracTickets for help on using tickets.