Thanks for tracking down this problem!
LarryK wrote:
> [...]
>
> 1) The change to using getBoundingClientRect (if available in the
> browser) requires changing the ajax project within Simile widgets:
> Plan:
> a) Create an ajax release tag "2.1" to capture the current version
> b) Make the change to use getBoundingClientRect when available (won't
> require browser sniffing) and release as ajax tag 2.2
>
Sounds good to me!
> 2) Currently, the Timeline api file uses the Simile/Ajax bundle from
> MIT. I have realized that since the svn repository is available on
> public urls from google, we can use the svn repository to serve the
> library files. (Hooray!) Sometimes, the svn props of the stored files
> have to be munged, but overall, it seems to work fine. As an example,
> the file
> http://simile-widgets.googlecode.com/svn/timeline/trunk/src/webapp/examples/monet/monet.html
> uses Google to obtain the Timeline js libraries and MIT for the Simile/
> Ajax libraries.
> Plan
>
Actually Google Code SVN isn't fast enough to be used in this way. But
there's a better way. Check out the static-site subproject
http://code.google.com/p/simile-widgets/source/browse/#svn/static-site
Then use svn:externals to create a link from ajax/2.1/ and timeline/2.2/
to the correct tags. When you check that in, I believe a shell script at
static.simile.mit.edu will do svn update to serve the new APIs within an
hour or so.
David