#1393 closed enhancement (fixed)
Assigning jQuery to an existing namespace
Reported by: | Byron | Owned by: | john |
---|---|---|---|
Priority: | major | Milestone: | 1.1.4 |
Component: | core | Version: | 1.1.3 |
Keywords: | namespace, 'this' | Cc: | |
Blocked by: | Blocking: |
Description
I've started using jquery in the development of a firefox extension.
generally when developing extensions i like to keep all my properties and functions etc in one global namespace, im not sure if this is the best approach but its worked pretty well in the past when it comes to avoiding namespace collisions.
example :
var myObject = {
config : {
debug : true
},
init : function () {..}
};
now after a bit of thought, i realised someone else might decide to use jquery in their extension or use the '$' namepace for something else.. then I thought "No Problem jQuery.noConflict() to the rescue!"
so off I went to try it out;
myObject.$ = jQuery.noConflict();
didnt work...
so then i tried some different combinations..
myObject.foo = jQuery.noConflict();
myObject.prototype.$ = jQuery.noConflict();
var jBuf = jQuery.noConflict(); myObject.$ = jBuf;
by now i was getting frustrated (as is probably evident in this post...) So is there any way to do it like this or will i have to use a seperate namespace for jquery?
--Byron
Change History (5)
comment:1 Changed 15 years ago by
Owner: | set to john |
---|
comment:2 Changed 15 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:3 Changed 15 years ago by
From Arrix:
- There should be some way to unroll 'jQuery' from the global object.
- new Function() should become eval('function(){...}') to catch jQuery in its scope
- Expandos need a prefix so that they don't overlap
comment:4 Changed 15 years ago by
Resolution: | fixed |
---|---|
Status: | closed → reopened |
comment:5 Changed 15 years ago by
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
I committed the first two points in SVN rev [2833], but changing the last one would cause the API to break (since plugins rely on the $events expando). I think this is ok for now, but I'll try to think of a better solution.
Fixed in SVN rev [2819].