Hi,

Up to now, I've been using the MIT-hosted libraries of Exhibit.  This
has worked well.  However, I have decided to take the plunge and host
Exhibit locally.  (This is due to the anticipated performance gains,
the removal of the dependency on the MIT servers, and because I want
to use Josh Huckabee's very nice Calendar view extension for Exhibit
which, apparently, is not included in the MIT-hosted version.)

I've been digging around trying to find out the definitive and current
recipe on how to do this.  Perhaps it doesn't exist.  I've looked at
these links:
http://www.stevetrefethen.com/blog/HostingMITsSimileExhibitOSProject.aspx
http://simile.mit.edu/wiki/Exhibit/2.0/Running_Exhibit_Yourself

However, there appear to be discrepancies between the two.  For
example:
1. The first link suggests SVN from googlecode whereas the second
suggests SVN from mit.  Does it matter?  Will I end up with the same
thing?  Will I get the Calendar view extension mentioned earlier?
2. The first link suggests that after checkout from SVN you should
remove a bunch of "site" content.  The second link does not mention
that.
3. The first link implies that a number of changes will be required
whereas the second implies that I'd only need to change references to
simile-ajax-api.js and toggle useLocalResources = true

Needless to say, I want the latest (production) version of Exhibit.
Ideally, I would also like to be able to support the recently released
new features of Timeline (2.3.0, I believe).  Is there something I can
do to my "local Exhibit installation" to enable that?

Any help or suggestions based on your experience would be appreciated.

Thx,
-Mark

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"SIMILE Widgets" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/simile-widgets?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to