No no, I just meant that as an update/explanation as to why the code isn't
readily available at the moment. It's on the back of my mind and should
ensure a long ans healthy life for the website.

On Tue, Mar 29, 2016 at 2:49 PM, Stephen Mallette <spmalle...@gmail.com>
wrote:

> Thanks for the update.  I'm not sure I'm reading you the wrong way, but are
> you saying that you'd like to hold off promoting GremlinBin more heavily
> until you get past proof of concept phase?
>
> On Tue, Mar 29, 2016 at 8:45 AM, Dylan Millikin <dylan.milli...@gmail.com>
> wrote:
>
> > I'm obviously biased so I'm just going to add a bit of information here:
> >
> > The current version was a bit of a proof of concept. As such the
> > documentation lacks a bit and code could be a tad cleaner. I'm currently
> in
> > the process of modulating the various moving pieces and documenting
> > everything so that I can put the code up on github for people to
> > contribute. This should solidify the entire project.
> >
> > I've added empty graphs to the current implementation and the next steps
> > are:
> > - open source some components (console-js at the very least)
> > - change the visualization plugin to support larger graphs.
> > - add the gratefuldead graph and the northwind graph.
> > - get things working on mobile
> >
> > Eventually, it may be interesting to see if starting docker
> containers/aws
> > images may be a good way to get rid of the inconsistencies due to
> > sandboxing and help in allowing for OLAP traversals. Though this implies
> > heavier resource usage and that would come with a cost. Worth exploring
> > though.
> >
> >
> > On Mon, Mar 28, 2016 at 1:13 PM, Stephen Mallette <spmalle...@gmail.com>
> > wrote:
> >
> > > I noticed his morning that we don't have a link to Dylan's GremlinBin
> on
> > > the home page.  Seems like it's a mistake not to promote such an easy
> way
> > > to get started with Gremlin.
> > >
> > > I was thinking we could create a "Try Gremlin" logo of some sort for
> that
> > > purpose - sound good?
> > >
> >
>

Reply via email to