[Rails-spinoffs] Re: Element.setStyle a resource hog?

2007-02-18 Thread Mislav
Wouldn't it make even more sense for instance to skip doing all these checks? How? By dynamically compiling different versions of those methods based on the capabilities of the browser running them. ;-) Well, duh! ;-P see http://dev.rubyonrails.org/ticket/6696 I agree that we should move

[Rails-spinoffs] Re: Element.setStyle a resource hog?

2007-02-18 Thread Martin Ellis
The quote you made, was not from myself. I dont believe that the web server should decide how to serve the javascript. As for optimisations, you use include alot, its incredibly expensive to use that function when just looking for 2 items in array. I was doing some tests, and the cheapest way

[Rails-spinoffs] Re: Element.setStyle a resource hog?

2007-02-17 Thread Marius Feraru
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Malard wrote: One of the first things that strikes me is that on every call we're finding out what version of the browser we're in. Which is an already well known pile of crap. Any user-agent based validation is feeble, but for one reason (or