Its about time - Webkit - the development version of Safari, has gotten a real javascript debugger. Its called Drosera, and the Surfin Safari blog has the announcement. Or you can just download the latest nightly of Webkit and go. Its interesting to note that this and the Web Inspector tool for Safari are about 90% plain HTML and Javascript. Hows that for a something that isn’t even a ‘real programming language’? | Read the rest »
via ajaxian (of course); I thought this might tie in to our previous conversation on accessibility.
Max Kiesler has produced another mega-list of Ajax links. This time it’s 40 Ajax accessibility tutorials and articles.
AJAX is a great tool for creating rich internet applications, however, when improperly implemented it can cause hugh accessibility issues. The good news is that most of these issues can be fixed so your websites are viewable by a much wider audience. Great resources on accessibility have been around for years, however, many web 2.0 and AJAX websites ignore all of the research that went into turning website accessibility into a movement followed by most professional web developers. Below you’ll find a list of 40 best AJAX accessibility tutorials and articles that I have found on the web in the last year.
With Max’s permission (and following our respective CC licenses), I’ve been wikifying his links at AjaxPatterns.org, so you can add your own resources too. Here’s the wiki version of the Accessibility links and list of all links pages.
Update: EBA have been researching this topic too and just released a podcast on Ajax Accessibility.
via ajaxian; who wouldn’t love a little slickness in the javadoc?
All Java developers can spot the look and feel of JavaDoc a mile away. The new JavaRef (developed with the Apache Tapestry Java web framework) aims to give you another take, allowing you to search JavaDoc of over 80 projects. | Read the rest »
via ajaxian… I know I’ve done a lot of little projects on my own where managing files has been a bit of a pain. We don’t run php here, but I still like the looks of this little application. | Read the rest »
Here’s a little utility I’m releasing for you sportsfans out there. After much wailing and gnashing of teeth, it would appear to be leak free. So what is it?
UPDATE This is now released for Mootools 1.0.
popupdetails.js makes a little DHTML layover when the user clicks or mouses over an element, generally to provide more detailed information for that item. It makes use of moo.fx to fade in and out (slick!) and it uses an iframe shim to obscure select elements and the like so they don’t poke through.
| Read the rest »
Ok. So in my previous posts I talked a lot about various ways to detect javascript leaks, what often causes them, etc. I have to libraries that are leaking, both of which use Objects that are instantiated and reference, in one form or another, elements in the DOM.
I've fixed my memory leaks in my popup handler (which I'll post about in a sec) but not yet in my toolbar script (which manages to leak in Firefox if you can believe it). My popup handler leaked for two reasons: circular references and closures. | Read the rest »
Continuing in my efforts to make my code stop leaking (fun!), I've been working on a popup handler I wrote recently (which I plan to post and share as soon as, you know, it doesn't leak). | Read the rest »
via Ajaxian: this is a somewhat old post, but this short (3min) screencast was useful in my on-going memory leak quest. Just watching it I better understand the problem and realize that previous code I've written will require some refactoring. | Read the rest »
It's been a while since I last posted. Partly because I haven't seen anything super interesting and partly because I've been heads-down on something super-duper secret. I'll post on it when I'm good and ready.
The super secret thing I'm working on has a problem: it leaks. It leaks in Firefox, which I'm told is a rare thing. I feel special. I emailed my pal Alex about it; he's an old friend who happens to have unstoppable code kung-fu and he always seems to have something to share that's worth listening to. He writes back regarding my javascript memory leak with this pearl of wisdom that probably would have taken me a long time to figure out: | Read the rest »
via Ajaxian (of course):
Developers all over the web are discovering the powerful new features that using Ajax lets them implement. Unfortunately, there's also a downside for some people associated with the web, namely advertisers, and how Ajax works. In this new article on the ClickZ Network, explores how Ajax can wreck havock on any normal "counting" system.
I've been very vocal about the AJAX counting issue; I've written several articles, spoken on panels, and pushed the IAB to update the impression guidelines on a very fast timeline. There's been interest and response, and the IAB is beginning to act. But everyone involved in the process realizes this will take time. So today, my recommendations for how developers of AJAX Web pages and software applications that include advertising can deal with the unique counting issues. There are no guarantees. Final guidelines may differ from my guidance. But, I'll put this stake in the ground. Let's see if we can't pivot around it.
He points out the main issue, namely that Ajax goes around the standard "just HTML" navigation model and can cause much less distribution of an advertiser's placement. He does have a suggestion or two, however - deploying new Ajax-equiped versions of sites, modifying the existing architecture to support an Ajax-related model, or just avoiding the use of Ajax all toegther.
His personal suggestion? Make sure Ajax is really the way to go with your application (as it pertains to getting advertising messages across) before making any kind of leap.