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
Read my post about how i tracked down the memory leak with morph(), it
should give you some tips on how to find out what is at fault. With so
many factors in your application you should first start to break it
down into smaller chunks to work out what is causing the increase in
memory
Yes it does, its just a toggle switch in the top menu, Aptana is
compiled against Eclipse 3.1 although it works in 3.2 i recommend
having a standalone copy of Aptana instead of trying to mix all the
different perspectives into one as there are some known conflicts.
While yes in this case it was
