Part 4: Testing, Tuning and Debugging
Submitted by criecke on Sat, 04/28/2007 - 19:26.
Up until now, we've been looking directly at Dojo and Dijit. Now we'll shift gears for a bit and talk about stuff outside the code itself. When you work with a rich toolkit like Dojo to build Enterprise-grade apps, the old JavaScript development paradigms aren't so hot:
- Debugging with alert() is tedious and inflexible
- Testing by eyeballing pages requires too much manual recordkeeping
- Notepad just doesn't cut it as an IDE!
- Development "frills" like whitepace and comments now get in the way of performance. The more you do, the more bytes to download to the client, and the slower the load time
In Part 4, we'll look at ways to combat all of these issues. The Dojo people aren't content with dropping the API in your lap and running. Oh no! In the course of developing Dojo itself, they have built tools and techniques to help you, and they're very generous in sharing them. So let's have a look.
- Printer-friendly version
- Login or register to post comments
- Subscribe post