Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement the widgets in an AMD/require.js compatible manner #16

Open
bleathem opened this issue Aug 8, 2013 · 6 comments
Open

Implement the widgets in an AMD/require.js compatible manner #16

bleathem opened this issue Aug 8, 2013 · 6 comments
Labels
Milestone

Comments

@bleathem
Copy link
Member

bleathem commented Aug 8, 2013

In order for us to be able to effectively use require.js to manage RichWidgets dependencies, the dependencies of RichWidgets themselves need to be manageable by AMD. While jQuery.js is itself AMD compatible, unfortunately the jQuery UI widget factory (and widgets built using that factory) are not AMD compatible.

This article explains a workaround to get the jQuery UI widget factory to be AMD compatible:
http://gregfranko.com/blog/registering-the-jqueryui-widget-factory-as-an-amd-module/

Efforts are underway to deliver an AMD compatible jQuery UI widget factory in an upcoming jQuery UI release. This can be tracked via the URL:
jquery/jquery-ui#1029

@rxaviers
Copy link

The plan is to support AMD on the upcoming jQuery UI 1.11

@lfryc
Copy link
Member

lfryc commented Aug 14, 2013

Great news, @rxaviers !

@lfryc
Copy link
Member

lfryc commented Sep 6, 2013

Consider using UMD (Universal Module Loader) as jQuery UI attempts to do:
https://github.com/umdjs/umd

@bleathem
Copy link
Member Author

Looks like the upstream issue is now resolved, we are now waiting on it to land in the as-yet upcoming jQuery 1.11 release.

@lfryc
Copy link
Member

lfryc commented Feb 19, 2014

It would like to grab stable master and try it before 1.11 is out, is that
worth it?

On Tue, Feb 18, 2014 at 11:45 PM, Brian Leathem notifications@github.comwrote:

Looks like the upstream issue is now resolved, we are now waiting on it to
land in the as-yet upcoming jQuery 1.11 release.

Reply to this email directly or view it on GitHubhttps://github.com//issues/16#issuecomment-35444791
.

@bleathem
Copy link
Member Author

+1 better to catch any incompatibilities before the release is out

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants