@Michael Greary In general it is good convention and good practice to follow a naming convention with your files. That goes for any file and not just JavaScript.
-- "Where does it say that" -- On http://docs.jquery.com/Plugins/Authoring it says "Name your file jquery.[insert name of plugin].js, eg. jquery.debug.js" under "There are a few very important points to remember:" -- "It's completely wrong" -- You sure about that? I'm thinking someone very important in jQuery wrote just those guidelines. -- "The filename means nothing unless the JavaScript code itself cares about it, and that would be a very rare case. -- If I were a colleague of your's, I would definitely care about the naming conventions that are used. JavaScript may not, but JavaScript also doesn't care if you compile all of your JS files into one file for less HTTP requests. On Jul 27, 3:29 pm, "Michael Geary" <m...@mg.to> wrote: > Where does it say that? It's completely wrong. The filename means nothing > unless the JavaScript code itself cares about it, and that would be a very > rare case. > > In fact, it's highly recommended practice to combine all of your plugins and > other JavaScript code into a single .js file for faster download. > > -Mike > > > > > From: rickoshay > > > The documentation says the file name for a plug-in is very important. > > There are no "files" from the browser's perspective but if > > we're talking about a URI pattern, why is it "very > > important"? Having the flexibility to serve up plug-in > > scripts using any old URI would be preferable. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to jquery-dev@googlegroups.com To unsubscribe from this group, send email to jquery-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en -~----------~----~----~----~------~----~------~--~---
