Search and Top Navigation
#8990 closed feature (wontfix)
Opened January 21, 2013 04:14AM UTC
Closed January 21, 2013 02:26PM UTC
jQuery UI compatibility with component.js
| Reported by: | dbarnes | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | none |
| Component: | [meta] ui.dev | Version: | git (not yet released) |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
Is there any chance of refactoring the jQuery UI source code enough that it would be compatible with the compontent.js package manager? (ie. separating each 'component' into their own directory)
It would definitely be a pretty monumental undertaking to fully isolate each widget, it's dependencies, and unit tests, but the payoff could be nice for developers and contributors.
If it's not something that can/will be done in core, would the license rule out "forking" the original source and refactoring it in this way for redistribution via component?
Attachments (0)
Change History (1)
Changed January 21, 2013 02:26PM UTC by comment:1
| _comment0: | > Is there any chance... \ \ Not really. \ \ > It would definitely be a pretty monumental undertaking... \ \ Yes, it would. \ \ > but the payoff could be nice for developers and contributors. \ \ Doubtful. I think we're up to a million and a half different package managers/dependency trackers/distribution systems. Everyone seems to have their favorite and they all have different requirements. \ \ > ...would the license rule out "forking" the original source... \ \ No, you can do what you want, but you must retain our copyright notice and permission notice (license). → 1358778429715804 |
|---|---|
| resolution: | → wontfix |
| status: | new → closed |
Not really.
Yes, it would.
Doubtful. I think we're up to a million and a half different package managers/dependency trackers/distribution systems. Everyone seems to have their favorite and they all have different requirements.
No, you can do what you want, but you must retain our copyright notice and permission notice (license).