[
https://issues.apache.org/jira/browse/VCL-505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Thompson updated VCL-505:
------------------------------
Fix Version/s: 2.3
> Dojo is slow to load, especially on pages with many ancillary class files
> -------------------------------------------------------------------------
>
> Key: VCL-505
> URL: https://issues.apache.org/jira/browse/VCL-505
> Project: VCL
> Issue Type: Improvement
> Components: web gui (frontend)
> Reporter: Aaron Coburn
> Priority: Minor
> Fix For: 2.3
>
> Attachments: utils.php.patch, vcl.profile.js
>
>
> Dojo has a dynamic loading mechanism with the dojo.require("...") function.
> This is very convenient for developers, but for web users, this requires, in
> some cases, dozens of extra GET requests to load the ancillary javascript
> libraries.
> With this in mind, I would recommend looking at the Dojo custom build
> framework at:
> http://dojotoolkit.org/reference-guide/quickstart/custom-builds.html
> This allows a developer to create custom javascript libraries that contain
> all the needed code for a given 'profile'. I have done this for our
> installation of the VCL, and it results in a dramatic improvement in load
> times for individual pages.
> This change requires changing the .ht-inc/utils.php file. I have attached a
> sample patch (based on version 2.2.1).
> This also requires building a custom dojo environment which can be done by
> first downloading the full dojo SDK, and then creating a vcl 'profile' in
> dojo-release-x.x.x-src/util/buildscripts/profile (i.e. vcl.profile.js). The
> custom files can be generated by issuing the following commands:
> $ cd dojo-release-x.x.x-src/util/buildscripts
> $ ./build.sh profile=vcl action=release
> (I first added the vcldojo files to the dojo directory so that the
> TimeTextBoxEnd class could be included in the package).
> I have also attached the vcl profile I used. The names given to each 'layer'
> correspond to the changes in utils.php.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
