It looks pretty cool in fact :-).
Thanks,
On 1/04/20 5:15 p. m., Thomas Passin wrote:
> Hi, I see you found us on another thread. Here is a longer example.
> It's a real one that I did for myself some time ago. It is too long
> to show in a single image, so I exported it to the browser and
Hi,
Nice to see this theme become alive again, as Jupyter interactive alike
experiences combining with Leo outiling alike experience have been
discussed before. We could have interactive emergent computing. I have
been a log advocate of them and it was the reason I prototyped
Grafoscopio[1],
On Tue, Mar 31, 2020 at 8:00 PM Thomas Passin wrote:
>
> On Tuesday, March 31, 2020 at 6:42:01 PM UTC-4, Edward K. Ream wrote:
>
>> As you say, at present the ipynb.do_cell method (in importers/ipynb.py)
>> doesn't save much. It should be easy to save more, if you would like that.
>>
>
> Easy,
On Tuesday, March 31, 2020 at 6:42:01 PM UTC-4, Edward K. Ream wrote:
> As you say, at present the ipynb.do_cell method (in importers/ipynb.py)
> doesn't save much. It should be easy to save more, if you would like that.
>
Easy, perhaps, but I would go slowly, because we need to look at how
On Tue, Mar 31, 2020 at 11:35 AM Thomas Passin wrote:
I tried importing a notebook using the importer from the Files/Import Files
> menu. It didn't bring everything in, just the text cells. If there is
> another importer, I don't know if it so I didn't try it.
>
There is only one importer ;-)
On Tuesday, March 31, 2020 at 9:28:01 AM UTC-4, Edward K. Ream wrote:
>
> On Tue, Mar 31, 2020 at 8:19 AM Thomas Passin > wrote:
>
> Thomas, seems like we agree on points 1 through 3.
>
> >> 4. In the (unlikely?) event that people want to use both Leo and
> jupyter, Leo can already import/export
On Tue, Mar 31, 2020 at 8:19 AM Thomas Passin wrote:
Thomas, seems like we agree on points 1 through 3.
>> 4. In the (unlikely?) event that people want to use both Leo and
jupyter, Leo can already import/export with jupyter
> Here I differ. Leo cannot import/export anything Jupyter-ish but
On Tuesday, March 31, 2020 at 7:24:52 AM UTC-4, Edward K. Ream wrote:
>
> Thomas, this post is an indirect response to some of your recent remarks.
> There is some chance I understand them now ;-)
>
It's hard to grasp some of these things until you get time to work with VR3
for a while. I
Thomas, this post is an indirect response to some of your recent remarks.
There is some chance I understand them now ;-)
When I awoke this morning I saw that Leo + vr3 looks to be *superior *to
Jupyter! vr3 adds all essential features of Jupyter notebooks and cells,
while retaining Leo's
