#45 ✓resolved

Improve initial loading speed

Reported by sebastian | July 10th, 2008 @ 09:28 AM

The Script.aculo.us-library consists of 7 separate files, which, even if reduced to less files than that, makes downloading the library more time-consuming, as for each and every file, the server latency has to be taken into consideration.

Additionally, the files are transmitted uncompressed, which could reduce download speed, too.

My proposal is the following:

Offer the library in a different way:

1. Offer the different available combinations of the library as complete files (everything in one file).

2. Offer the files both compressed and uncompressed.

The compression should of course not include the license notice and should include a link back to the script.aculo.us-site.

Mootools offers that, and for time-conscious developers, the less than optimal way script.aculo.us is loaded is definitely a reason to choose one library over the other.

Comments and changes to this ticket

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

script.aculo.us is an open-source JavaScript framework for visual effects and interface behaviours.
<br/><b>Source available from github</b>
The Git repository resides at:
<a href="http://github.com/madrobby/scriptaculous">http://github.com/madrobby/scriptaculous</a>
<br/>Check out the current development trunk with:
<code>git clone git://github.com/madrobby/scriptaculous.git</code>
<br/>As <b>script.aculo.us 1.xx is feature-frozen</b>, this development trunk is for <b>bugfixes only</b>.
<br/>New development should happen only for
<b>script.aculo.us 2</b>.
<br/><b>Creating a bug report</b>
When creating a bug report, be sure to include as much relevant information as possible. Post a an example that shows off the problem. Preferably, <b>alter the unit tests</b> and show through either changed or added tests how the expected behavior is not occuring.

People watching this ticket