Up until now I just put all my jQuery goodness inside the $(document).ready()
function, including simple functions used in certain user interactions.
B
If you're creating a function that needs to be called outside of the scope of the $(document).ready() function, keep it outside of the $(document).ready() function.
Otherwise keep it internal.
one advantage of putting those functions inside the document ready function is that they don't pollute your global namespace... with the downside that if you need them somewhere else on the page they won't be available.
Put it inside so it won't pollute the global namespace. It also ensures a faster resolve of the function name because of JavaScript's scope chains.
Put it outside if it's a reusable component so you could easily move it in a separate file and call from different contexts.
Since you already use JQuery, it's worth mentioning, that in your case you may want to define hexvalidate
as a JQuery plugin outside and then invoke it inside.
I don't think you should be using any 'just functions' in the first place. In OOP javascript a "function" usually belongs to one of four distinct types:
e.g.
(function() { <- init closure
function helper1() { <- utility }
globalSomething = {
foobar: function() { <- method
xyz.replace(/.../, function() { <- constant })
}
}
)()
In your example, 'hexvalidate' is obviously a part of Validator object, which, in turn, can be made a jQuery plugin:
(function($) {
$.validate = {
hexColor: function(color) { ... your code }
more validators...
}
)(jQuery)
If all your functions are only called from within the jQuery(function () { })
block, put them inside it. Otherwise you're needlessly polluting the global namespace, which may lead to conflicts down the road.
Only declare functions globally that are also used by code in other scopes.