extensions for e3

60 views
Skip to first unread message

David Karger

unread,
Jul 15, 2012, 2:13:15 AM7/15/12
to SIMILE Widgets
I have some students working on some chart views for exhibit3 (e.g.
scatter plot and bar chart). When done, how should these be
incorporated? Should we submit a pull request with the intent that they
be incorporated on github and served from simile-widgets, or just host
the extension somewhere ourselves?

Contemplative

unread,
Jul 16, 2012, 8:11:36 PM7/16/12
to simile-...@googlegroups.com
Gosh!  That is excellent!  I am just a user, not one of the active project participants, but whether you 
post them to github or from another site, please do let us know!  The chart extensions are one of the 
things I have been wishing for in exhibit 3.x

Thanks,

wjw

Ryan Lee

unread,
Jul 18, 2012, 4:33:31 PM7/18/12
to simile-...@googlegroups.com
You should plan to host them regardless of their eventual fate - the
community's going to need an opportunity to review them for usage before
deciding whether they belong in the core.

We can discuss wider plans for hosting experimental / non-core material
somewhere in the realm of simile-widgets, but since that hasn't yet been
decided, I'd go with some method of self-hosting.

David Karger

unread,
Aug 5, 2012, 2:47:37 PM8/5/12
to simile-...@googlegroups.com, Ryan Lee
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
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?

Ryan Lee

unread,
Aug 22, 2012, 8:54:11 PM8/22/12
to simile-...@googlegroups.com
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.

David Karger

unread,
Aug 23, 2012, 12:13:06 PM8/23/12
to simile-...@googlegroups.com, Ryan Lee
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.
Reply all
Reply to author
Forward
0 new messages