good stuff indeed
i know that Julian had a proof of concept working a while ago now too
(but because there was so much involved with getting ajax set up and it was new,and it would compete wtih WDL, it went no further
I was doing a bit of a refresher on Ajax a couple of weeks ago and whilst it does have some promise, it’s not all plain sailing…if the information I found was to be believed and I have no reason to suspect that it was intended to be misleading.
Unfortunately I seem to have forgotten to bookmark a page which listed a number of issues, so I can’t recall all of them. I’m fairly sure that one significant area was browser compatibility.
The issues I saw led me to conclude that Ajax wasn’t (yet) a suitable tool to use for what I wanted to do.
I would agree with you except that 97% of my visitors can use Ajax. If only PHP detected javascript enabled, I could easily take care of the other 3%. I’ll have to find a workaround instead (like having the ability to disable Ajax, which I’ve already encorporated).
It wasn’t simply an issue of scripting being disabled. If I remember correctly there are some browsers which have ‘broken’ versions of Javascript which have a range of problems with Ajax sites, others where the Javascript processing is very slow if you have large Javascript files and there also appeared to be a range of other problems, many just minor irritants/cosmetic issues. Ajax is pretty new, so it’s to be expected that it’s got issues. Maybe some of the problems I saw have already been fixed…with others probably introduced as well!
I just want to point out that this script is no new wdl, it is just a small javascript to change some value’s on a page using the clientraw.txt-file like on Tom’s and Julians page
Great stuff, Pinto and Tom! Thanks for showing us examples with your pages.
I found that updating pages realtime with clientraw.txt will sometimes yield zeroes for results… probably trying to access the clientraw.txt just when it was being ftp’ed, so I’d recommend putting in a small check to see the field[0] contains ‘12345’, and if it doesn’t, wait a second or two and try the access again. That fixed issues I’d had with Anole’s wxsticker sometimes displaying a data that wasn’t correct.