Regarding jQuery, and other major JavaScript libraries: they definitely have a large community and there’s an abundance of plugins available. However, my hope is that having an efficient and fast core will, in the long run, provide the best ground to build on.

There’s a validation plugin to DOMAssistant in beta, so please try it out if you want to.

With ASK, it’s not being developed anymore, but feel free to tweak it to the needs you might have.

And also the links are taconite & jQuery taconite plugin.

Regards,
Shihan

Thanx for your quick response.

Never aware of DOMAssistant till now. Thanx a lot. Will definietly give it a try. But I think jQuery’s plugin-base is now so much stronger than DA, that the performance gain can be compromized for consistency and availablity of a large collection of ready to use codes. Particularly, I’ll wait for plugins like form, validate, tab & taconite in DA that I frequently use in my developed apps with jQ.

Another question, ASK’s history support is currently intended to remember just only the content that is added/changed in a single container by a single AJAX call. Is it possible to extend ASK’s history management (& also how much effort do you think is needed if possible) to remember multiple DOM changes that are performed in one or many containers through a single AJAX call (think about using taconite)? I’ll hope you are very familiar with taconite though FYI, with taconite architecture its very easy to to perform any kind of DOM modification as a result of a single AJAX call through a very manageable way that can be controlled from server side scripts. And also the links are…

Regards,
Shihan

Thanks! I haven’t really looked at this code in a long time, and I know IE can have some problems with repeated actions.

I think this should work fine side-by-side with jQuery, although I can’t guarantee it. Then, if course, I’d like to recommend that you take a look at DOMAssistant as well.

Do you think ASK can be integrated with with a jQuery based web app without any conflict?

One more thing, doing Back & Forward for a few times in IE7 for your demo page, breaks the history maintenance also the AJAX functionalities of links where as in FireFox 2 evrything was so smooth & functional. Not sure whether its a particular bug in IE7 or not but would be nice to have it fixed (if possible).

Hats off again for your great work.

Regards,
Shihan

Great!

Hmm, that’s a tricky question. If I understand you correctly, you have ASK links within the new content you retrieve with ASK? And that works as long as you move forward, but if you use back, no events are applied?

I tried that out and your description is correct. What you can do, which should work, is to add one line in the code:

Line 108, you will find this code:

document.getElementById(strElmToRemoveContentFromId).innerHTML = this.links[intLinkIndex][2];

After that, add this line and events should be applied again:

this.addEvents(document.getElementById(strElmToRemoveContentFromId));

This is, however, experimental and I can’t guarantee that it works consistently.

You have done a great job with this lib.
However, I encounter the following problem :
I setup useSameTargetForSeveralCalls to true, when a page loaded thru ask is put in the target div, the links inside this page with the ask class name works fine. But when I press the back button of the browser, the previous page loaded thru ask with some links inside isn’t handle anymore by ask. The onclick event isn’t added any more.
I tried to look thru the code but I don’t find how to apply again AskAddEvents…

Absolutely, but it’s not supported in the core script, so you need to tweak it yourself.

Thanks.

Thank you, I’m glad you like it!
That is valid input, and something I should look into. At the moment, unfortunately, I don’t have the possibility to put any more time into ASK (although I’d definitely like to). However, a tweak like that sounds fairly easy if that property is set to true, so maybe it can be easily fixed.

Just not now, though.

Regarding your problem with the navigation: if you have ASK functionality to replace already existing links with new ones, i imagine you might run into problems. I guess the thinking is somewhat reversed; if you have ASK links, why replace them with new ones with the same functionality?

To answer the question: replacing existing ASK links with new ones probably won’t work.

I’ve tried ASK generally in IE 7 myself, with the native support, and it works as intended. I guess it’s something with your specific scenario that unfortunately breaks the desired functionality.

I’m sorry I can’t help more.

And concerning the bookmark problem I think I found a workaround:
I just change in line 93 i=0 to i=arrLinkIndexes.length-1.
I don’t understand much JS, so I dunno if this brings up any new bugs, but at least in firefox it seems to work quite nice!
It loads the first page once and than the right one.

Thank you!
The way it works, it adds the number to the URL for each click on a link, no matter if that link has already been clicked. This is for forward and back navigation to work properly, but unfortunately it will affect bookmarking they way you describe.

As of now, I’m not sure how to address that.

really nice JS library. I only have one problem with it, I have several links that target one div and I set this.useSameTargetForSeveralCalls=true, but when I browse through my pages the URL looks like this: foo/#1:3:1. When I boomark the page and go to that bookmark, it loads 1, then 3 and then 1 rather than just the last one. Any way to fix this?

Thanks