Thank you! Regarding to your question, the idea with DOMAssistant is to always return DOM references, i.e. with all native DOM methods as well.

The problem with web browser implemented code, such as getElementsByTagName, is that it returns a HTMLCollection instead of an Array, so it’s not as easy to extend as desired. Perhaps I should implement my own version of getElementsByTagName as well, for proper chaining support with often-used DOM methods.

To achieve what you want with DOMAssistant, in its current state, would be to do it like this:


var listItems = $("navigation").getElementsByTagName("ul");
var items = [];
for(var i=0; i items.push($(listItems[i]).elmsByClass("current", "li"));
}


One question, though. What if I’d want to reproduce these CSS selectors with your library?

#navigation ul li.current

If I’m not mistaken, there is no elemsByTagName in your library, and I can’t use the DOM default function getElementsByTagName if I want to preserve the chainable syntax.

Ideas?

Many thanks.

It depends on how you want to use it, but the AJAX module is very simple in that perspective. You can send in a URL with a query string to the AJAX call if you mean that you need several parameters to the server.

If you want any custom parameter when handling the actual response, it is better and recommended that you do that in the receiving function, e.g. through a parameter of a JavaScript object or a global variable.

I’m glad you took it the right way; I didn’t mean any offense!
It’s completely valid to link your name to your web site, it was just a mere reflection of what wa in the comment itself.

And, yeah, thanks.

Nevertheless, congrats on your latest release

No problem at all, it was good feedback!

Yes, your right… my “Quick look” was perhaps too quick

Kind regards,

Marc (Calm_Pear)

Thanks, I’m glad you like it, and that you find it simple and flexible!

What’s mentioned in the article is to avoid doing the XMLHttpRequest check over and over again, which is good advice. But if you look at my code, what’s returned from the first time I run it is then set as a property of the DOMAssistant.AJAX.

Consequently, it will only do that again if it has lost the reference or creation of the XMLHttpRequest; otherwise, it will just directly reference the object instance in the XMLHttp property of the DOMAssistant.AJAX object.

Regarding the Microsoft namespaces: I’ve been using those that have proven to be stable and solid over some time now, but I agree that in the long run Msxml2.DOMDocument.6.0 should be added to that list.

I had a quick look at the library and frankly, I like what I see. Simple and easy to understand code and quickly adjustable to my needs. I was especially interested in the AJAX bit and although the same clearness of coding exists I do think perhaps some things could be improved.
Check this article: http://www.dustindiaz.com/faster-AJAX/

And here’s what the MS guys think should be used for namespaces:
http://blogs.msdn.com/xmlteam...
i.e. MSXML2.XMLHTTP.3.0 or MSXML2.XMLHTTP.6.0 (scroll down a bit)

Keep up the good work!!

Thanks for the suggestion, and the perspective, although they are slightly diferent approaches.

Also, I still await a comment from you here without a link back to your or Yahoo’s code.

Comment update: My snappy remark maybe wasn’t called for here, and Dustin is a good JavaScript developer, no doubt. Check out his alternative if you find it interesting. I’ll leave my comment, though, since I don’t believe in suddenly and mysteriously disappearing comments in blog posts.