We'll have demos and github repos up in a couple days (scatter plot, bar
chart, and force-directed graph layout). There are a couple of pending
pull requests on core that will make them work better.
On 8/22/2012 8:54 PM, Ryan Lee wrote:
On 2012-08-05 11:47 , David Karger wrote:
OK, we'll (eventually) host them at
http://projects.csail.mit.edu/exhibit .
Next question: for development, we can set up our own github repo to
contain just our extensions, and host just those extensions on our
site. Alternatively, we can fork zepheira/exhibit3 , add our
It would make sense to me to work in a separate, non-forked repository
for each extension. I suspect both your deployment and development
mechanics are quite a bit easier when you need not concern yourself
with the rest of the supporting files, reconciling commits, etc. while
you're focused on one piece.
I'm curious about what these extensions are. Obviously nobody needs
to show off anything prematurely, but if any of your students want to
discuss where they're planning on going, I'm sure there would be
others here interested to hear it.
extensions to the extensions directory in the fork, and host the entire
forked repo on our server. In fact the questions of what to put in the
repo and what to host on our site are separable. Any advice as to which
is the better approach?
--
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.
