Thread: JavaScript Documentation & References

The Document Object Model - DOM:

• W3C DOM Technical Reports (List of the current specs when it comes to the DOM, and their present status)
• Introduction to the Document Object Model
• Peter Paul Koch's Quirksmode (Best resource for DOM and CSS cross-browser support)
• Scripting for the version 6 browsers
• Rough Guide to the DOM

I'm working on collecting DOM links now. PM me with suggestions if you have any.

Other resources:
Event Handling:

• [DOM2Events] (W3C)
• Event Handlers Reference (Netscape DevEdge)
• Handling Events Guide(Netscape DevEdge)
• Understanding the Event Model (MSDN - DHTML)

JavaScript general references:

• ECMA JavaScript References
• JavaScript Tutorials (John Russel)
• DevGuru JavaScript Reference
• Learn Advanced JavaScript Programming
• dev-x JavaScript Operators
• dev-x JavaScript Objects
• JavaScript and Browser Objects Quick Reference
• HTML,CSS,Javascript docs
• JavaScript 101 Part 1
• JavaScript 101 Part 2
• JavaScript 101 Part 3
• Teach Yourself JavaScript in a Week (Arman Danesh)
• JavaScript Manual of Style (Marc Johnson)
• Using JScript Special Edition (Mark Reynolds with Jerry Honeycutt)
• Web Scripting Secret Weapons (Scott Walter)
  

Documentation on Specific Features:

• jellspace - all javascript event handlers (old-but-good)
• JavaScript Reference and Example Site
• jsIndex (Best object oriented JavaScript linklist there is)
  

Document Bindings/Behavior (Two separate Mozilla and Microsoft technologies that might be united in some form in CSS Level 3)

• PBWizard Binding/Behavior version 1.0 Documentation (Meta-resource on this)
• HTC Reference (MS technology)
• HTML Components (W3C Note by MS)
• Action Sheets (W3C Note by Ns)
• BECSS: Behavioral Extensions to CSS (W3C WD, 1999)
• XBL - XML Bindings Language (Moz technology)
• XBL - Extensible Binding Language 1.0 (mozilla.org spec)
• Using DHTML Behaviors (MSDN)
• Behaviors Reference (MSDN)

Object Oriented and Higher Order Programming in JavaScript

• Class Inheritance
• The Many Inheritances in JavaScript
• Object-Oriented Programming with JavaScript, Part I: Inheritance
• JavaScript Inheritance Tutorial
• Object Hierarchy and Inheritance in JavaScript
• Extending JavaScript with Function Pointers
• Event Handlers and Callback Functions - article
• Higher Order Programming - article (Sjoerd really grasps the finer details of JavaScript)
• Douglas Crockford (As does Douglas...)
• Currying JavaScript Functions (Svend Tofte isn't bad at it either)
• JavaScript Object-Oriented Programming Part 1
• JavaScript Object-Oriented Programming Part 2

Various, often specific task related:

• JavaScript Kit (formerly Website Abstraction)
• JavaScript FAQ Knowledge Base
• GateScript

Other technologies related to JavaScript and web design:
W3C Specifications:

• [CSS1] Cascading Style Sheets, level 1
• [CSS2] Cascading Style Sheets level 2
• XML Core WG (XML, XInclude, XML Base, XML Fragment Interchange, XML Information Set, Namespaces in XML, Associating Style Sheets with XML)
• XSL WG (XSLT, XPath)
• XML Linking WG (XLink, XPointer, XML Base)
• XML Query WG (XQuery, XPath)
• XML Schema WG
• HTML Home (XHTML2, XHTML, XForms, XFrames, XML Events, HLink, HTML)
• SVG (Scalable Vector Graphics)
• Math Home (MathML)
• PNG (Portable Network Graphics)
• [HTTP/1.1] HyperText Transfer Protocol 1.1
• What is a good standard? An essay on W3C's design principles

W3C Technologies Resources:

• ZVON.org A site with lots of XML and Mozilla related tutorials and references

JavaScript Graphics Libraries:

• 
  High Performance Vectorgraphics Library (Walter Zorn)
• JavaScript Diagram Builder (Lutz Tautenhahn)
• PNGLets

Now, tell me: Did I miss anything?



Also, not that good for JavaScript, but having a few gems on other languages and maybe a resource to keep an eye on, is The Quick Reference Site.



(PM me with suggested additions, if you have any)

[cut off part from another thread]


Global variables eat memory - local variables exist only as long as the function survives, unless they are in some way referenced from somewhere else. (Mostly the objects that has been created using the function, gíven the function is a constructor.)

If-else consume memory. Use conditional operation (sometimes called ternary operation because it is the only operation that takes three operands in JavaScript) (condition?expression:expression) or short circuit validation when you have only expressions to handle. If you have to handle statements, a switch...case...default is usally faster - even for a simple if(){}else if(){}, though it takes more space to write.

Every extra action you have to take - including climbing the scope chain and calling a function - consume processing power. You gain load speed and readability from splitting up in smaller functions, especially if they are called from many places.

Do..while is faster than while is faster than for is faster than for..in. Sometimes a function calling itself is faster than an iterator, sometimes not. Seems to depend on function complexity - the more complex the more gain. If you can keep a loop shorter than a function, use that instead.

setInterval is better than setTimeout. Neither is good.

Don't ever use eval, Function constructor or RegExp constructor if you can avoid them. They are big hogs all of them.


Use break and continue in loops if they perform an action you might be interested in. It's often better to loop through everything and jump what you don't want to handle than to set a more complex expression in the condition of the loop.

Use labled blocks and breaks for complex execution handling. It may be spaghetti, but it's fast.


Minimise actions inside loops. For instance, never use collection.length inside the condition if it's static during the loop - store it in a variable instead.

Thanks for Your outstanding answer, liorean!

Most subjects I am aware of / understand, however I will dive in the iternary operations structures to know more of it.

One question for now, what's Your advice on the amount of used global variables, maximum 50, 100,...... Because it's so easy to have all my div.id's directly to play with.

Jerome

Use as few as possibly. Create one or just a few holding object containing the variables you want as properties instead.

Also, if you declare a variable inside a function instead of globally, it will exists only so long as the function, so that's a good way of avoiding global variables.

Never use MSDN for information about anything non-MS-proprietary. If you look up a standard property MSDN will tell you how IE implements it, which may or may not be how it's supposed to be implemented, but MSDN never distinguishes. Therefore its information with regard to anything non-MS is unreliable.

<nb>I'm not MS bashing here .. simply passing on advice because I value integrity of information ... and I've been embarrassed too many times </nb>

For MS-proprietary information it's second to none, but it's search facility is not so great; Google Site Search is much more reliable: "site:msdn.microsoft.com your search words"

Just made a cleenup of blind links and made some additions. (Thanks, everyone reporting those blind links and suggesting additions.)

I'm also looking for some way to bring the structure of this list to a level that makes it easier for newbies to find what they are searching for in it (Currently it's more targetted at people already familiar with the languages and it's construction and abilities). If you have any suggestions, PM me.

(I like to keep this thread absolutely on-topic and relevant)