Yes I know'"with the framework in progress, we don't need no more stinkin' frameworks. Except there's a couple I've seen recently which are noteworthy. I haven't delved into the source code in any depth'"exploring framework code bases has become as much fun as watching paint dry, but there are some interesting ideas here, if you're looking to new angles on the problem.

The "new angles" he mentions are:

• For Tonic, the fact that it's a "RESTful" environment and feels like web.py in its development
• And for Code Igniter, because it has a "Rails-esque" with an interesting approach to URL mapping.

Javascript is a powerful tool in the web programmers toolbox however, it's also one of our greatest headaches. Dealing with browser inconsistencies is always a source of great pain. You test on multiple platforms, find everyone you know with a mac running safari and think you have your code locked down however it rarely always works out this way. Being able to detect javascript errors in the wild can be a great resource for you to really see how your code is performing on a day to day basis.

The key to it is that it uses a global function that IE and Mozilla both have to create a global-level error handler for the page - "onerror". He shows you how, with a few simple lines, you can create the function (with an alert inside) and, together with a little bit of Ajax and PHP magic, write it out to an error logging script for review...]]> Mon, 02 Jan 2006 16:09:01 -0600