1,3: more about developer's judgment or common sense than 'coding with jQuery'. In any project you'll have to manage the sources/includes in an understandable way, write readable code.
2: that's the idea, separating content, functionality and presentation. looking at the markup must only give you an understanding of the content, when you look at the javascript you'll see the funcionality clearly. 4: a question of following the Unobtrusive JS model. There isn't a situation where it's strictly necessary to insert inline event handlers that I know of. It all boils down to best practices in Javascript or coding itself, there's nothing specific to jQuery in it. If anything, coding in jQuery "forces" developers to write somewhat cleaner code. Some articles about it: http://www.letmegooglethatforyou.com/?q=javascript+best+practices - ricardo On Dec 8, 12:20 pm, Leo <[EMAIL PROTECTED]> wrote: > I am a fairly new adopter of jQuery, but a long time software > developer. One of the things I really like about the jQuery approach > is a mindset to keep implementations clean and maintainable. Having > said that, it is easy enough to take the unobtrusive paradigm down the > path towards unmaintainable systems without some good guidance. > > Several things can happen (in no particular order): > > 1 - application developers can load up one or more js include files > with a lot of seemingly unrelated javascript. Finding the source gets > hard to do. > 2 - the developed jQuery javascript hides the intent of the > application. i.e. When looking at the markup, you can't really > understand what's going on. > 3 - the developed jQuery javascript is hard to follow. It seems as > though spaghetti code never goes out of style > 4 - developers throw some stuff in markup, other stuff in include > files without a clear purpose thereby confusing even themselves two > months down the line. Sometimes it was expedient, other times > necessary, other times it was poor understanding of the app, and yes, > laziness too. > > I've seen some older writing by Yehuda that point the way, but it sure > would be great if there was a wiki or something that provided a > thorough treatment. > > If something already exists, it would be great to shine a brighter > light on it (I haven't found it yet). If not, are there folks willing > to get something together; the entire community would benefit?
