Side navigation
#7561 closed enhancement (wontfix)
Opened November 19, 2010 08:27AM UTC
Closed November 21, 2010 04:36AM UTC
Manage a plugin registry table
| Reported by: | anonymous | Owned by: | |
|---|---|---|---|
| Priority: | undecided | Milestone: | 1.5 |
| Component: | unfiled | Version: | 1.4.4 |
| Keywords: | needsreview | Cc: | |
| Blocked by: | Blocking: |
Description
An issue I found using Jquery plugins on a website managed with a content-centric CMS is its capability to know if a pluggin is already loaded.
A nice feature would be to maintain a plugin regsitry list in jQuery core and access the list like $.isRegister(aPlugginId-aPlugginVersion). Plugins compatible with this version are responsible of their own registration.
For example I have a page with 3 code snippets, 1 for rendering an event that require a date picker, and 2 times the same snippet for rendering an image gallery. The first time the snippet for the galery is called it will load the required pluggin. The second time as it will see it's already present in the registry, no need to load the pluggin.
Hope this makes sense
Attachments (0)
Change History (2)
Changed November 20, 2010 10:42PM UTC by comment:1
| keywords: | → needsreview |
|---|
Changed November 21, 2010 04:36AM UTC by comment:2
| resolution: | → wontfix |
|---|---|
| status: | new → closed |
This seems like something you'd want to do with a dependency management solution like requirejs or stealjs. jQuery currently isn't throwing its cards into that game, but may in the future, but as a full system, not as a specifically plugin registration system. You could build this as a plugin though.