[Product-Developers] JQueryUI history and futur and sunburst's !important

Luca Fabbri luca at keul.it
Tue Dec 6 08:09:23 UTC 2011


On Mon, Dec 5, 2011 at 11:17 AM, Jean-Michel FRANCOIS <toutpt at gmail.com> wrote:
> 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.
>

This will be great. For sure beeing able to control what component
could be loaded can be a great new feature. Also, a way to use generic
setup for this is a great task.

----

In the past I was thinking about a new way of importing jQueryUI
stuff. Note that this is only an idea, I've never write a single line
of code for this, but I think that can be a good enhancement if
JQueyUI JavaScript can be imported calling a views, like:

http://foo.com/++resource++collective.js.jqueryui/autocomplete+datepicker
...obtaining only minimal jqueryui code for autocomplete and datepicker

and

http://foo.com/++resource++collective.js.jqueryui/autocomplete+datepicker+slider
...obtaining only jqueryui code for autocomplete and datepicker  and slider

and possibly a bulk import like:
http://foo.com/++resource++collective.js.jqueryui/all

So ++resource++collective.js.jqueryui became simply a view that merge
all JavaScript code needed for obtaining a set of features (and the
view itself think about dependencies of jQueryUI components, like
jqueryui.com site does when you download the source).

-- 
-- luca

twitter: http://twitter.com/keul
linkedin: http://linkedin.com/in/lucafbb
blog: http://blog.keul.it/


More information about the Product-Developers mailing list