HTML_AJAX 0.4.0 is released

HTML_AJAX 0.4.0 has been released. You can upgrade using the PEAR package manager in the normal ways.

The biggest new feature is the addition of a setInnerHTML method that runs any JavaScript in the string your using to update and elements innerHTML property and the addition of an ordered queue. The ordered queue makes your AJAX requests return to the client in the same order they were sent. One of the biggest area’s this comes into play is when creating livesearch implementations or any other time you’re making lots of AJAX requests and overwriting the results of the earlier ones with the results of latter ones.

More details (including a place to put testing results for your browser of choice) are available in the release notes on the HTML_AJAX wiki.

I’d also like to thank Laurent Yaish for helping with the testing of this release and Arpad Ray for working with me until we got the optimal implementation of setInnerHTML.

7 thoughts on “HTML_AJAX 0.4.0 is released”

  1. Pingback: php tidbits? » a week in phpworld #1

  2. Pingback: HTML_AJAX 0.4.0 is released (PEAR Package) » - techvolution (technology evolution)

  3. Got a Q though.
    Since HTML will eventually be deprecated to evolve into pure XHTML, and innerHTML doesn’t work outside the HTML-DOM, is this set of functions still relevant?
    I’ve decided to go with XHTML all the way, for all my applications, cause that’s really the only way to go (certainly for applications – maybe I’ll use the HTML doctype once or twice for a “regular” website again).

    innerHTML doesn’t work in XHTML-documents, right?
    I’m convinced this framework is a great toolset if you’re into HTML, but it’s not the way to build ajax-enrichened apps for the future, I believe.

    Please comment, correct me if I’m wrong.
    Perhaps the mere name of the framework “HTML_AJAX” says enough: it’s only for HTML-documents…

  4. Kenneth:
    First i doubt HTML will ever be deprecated, in a lot of ways XHTML is just a pain to work with and adds very little value unless your creating it from some other XML file.

    On your decision to go all XHTML I feel for you, it doesn’t work all that well in IE and you have the whole mess content-type mess to deal with.

    innerHTML is an extension to the DOM so im guessing you’ll see innerHTML support in XHTML documents as new browsers versions are released.

    That being said, you can use HTML_AJAX without using innerHTML, there are just some handy functions like replace etc, you can’t use.

  5. Hey,

    I appreciate the comment but we’ll see how it turns out. I’m not so confident the w3c will adopt innerHTML into the DOM any time soon. since the whole idea of ajax isn’t fully adopted yet but probably will be at some point, you might be right too.

    However, I see a bigger future for xhtml than you do. we will all have to move to xhtml if the web is to live on and keep growing without loosing the ability to control it (searching, indexing, you know what i mean). I believe the mess we all have made in the past HAS to be cleaned up.

    As i said, we’ll see. Thanks for the feedback. And thanks for “feeling for me” 🙂

  6. Kenneth:
    The thing to remember is that the w3c doesn’t matter

    If all the big browsers support something its a stand, and at some point the w3c will wake up and add it too the spec, look at XMLHttpRequest

  7. A great AJAX tool, but for the Eclipse environment! Enhanced support in MyEclipse 5.0.
    Unfortunately, doesn’t solve the IE issues – that’s Microsoft’s problem. 🙂

Comments are closed.