As most of you are aware of, me and a small group of very talented people are working on our JavaScript library of choice, DOMAssistant, because we have a strong belief that light-weight code, fast and accurate performance, Unicode support and modularity is very important, and crucial for the future state of the web.
Two and a half years ago, I released the first version of getElementsByClassName. With how web browsers has evolved since, I thought I’d release a real ultimate version, dated 2008. π
A very common problem when people code JavaScript, is that they don’t take automatic type conversion into account. As a result, there are numerous weird errors and JavaScript is getting a lot of blame for being loosely typed. Therefore, I’d like to show you an easy way to avoid that problem.
DZone asked me to write an article about DOMAssistant, so I chose to give an introduction to how to work with element selection and especially different ways of making AJAX calls. Please read Making Element Selection and AJAX simple with DOMAssistant for more information.
Many people ask me how I choose to address an situation where all content in a web should be available without JavaScript, but certain parts hidden if JavaScript is enabled.
Ok, this is probably one of those publishings that will be a miserable failure, a crash-and-burn post. But hey, we learn from our mistakes, right? π
When YSlow was released to indicate how well a web site performed, there were a lot of people disappointed, and perplexed, by their own score. Overall, I think performance is underrated, so I thought I’d give you some short guidelines how to improve the performance of your web site.
We have just released a PictureSlides plugin for DOMAssistant, with which you can create picture slideshows, image presentations and also complete picture galleries.
There has been a fair share about JavaScript and event delegation, but since a lot of people doesn’t seem to have read it, I thought I’d re-iterate the point here. The more the merrier, right? π