I think most developers around ASP.net and visual studio want some form of Ajax functionality that can be easily implemented using webforms and the visual designer. We don't all need web service functionality in the browser. Is there any way that the Atlas team can look at componentizing the javascript libraries even more?
If we could get Ajax functionality and visual effects (think the Prototype and Scriptaculous libraries) in under 100K or so, then I could consider using Atlas. If Atlas just continues to balloon in size, asp.net developers will continue to have to struggle to implement Ajax via WebForms and Visual Studio.
I want to thank you for your continued work though. Please just remember that bandwidth is not unlimited.
wwahammy wrote:
If we could get Ajax functionality and visual effects (think the Prototype and Scriptaculous libraries) in under 100K or so, then I could consider using Atlas. If Atlas just continues to balloon in size, asp.net developers will continue to have to struggle to implement Ajax via WebForms and Visual Studio.
The weight of full Atlas cient script library in it's release version is only 178 kilobytes (it is /ScriptLibrary/Atlas/Release/Atlas.js).
Related topic:http://forums.asp.net/1165332/ShowPost.aspx
If you use gzip compression on the static .js file, the full Atlas library is ~37k. Note that this is cached on the client forever, and is only downloaded once per site.
AtlasRuntime.js is about 12k in size if you want just the core features.
Hope this helps,
Scott
? gzip compression on the static .js file
how do we do this?
I'm curious how the Atlas engine knows which directory of the ScriptLibrary to get the files... is it simply based on the Web.Config's "compilation mode" property, or is there more to it than that?
erdsah88:
? gzip compression on the static .js file
if i recall correctly, there's a module that does that (WebResourceCompression is its name, i think). take a look at the tipical atlas web.config file and you'll see what i mean...
No comments:
Post a Comment