I've been tasked with speeding up a web 2.0 application based on ExtJS 2.2.0 that contains several routines that take up quite a bit of time and, because IE6's javascript processing engine is less than stellar ((In other words, it sucks pretty bad.)), I needed to find a way to "speed things up".
javascript
Debugging an application today before launch I noticed a problem where it seemed to be parsing a specific time value (0900) incorrectly as (12:00 AM or ‘0000’). During my search I ran across this oddity with the parseInt function of Javascript. Apparently parseInt can also work with different base notations […]
parseInt gotchas
Today I had an interesting task of figuring out why a piece of code I’d written a few weeks ago for autosaving user changes wasn’t being called as uniformly as we’d thought. That is, on IE6 and FF, we were seeing a particular piece of code take almost twice as […]
Web browsers and time
Although it only works in Chrome and FireBug, I’ve found console.log() to be an extremely handy tool for debugging javascript without having to step through code. Here’s a bit of code I’ve found handy to make sure browsers without console.log don’t bomb out in case you forget to take your […]
Console.log is your friend
I recently ran into a situation where I needed to know how many Monday’s were in a given month via javascript and figured I would make the function (which depends on Date extensions by ExtJS) for it available here in case anyone else runs into the same problem. /* * […]