Re: [matplotlib-devel] IPython Comm backend

2013-11-18 Thread Michael Droettboom
On 11/14/2013 08:24 PM, Jason Grout wrote: > On 10/16/13 3:46 PM, Jason Grout wrote: >> On 10/16/13 1:58 PM, Michael Droettboom wrote: >>> Sorry to take so long to get to this. This is a nice piece of work. >>> >>> The most obvious thing is that this is a copy-and-paste of the existing >>> WebAgg b

Re: [matplotlib-devel] IPython Comm backend

2013-11-15 Thread Phil Elson
Very nice. Thanks for sharing Jason. On 15 November 2013 13:18, Jason Grout wrote: > On 11/14/13 7:24 PM, Jason Grout wrote: > > Following a very helpful conversation with Michael this morning in the > > dev hangout, I got this working with the current master (of matplotlib > > and ipython). >

Re: [matplotlib-devel] IPython Comm backend

2013-11-15 Thread Jason Grout
On 11/14/13 7:24 PM, Jason Grout wrote: > Following a very helpful conversation with Michael this morning in the > dev hangout, I got this working with the current master (of matplotlib > and ipython). I also got this initial experimental demo working on the Sage cell server: http://sagecell.sage

Re: [matplotlib-devel] IPython Comm backend

2013-11-14 Thread Jason Grout
On 10/16/13 3:46 PM, Jason Grout wrote: > On 10/16/13 1:58 PM, Michael Droettboom wrote: >> Sorry to take so long to get to this. This is a nice piece of work. >> >> The most obvious thing is that this is a copy-and-paste of the existing >> WebAgg backend -- and maintaining the two is going to be m

Re: [matplotlib-devel] IPython Comm backend

2013-10-16 Thread Jason Grout
On 10/16/13 1:58 PM, Michael Droettboom wrote: > Sorry to take so long to get to this. This is a nice piece of work. > > The most obvious thing is that this is a copy-and-paste of the existing > WebAgg backend -- and maintaining the two is going to be much harder > than building both out of the sam

Re: [matplotlib-devel] IPython Comm backend

2013-10-16 Thread Michael Droettboom
Sorry to take so long to get to this. This is a nice piece of work. The most obvious thing is that this is a copy-and-paste of the existing WebAgg backend -- and maintaining the two is going to be much harder than building both out of the same pieces. As of 6389d14f, the WebAgg backend was ref

[matplotlib-devel] IPython Comm backend

2013-10-10 Thread Jason Grout
I've been working on a backend based on the webagg backend, but that uses the IPython Comm architecture at https://github.com/ipython/ipython/pull/4195 to send messages instead of starting a server and opening websocket connections. I have an initial version in my github ipython-comm branch (s