But if you're using all these new fangled groovy webby bits then it should already be part of your suite of bits that get installed.
If you are just using them for one little display box then there is definitely too much overhead.
I think the reason that there are many toolkits is that this sort of technique is just making itself apparent, and many people are developing their own bits. I have a nice layered effect that I use when submitting a form that I know would take a while for the server to process. Can you say WebQuerySave? All it does is throw up a nicely formatted "please wait" in the centre of the screen on submit.
It's all about usablity. These scripts give us great ways of enhancing the various applications we are developing. Some are good. Some are bad. Some are downright weird. Providing it doesn't break the function of the application when the user does silly things (reload, back etc.) then use whatever floats your boat.
110KB is a hefty overhead.
But if you're using all these new fangled groovy webby bits then it should already be part of your suite of bits that get installed.
If you are just using them for one little display box then there is definitely too much overhead.
I think the reason that there are many toolkits is that this sort of technique is just making itself apparent, and many people are developing their own bits. I have a nice layered effect that I use when submitting a form that I know would take a while for the server to process. Can you say WebQuerySave? All it does is throw up a nicely formatted "please wait" in the centre of the screen on submit.
It's all about usablity. These scripts give us great ways of enhancing the various applications we are developing. Some are good. Some are bad. Some are downright weird. Providing it doesn't break the function of the application when the user does silly things (reload, back etc.) then use whatever floats your boat.
My boat currently floats on prototype.js.