Monday, January 1, 2007

A few ideas came to my mind when it was idle over the weekend. (An idle mind is the devil's workshop!!?? :D )

What are the limits to which we can tweak the blogger template? I can't say for sure. Too much of anything is bad. If we have to modify the entire architecture of the template, then it is not worth pursuing that hack.

Anyway, here are the ideas. Discussion is open.

Idea #1: Seamless Asynchronism in Navigation
Let me be specific. Is it worth implementing the entire post section in a custom manner, and getting rid of the GML portions altogether?
Right now, I can't think of any way other than that.
I stumbled upon a slider based asynchronous navigation in one website. We can use similar stuff for the older posts and newer posts links. Rather than bringing up the results in a freshly loaded page every time, we can just load the posts section. I reckon that will be a mammoth change.

The idea of seamless navigation encompasses any page inside a particular blog.
We can very well modify the blog to load only the post section every time. Why? Answer is simple; we seldom have sidebar sections which change with the type of page (Item, Index or Archive)

Idea #2: Search Suggest
Aditya had created the Native Search Suggest hack which he just showed a trailer of, but never released. I bet it was one of the most anticipated hacks, but Alas!

If you ask me, the idea of Google Suggest is one of the best AJAX implementations ever.

This idea is again something which I stumbled upon while experimenting with Firebug. I saw the response of the AJAX requests sent by Google Suggest, which was in a very desirable function call format.

When I typed "suggest", the HTTP request sent was

GET http://www.google.com/complete/search?hl=en&js=true&qu=suggest
And the response text was
sendRPCDone(frameElement, "suggest", new Array("suggest", "suggest link", ...
(Truncated, as it is too long)

So it is just a matter of defining the function, sendRPCDone. (i.e., deciding what the function does.)
But there is a catch here too. There is an inherent feature of Gecko-based browsers (don't know about others) where XMLHttpRequests (known to common man as AJAX, although there is more to AJAX than XMLHttpRequest) to other domains are not possible. So you cannot get the results in this case. Can we do this without XMLHttpRequest? This is something to be investigated.

So, Aditya, if you promise you'll release your Native Search Suggest soon, then there's no need to pursue the above one ;)

0 comments:

Post a Comment

By :
Free Blog Templates