Those crazy guys at mad4milk.net have added a bit more to the moo.fx library. Now, in addition to their animation library, prototype-lite, and ajax-lite scripts, they’ve added a 3kb selector library: moo.dom
Archive for April, 2006
I think this is something we should seriously consider here at CNET.
Would you want to do this? Maybe as part of a usability testing framework?
He has one PHP file that does both the error writing, and also acts as the script xsrc= to capture errors:
… ajax call back to the server log …
Google Calendar has launched in beta, and it has a lot of great Ajax in it.
It feels like GMail and Google Reader, and has great performance.
There are some nice patterns, such as highlighting elements in yellow means that you can click to go into edit mode on that element. If you click on a date, the textual representation changes to become a date picker. Read the rest of this entry »
Last night I went down to Google for Bill Scott’s presentation on Designing for Ajax and I’m glad I went. I can’t say that I learned a lot but his presentation was the most thorough and well rounded argument for spending time getting client side behaviors right.
Creating this stuff with all the slick interactive and animated features is no picknick. But making elements interactive and intuitive can provide big windfalls in usability. Read the rest of this entry »
I’ve been working on a little project that involves creating some tools for any of CNET’s sites including our back end tools. I’ll post more on the project when it’s presentable, but in the process of working on this I have, of course, run into questions about cross domain security brick walls and how to transport portions of the data to create a consistent and persistent experience for the user.
Here are a couple of articles that I’ve found that I think could be useful:
Mashup Data Formats: JSON versus XML
This is a nice article outlining from a fairly objective perspective the differences between these two data formats/transport systems. They both have advantages and disadvantages, but it’s helped me understand when to use one vs. the other and how to get around certain problems by making the right choice at the right time.
The Case For JSON: What Is It and Why Use It?
Another article on why to use JSON that’s a little more detailed. This fellow definitely has his mind made up, so he’s not really going into xml’s positive aspects so much, but he does a great job of shining a light on JSON.
Look Ma, Cross-Domain Scripting!
Same author as the previous link but focused on one of JSON’s biggest assets: it’s ability to get across domains. It’s tricky stuff, and it’s not clear to me how to make the data go both ways (to and from a foreign server), but it has some useful code snips and demonstrations on how do do some of it.
via Ajaxian; new to Ajax? want to use Prototype to handle all the work? Read on!
via Ajaxian – I wonder if there’s a performance difference between using DWR and JSON:
Speed is everything when it comes to online applications. Users hate to sit and wait, especially the experienced ones. A few seconds pass and they start to think something’s broken. Knowing this, optimizing everything you can on your application can mean the difference between someone leaving or sticking around to explore the site more. One method for enhancing the speed in your app is described here on Builder.com – using JSON to speed up your Ajax script’s connection between it and the server.
Fortunately, there’s a better way.
The article introduces JSON to the reader, offering a comparison with a matching XML structure. Their point of view is that XML is great for marking up data, but JSON is meant for the speed of data exchange. There’s an example provided of the difference between the same request done in both XML and JSON, with the JSON seeming to be the simpler. The article finished off with a look at how reliable JSON is for your application, and some mention of life on the other side – the server-side functionality.
I just found this article on the Scriptaculous Effect Queue and I’m sold. I’d been meaning to really dig into this library and wrap my head around how best to use it, if at all. Basically Scriptaculous is a visual and interface effects library. It features the tools for doing lots of snappy looking fade in, drop in, scroll out, etc. effects and also effects useful for data entry and interactivity (drag and drop, live search, etc.).
One problem encountred when putting these types of effects together into strings of animations and the like is that you can have various things collide. Enter the Effect Queue:
A queue is a list of events (in the current context Effects). These events take occur one after the other (or parallel) for the purpose of preventing disturbence of current actions.
I’m not geek enough to tell whether this article‘s points are credible enough or not (I’m just the design guy), but I thought I’d pass it along just in case.