Hi Thomas,
Thank you for doing all that research!
> 1. Should we go ahead and tie Exhibit to some of these libraries, or
> develop a method by which to be able to plug in various libraries?
I think we were able to plug in Google Maps quite seamlessly and that's
the model I'd like to follow. As far as an exhibit author is concerned,
all she has to do is this:
<script src=".../exhibit-api.js?views=plots"></script>
Everything else can be replaced should we find it too slow, too big, or
insufficient in term of flexibility, etc. etc.
> 2. Should we favor recreating these ideas in a more light weight
> fashion or otherwise custom for Exhibit?
Your choice, really, if you're implementing it. But I think everyone
does want speed, features / flexibility, and a look and feel that's not
jarring with the rest of Exhibit.
What I usually do is start with my own code and just a few features so
that I understand the space. Once I understand from that early prototype
what I want out of the "finished" product, then I re-evaluate my choice
of frameworks / libraries.
> 3. There are a lot of features to all of these items. Would we prefer
> simpler, cleaner solutions with fewer options?
Let's start simple and I'm sure you'll get enough requests to last
several years of coding :-)
Mason (CC'ed) is another student in my research group and he'll be
taking care of the calendar view. So, that's one thing off your plate. I
think the plots are already a lot to implement if you would like to give
us a hand with that...
Thanks,
David
_______________________________________________
General mailing list
[email protected]
http://simile.mit.edu/mailman/listinfo/general
