JavaScript

BeYou Pledge Widget Test (devel)

Canogle Widget Test

this is just some regular HTML page

It contains a specific DIV with the id canogle-art

What if there was no IE6?

Recently I have been fighting IE6 again, and it never stops to amaze me how it can ruin my day. So I thought I link to this article/blog on ajaxan.com which speaks to this piece of $#@%!$@ software.

IE keeps giving ...

A friend just told me a nice little "easter egg" of IE6 that is doggone hard to debug when one doesn't know about Redmond's little secrets plot to make a web developers life hell (me conspiracy theorist? never!)

Turns out that IE6 has a css file limit per page that kicks in with the 32nd file, where it simply doesn't seem to read the contents of the file. And if you are mindful of this and slap all your CSS into less than 32 files, the beast still gets you by the nuts because there also is a total CSS size limit.

Go do yourself a favor and download firefox ....

No votes yet

jaxer

This seems really interesting

jquery href hover

Contrary to what you can find on the web, when trying to set the window.status when hovering over a link, you need to return false at the end of the hover function, otherwise the standard mouseover event is going to kick in overwrite your window.status

The following jQuery works

$('a').hover(function(){window.status=this.title?this.title:'';return false;},function(){window.status='';return false;})

If you return true, the window status is going to display the URL instead, which is the standard.

Your rating: None Average: 2.5 (6 votes)

Prototype callbacks and this keyword

Trying to encapsulate programming logic into objects, I hit a snag when dealing with event callbacks in javascript. Using the prototype library I use the Object.extend method to create my own objects, which contain their own event handlers. When the event handler fires, the reference to the object instance has been lost, however, so the code does not work anymore.

The gentleman in this blog entry found the solution: the callback needs to be passed as event listener like so

this.callback.bindAsEventListener(this)

and all is well.

Hybridizing Java

A very thoughtful 'article' by Bruce Eckel about the state of affairs of 'the Web'

COMET - the next stage of AJAX

quoted from the article


Regular Ajax improves the responsiveness of a UI for a single user, but at the cost of allowing the context to go “stale” for long-lived pages. Changes to data from others users is lost until a user refreshes the whole page. An application can alternately return to the “bad old days” and maintain some sort of state mechanism by which it tells client about changes since the last time they’ve communicated. The user has to either wait until they preform some action which would kick off a request to see the updated state from other users (which might impact the action they wanted to preform!) or request changes from the server at some interval (called “polling”). Since the web is inherently multi-user, it’s pretty obvious that regular Ajax imposes usability and transparency hurdles for users. Applications that employ the Comet technique can avoid this problem by pushing updates to all clients as they happen. UI state does not go out of sync and everyone using an application can easily understand what their changes will mean for other users. Ajax improves single-user responsiveness. Comet improves application responsiveness for collaborative, multi-user applications and does it without the performance headaches associated with intermittent polling.

Comet: Beyond AJAX

quoted from the article


Comet application fight lag by avoiding HTTP and TCP/IP set-up and tear-down and a single connection is re-used. But the big kicker for AJAX is polling latency which Comet avoids. The big takeaway: transfer only the necessary data, exactly when it’s most relevant.


There are two implementation techniques: Long-polling where you reconnect after every datagram. This is simple to implement with XmlHTTPRequests. Another method is to use multi-part XmlHTTPRequests. This works differently on IE and Firefox and doesn’t work on Safari. No known system does this portably today.

Syndicate content