Slashdot Mirror

I spent a lot of time between '99 and '02 developing an DHTML toolkit (example). In the summer of 2002 I started working on a rewrite of the widget toolkit, and ultimately created something else - Engine. I wrote an article about the decisions that lead me from the widget-heavy MDI toolkit to service and component orientated Engine toolkit: The Separation of Functionality from Content. Dojo, and the other toolkits that are pretty similar to it, have a lot of neat aspects and very clever widgets. However, there are a lot of corner-cases when dealing with managing events through the DOM and script, and its very easy to miss those situations. I think the Dojo foundation is doing some good work, but, the examples I've seen where Dojo has been implemented has left something to be desired. Also, after refining my approach and using it in high traffic areas (particularly the Web Analytics and window component) I've found it to be much easier to maintain and add/remove as the situation warrants.

I spent a lot of time between '99 and '02 developing an DHTML toolkit (example). In the summer of 2002 I started working on a rewrite of the widget toolkit, and ultimately created something else - Engine. I wrote an article about the decisions that lead me from the widget-heavy MDI toolkit to service and component orientated Engine toolkit: The Separation of Functionality from Content. Dojo, and the other toolkits that are pretty similar to it, have a lot of neat aspects and very clever widgets. However, there are a lot of corner-cases when dealing with managing events through the DOM and script, and its very easy to miss those situations. I think the Dojo foundation is doing some good work, but, the examples I've seen where Dojo has been implemented has left something to be desired. Also, after refining my approach and using it in high traffic areas (particularly the Web Analytics and window component) I've found it to be much easier to maintain and add/remove as the situation warrants.

I spent a lot of time between '99 and '02 developing an DHTML toolkit (example). In the summer of 2002 I started working on a rewrite of the widget toolkit, and ultimately created something else - Engine. I wrote an article about the decisions that lead me from the widget-heavy MDI toolkit to service and component orientated Engine toolkit: The Separation of Functionality from Content. Dojo, and the other toolkits that are pretty similar to it, have a lot of neat aspects and very clever widgets. However, there are a lot of corner-cases when dealing with managing events through the DOM and script, and its very easy to miss those situations. I think the Dojo foundation is doing some good work, but, the examples I've seen where Dojo has been implemented has left something to be desired. Also, after refining my approach and using it in high traffic areas (particularly the Web Analytics and window component) I've found it to be much easier to maintain and add/remove as the situation warrants.

I spent a lot of time between '99 and '02 developing an DHTML toolkit (example). In the summer of 2002 I started working on a rewrite of the widget toolkit, and ultimately created something else - Engine. I wrote an article about the decisions that lead me from the widget-heavy MDI toolkit to service and component orientated Engine toolkit: The Separation of Functionality from Content. Dojo, and the other toolkits that are pretty similar to it, have a lot of neat aspects and very clever widgets. However, there are a lot of corner-cases when dealing with managing events through the DOM and script, and its very easy to miss those situations. I think the Dojo foundation is doing some good work, but, the examples I've seen where Dojo has been implemented has left something to be desired. Also, after refining my approach and using it in high traffic areas (particularly the Web Analytics and window component) I've found it to be much easier to maintain and add/remove as the situation warrants.

I spent a lot of time between '99 and '02 developing an DHTML toolkit (example). In the summer of 2002 I started working on a rewrite of the widget toolkit, and ultimately created something else - Engine. I wrote an article about the decisions that lead me from the widget-heavy MDI toolkit to service and component orientated Engine toolkit: The Separation of Functionality from Content. Dojo, and the other toolkits that are pretty similar to it, have a lot of neat aspects and very clever widgets. However, there are a lot of corner-cases when dealing with managing events through the DOM and script, and its very easy to miss those situations. I think the Dojo foundation is doing some good work, but, the examples I've seen where Dojo has been implemented has left something to be desired. Also, after refining my approach and using it in high traffic areas (particularly the Web Analytics and window component) I've found it to be much easier to maintain and add/remove as the situation warrants.

I spent a lot of time between '99 and '02 developing an DHTML toolkit (example). In the summer of 2002 I started working on a rewrite of the widget toolkit, and ultimately created something else - Engine. I wrote an article about the decisions that lead me from the widget-heavy MDI toolkit to service and component orientated Engine toolkit: The Separation of Functionality from Content. Dojo, and the other toolkits that are pretty similar to it, have a lot of neat aspects and very clever widgets. However, there are a lot of corner-cases when dealing with managing events through the DOM and script, and its very easy to miss those situations. I think the Dojo foundation is doing some good work, but, the examples I've seen where Dojo has been implemented has left something to be desired. Also, after refining my approach and using it in high traffic areas (particularly the Web Analytics and window component) I've found it to be much easier to maintain and add/remove as the situation warrants.

The article describes another form of clickstream analysis. However, I wonder whether user behavior couldn't also, and perhaps better, be identified by content interaction. There are a number of products that show Web page heatcharts ostensibly to identify layout problems. But there are not many products that show what a person actually did on a page. The article used sample data for a year, but I wonder how much of that data was skewed by changes in content layout and promotion. For example, I monitored the behavior on several Web pages with a consistent layout for three years and can show clear behavior patterns by content type (Identifying Behavior by Content Type). I think individual behavior on a given page with a particular type of content might also be useful in identifying particular users.

It kind of tracks your movements. I have a monitor that does track device movements in addition to interactions, much more so than this kind (I do give them that they have better reports).

I've always liked my own AJAX framework, Engine for Web Applications, but it never seems to make it farther than the appendices (if even) - here are some good toolkits, see appendix A for some other stuff that showed up in Google.

On the framework topic, I've been working on one with AJAX support since 2002: Engine for Web Applications (Example). The XML utility also exists standalone as libXmlRequest, and includes both request object and response content caching.

On the framework topic, I've been working on one with AJAX support since 2002: Engine for Web Applications (Example). The XML utility also exists standalone as libXmlRequest, and includes both request object and response content caching.

On the framework topic, I've been working on one with AJAX support since 2002: Engine for Web Applications (Example). The XML utility also exists standalone as libXmlRequest, and includes both request object and response content caching.

For the do it yourself crowd, I wrote a short article on how Web developers can create custom passive monitors using a library I wrote. I haven't yet posted the other individual parts that make for a complete solution, but this is an easy way to get started with the passive client-side monitor.

You can load a javascript file from another domain, and send data to other domains via the ages-old image request piggyback. The javascriptfile in this case is loaded in the same domain and scope of the page itself. Most browsers have extra rules and conditions pertaining to cookies created by third-party resources like this. If anyone wanted to use the service but were concerned about the origins of the script, they could download it and host it on their own server while still sending the data back to Google. I think the previous poster was alluding to Web spyware, or behavior monitors.