Best practices for implementing javascript (for rich internet applications)
28 Jul 2005 - 3:25pm
1 reply
557 reads
Austin Govella
2004
I was documenting best practices for the University where I work, and
I came up with a list for javascript. Developers gave it the once over
and the general okay yesterday:
* http://thinkingandmaking.com/entries/63
These practices should be included in your project's technical requirements.
Jonathan Boutelle, a savvier guy than I, has some good comments about
progressive enhancement/graceful degradation that are worth taking
into consideration. Mostly cause he's right:
http://www.jonathanboutelle.com/mt/archives/2005/07/best_practices.html
--
Austin Govella
Thinking & Making: IA, UX, and IxD
http://thinkingandmaking.com
austin.govella at gmail.com
Get the feed
Comments
On 28 Jul 2005, at 21:25, Austin Govella wrote:
> [Please voluntarily trim replies to include only relevant quoted
> material.]
>
> I was documenting best practices for the University where I work, and
> I came up with a list for javascript. Developers gave it the once over
> and the general okay yesterday:
> * http://thinkingandmaking.com/entries/63
>
> These practices should be included in your project's technical
> requirements.
[snip]
The one thing I'd add is to have automated tests for as much of the
client-side code as possible. Tools like JSUnit[1] and Test.Simple[2]
can help enormously in keeping your code working reliably.
Adrian
[1] <http://sourceforge.net/projects/jsunit/>
[2] <http://www.openjsan.org/doc/t/th/theory/Test/Simple/>