We've been using Exhibit for about a year now and continue to find it
a robust and elegant solution. However, like most of us, I'm trying
to squeeze every last drop of performance out of the tool. Initially,
we were loading the JS libraries & resources from either the mit or
simile-widgets domains. However, some months back I deployed those
resources on our internal web server and made the appropriate changes
in our pages.
Profiling the performance of our pages now with Firebug, I still see
about 20 GET requests to
api.simile-widgets.org for the following
resources:
simile-ajax-api.js
simile-ajax-bundle.js
signal.js
graphics.css
timeline-api.js
timeline-bundle.js
timeline-bundle.css
labellers.js
timeplot-api.js
timeplot-bundle.js
timeplot-bundle.css
On our webserver, I have:
simile-exhibit directory including exhibit-api.js, exhibit-bundle.css,
exhibit-bundle.js, manifest.json files and the following populated
subdirs:
extensions
images
locales
scripts
styles
I can see that many of those "local resources" are getting loaded.
How can I eliminate the remaining calls to
simile-widgets.org?
I did try to use this document as a guide:
http://www.simile-widgets.org/wiki/How_to_use_Exhibit_offline#Preliminaries
However, I was unable to get it working and noticed that it still
references the old
mit.edu domain.
Thanks for suggestions,
-Mark