Closed
Bug 655556
Opened 14 years ago
Closed 12 years ago
iQ library should be separated into a reusable code module
Categories
(Firefox Graveyard :: Panorama, enhancement)
Firefox Graveyard
Panorama
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: jorgev, Unassigned)
Details
I recently read Ian's post on what was learned while developing Panorama (http://blog.iangilman.com/2011/04/firefox-panorama-what-did-we-learn.html), and I was reminded about the iQ library, which is something I discussed with Aza at some point. I was very excited about it because many Firefox extensions use jQuery, and it would be really awesome if we included jQuery support in Firefox to some extent so that extension authors don't need to worry about including the library themselves.
So I looked into the code and was finally disappointed when I realized that the whole code for iq.js is just being merged into the tabview.js file, which contains a ton of other globals and code.
It would be very useful to have iq as a separate JSM, so that authors can import it into their code and have lightweight jQuery capabilities without having to include any more library code.
This seems like a good idea, my only concern is that this could lock us in to a JQuery version that we can never change. Not sure if that's a problem or not ...
Comment 2•14 years ago
|
||
The idea itself isn't bad but I don't know if iQ is ready to be an add-on library or (as Kyle said) if we'd even want that. iQ is pretty good for handling the small stuff that Panorama needs but this may not be true for general needs.
Comment 3•12 years ago
|
||
I don't think we'll want this anymore.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
Assignee | ||
Updated•9 years ago
|
Product: Firefox → Firefox Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•