Hi Will,

It's possible to build something like exhibit_timeline_en.js, and indeed 
I have thought of it before. I remember wanting to serve "distributions" 
at such URLs as this one

    http://simile.mit.edu/exhibit/api-2.0/dist/exhibit_timeline_en.js

But I never got around to it because there wasn't enough demand. So, you 
need to download the Exhibit code base, add an ant target in build.xml, 
and build the distribution yourself. Unlike the target that build 
exhibit-bundle.js, you need to include
- a distribution of the Simile Ajax API
- a distribution of the Timeline API
- the subset of exhibit-api.js that doesn't do any further script 
loading (but does style loading)
- the script files (same as those included in building exhibit-bundle.js)
- the locale files
- the script files of the Timeline Exhibit extension

Careful--as both Timeline and Exhibit needs Simile Ajax, watch out that 
Simile Ajax doesn't get included twice in the Exhibit+Timeline 
distribution. Let me know if you get it to work.

Cheers,

David

Will Moffat wrote:
> Hi,
>
> Exhibit is great! I'm playing around with using Freebase data and I'm
> really impressed so far.
>
> I'd like to be able to load Exhibit dynamically since I'm using
> templates and I don't know if the user has included a timeline or not.
> I've hit two problems:
>
> * Safari loads scripts out of order and so Exhibit fails to load. See
> this test page:
> http://mqlx.com/~willmoffat/learn_feature/exhibit/test_dynamic_loading.html
>
> * time-extension.js does not support the callback parameter, so I have
> to poll until it's loaded. That works but it's ugly.
>
> Is it possible to build one giant exhibit_timeline_en.js file? That
> would solve these problem and load quicker.
>
> regards,
> --Will
> _______________________________________________
> General mailing list
> [email protected]
> http://simile.mit.edu/mailman/listinfo/general
>   

_______________________________________________
General mailing list
[email protected]
http://simile.mit.edu/mailman/listinfo/general

Reply via email to