What are the limitations/problems of binding a variable to the Jquery Object. I have a function in file A that I would like to access in file B. So in order to do that I bind it to the Jquery Object. I feel there might be reasons not to do that. But I can't think of any. Can anyone help me
e.g
// File A
$.sayHello = function sayHello(){
alert("Hello");
}
//File B
$.sayHello();
what are the problems with this.
Problem with what you do is conflicting with existing functions, that is valid even if you not bind to jQuery and bind to your window, so its better to create namespace and attach variables, functions to it:
Myspace = {}
Myspace.sayHello = function sayHello(){
alert("Hello");
}
Myspace.sayHello();
or if you still want to attach to jQuery do the same with jQuery:
$.Myspace = {}
$.Myspace.sayHello = function sayHello(){
alert("Hello");
}
$.Myspace.sayHello();
You have to ensure that FileA will load before FileB. If you can't ensure that, I'd recommend using document.ready to ensure that the method isn't called until all files are loaded.
// File A
$.sayHello = function sayHello(){
alert("Hello");
}
//File B
$(document).ready(function() {
$.sayHello();
});
Don't pollute the jQuery namespace, declare your own namespace instead :
var myNamespace;
(function (myNamespace) {
var doSomething = function () { console.log('Did Something'); };
})(myNamespace || (myNamespace = {}));
I suggest to use mohamed-ibrahim solution with namespace but with jquery :
File A:
$.fn.extend({
sayHello: function() {
alert("Hello");
}
});
File B :
$.fn.sayHello();
Without Jquery :
File A :
var MYNS = {
sayHello: function(){
console.log("Hello");
}
}
File B :
MYNS.sayHello();
Make sure that file A is defined before file B
jQuerynamespace.