I have read again all the documentation of collective.jqueryui.autocomplete.
My reaction was bad, so sorry for that.

I guess it's time to make this proposal for jqueryui js integration in
Plone regarding the fact that there are still new addons to solve the issue
c.js.jqueryui is trying to solve: register
jqueryui plugins in Plone.

The proposal:
Add ability to select JQueryUI plugins you want. The form controller will
check dependencies for you. It will use the jsregistry as a backend to
achieve this.
It means we stop using a 'custom' build of jqueryui because every body need
only one or two plugins will be forced to use the bundle.
I guess this should fix the all addons created with their own build because
the need was different. It will also add the ability to optimize the
javascript configuration
of a project.

TODO:
add a jqueryuiplugins genericsetup step (jqueryui.xml)
add a controlpanel to select plugins.
use plugins instead of custom build
update 'Update' documentation'

So who want this ? Who are against this and why ?

Regards / Cordialement,
JeanMichel FRANCOIS
Find me on Google + <https://profiles.google.com/toutpt>




2011/12/3 Luca Fabbri <[email protected]>

> On Fri, Dec 2, 2011 at 3:01 PM, Jean-Michel FRANCOIS <[email protected]>
> wrote:
> >
> > So what is not working on plone3.3 ? could you sumup the situation
> please ?
> >
>
> Is all in the HISTORY of collective.js.jqueryui:
>
>    1.8rc3 (2010-04-30)
>       Removed completly the withjqtoolsplone3 and withjqtools
> profiles. We don't depend on collective.js.jquery anymore.
>       So the jQuery of Plone 4 is kept. The defaut profile now
> install jqueryui 1.8 without the tabs plugin which conflicts with
>       plone.app.jquerytools. This version only works on Plone 4
> because Plone 4 ships with JQuery
>      1.4+ and jQuery 1.8 requires jQuery 1.4+.
>
> Reading this was clear to me that this project stopped Plone 3.3
> support. I think this is the same issue that make another guy to
> create collective.javascript.jqueryui.
>
> Technically speaking: I still tested the 1.8 branch of you product on
> Plone 3.3 some months ago: the first issue was the use of
> "applyPrefix" attribute on the cssregistry.xml.
> However, fixed this, I still got a lot of other JavaScript issues I
> don't remember.
>
> Offtopic: what I never understand is the need of jQuery 1.4. Isn't
> latest jQueryUI working also with jQuery 1.3.2+ (reading at
> http://jqueryui.com/)?
>
> --
> -- luca
>
> twitter: http://twitter.com/keul
> linkedin: http://linkedin.com/in/lucafbb
> blog: http://blog.keul.it/
>
_______________________________________________
Product-Developers mailing list
[email protected]
https://lists.plone.org/mailman/listinfo/plone-product-developers

Reply via email to