Re: The roadmap for 2018: visualization & services

2018-01-16 Thread Edward K. Ream
On Wed, Jan 3, 2018 at 2:48 PM, Offray Vladimir Luna Cárdenas < off...@riseup.net> wrote: > Hi, > > This reminds me of a blog post where I saw kind of a similar relationship > between visualizations and outlining that was the AHA moment to conceive > the development of Grafoscopio [1]. Several inf

Re: The roadmap for 2018: visualization & services

2018-01-03 Thread Offray Vladimir Luna Cárdenas
Hi, This reminds me of a blog post where I saw kind of a similar relationship between visualizations and outlining that was the AHA moment to conceive the development of Grafoscopio [1]. Several influences, like Leo and IPython are mentioned there. In the Pharo case, the GT Tools[2] and the Roass

Re: The roadmap for 2018: visualization & services

2017-12-31 Thread Edward K. Ream
On Sunday, December 31, 2017 at 6:46:26 AM UTC-6, Edward K. Ream wrote: > > > *Summary* > > Splitting body text into @language blocks has implications for rendering, > for the valuespace plugin, for jupyter "emulation" and for the rst3 > command. Making tags visible is a pattern suggested by org

Re: The roadmap for 2018: visualization & services

2017-12-31 Thread Edward K. Ream
On Saturday, December 30, 2017 at 6:47:04 AM UTC-6, Edward K. Ream wrote: *Visualization is the heart of what we want* > > To emulate the look of a jupyter notebook *we need only aggregate the > rendered output of several nodes into a single VR pane*. This is kinda > what VR2 does. It can and

Re: The roadmap for 2018: visualization & services

2017-12-31 Thread Edward K. Ream
On Sat, Dec 30, 2017 at 4:28 PM, tscv11 wrote: * - "Leo's DOM (outline DAG) and API (programming interface)."* > ​Leo's tree of vnodes is indeed a Directed Acyclic Graph. That is, vnodes may have multiple parents. That's how Leo represents clones. > > *- It should be possible to do be

Re: The roadmap for 2018: visualization & services

2017-12-30 Thread tscv11
Hello, It's amusing that you're talking about improving the vr-pane when I've just run into the problem of not being able to play movies in Leo. I've covered that in another post. Anyway, what you've said sounds good to me, except for "DAG" which I'm guessing stands for (d)irected (a)cyclic (

The roadmap for 2018: visualization & services

2017-12-30 Thread Edward K. Ream
Yesterday, sitting in the bathtub, I saw a principle that simplifies everything: *Visualization is the heart of what we want* To emulate the look of a jupyter notebook *we need only aggregate the rendered output of several nodes into a single VR pane*. This is kinda what VR2 does. It can and