Re: Wasm, rust, progressive web apps, etc.

[rengel]

See: Qt for WebAssembly 

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Leo in 2019

[rengel]

On Friday, January 4, 2019 at 2:49:44 AM UTC+1, Joe Orr wrote:
>
> Hmm... yet another mind mapper. Not impressed.
>
> I don't need another hairball to deal with. Leo forces me to put things in 
> order, but allows multiple orders.
>
> Ignore to your own detriment! 

I've been using outliners as PIMs ever since Dave Winer invented ThinkTank 
 at the beginning of the 
80s, in between More, Agenda, Ecco, Freemind, MindMapper, and others, and 
now TheBrain for more than a decade now. For that purpose, nothing comes 
close to TheBrain. TheBrain has been used by Britannica and the World 
Economic Forum.

Try to manage 500,000+ items (nodes/thoughts) plus 45 GigaBytes so called 
attachments (notes, images, links, tables, movies, PDF files, EXE files, 
etc.), capture links, screenshots, texts, folders of your file system or 
drag, access local files, your network, or the Internet with just one 
click, etc. with one click, rearrange visually, rearrange, regroup any 
number of items visually and ad hoc, retrieve everything almost 
instantaneously. Try all this using Leo or 'yet another mind mapper'. 
Edward made a sound assessment: Leo has its place, but not as a superior 
PIM.

It's the scaleability and ease of use that sets TheBrain apart.

There's a large public brain of a long time TheBrain user: Jerry's Brain 
, that's often used to showcase TheBrain. Try 
to do something like this using Leo.

Cheers, and happy new year!

Reinhard


(Disclaimer: I'm not connected to TheBrain company in any way.)


-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Couple new features in LeoVue

[Joe Orr]

1.
@page directive, display child nodes on same content page, example here:
https://kaleguy.github.io/leovue/#/t/66/

2.
Import with @json directive, export to Leo
https://kaleguy.github.io/leovue/#/t/163/

Should be able to look into the PhosphorJS - Vue - Tornado approach soon.

Joe

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Leo in 2019

[Joe Orr]

Hmm... yet another mind mapper. Not impressed.

I don't need another hairball to deal with. Leo forces me to put things in 
order, but allows multiple orders.

Joe

On Tuesday, January 1, 2019 at 4:46:31 AM UTC-5, rengel wrote:
>
> - A breakthrough in visualization and simplicity.  ...
>>
>
> For inspiration, have a look at https://www.thebrain.com/.
>
> Happy new year!
>
> Reinhard
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Wasm, rust, progressive web apps, etc.

[Edward K. Ream]

Wasm (WebAssembly) promises to alter the programming landscape in profound 
ways.

Vitalije has been interested in rewriting parts of Leo in rust, and this 
may be natural in the wasm world.  It's too early to use such code because 
of distribution issues, but those issues may disappear in a year or three.  
See The "death of JS?" video. 

The same video mentions PWAs, Progressive Web Apps 
, a term I 
never heard before yesterday.  This might be the future of many apps, 
including Leo.  Or not.

All the old certainties are now in doubt. Exciting times.

All comments and links welcome.

Edward

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: OMG: pyodide & webassembly

[Edward K. Ream]

On Wednesday, January 2, 2019 at 1:02:13 PM UTC-6, Matt Wilkie wrote:
>
>
> This [WebAssembly] looks like the way around the lack of browser support 
>> for python.
>>
>
> Oh yes please! 
>

It won't happen immediately, but in the meantime I highly recommend two 
videos:

Lin Clark: A Cartoon Intro to WebAssembly 

This is a pretty good overview of a graduate level course in compilers and 
optimization! 

WebAssembly and the death of Javascript? 

A good overview of the present state of wasm (WebAssembly)

The Python devs will decide what to do when wasm is ready (threads, gc), 
but the following ideas come to my mind:

1. Just as JS is not a very good assembly language for JS, Python is a poor 
assembly language for Python ;-) Wasm will work for Python as well as JS. 
This might be the knell for PYPY.  Or not. There is already a PYPY back end 
for asm.js, the precursor to wasm, but imo the whole PYPY project looks a 
bit suspect now.

2. One can easily imagine CPython converted to WasmPython. I suspect this 
will happen relatively soon.  One can also imagine Python's C API converted 
to a Wasm API.  There might be a performance boost available in doing so, 
because of a better "impedance match" between the WasmPython interp and 
wasm extension modules.  Or not.

3. WasmPython will surely be based on Python 3, not 2.  This should speed 
the transition to 3, a very good thing.

Edward

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Coming: live coding in python

[Edward K. Ream]

On Wed, Jan 2, 2019 at 11:19 PM rengel  wrote:

> Thanks for the links!

You're welcome.

> May I add: Observable. 

I've bookmarked it.  Thanks.

I'm not sure how general or useful the live-py-plugin is.  I got distracted
by wasm while looking at live-py-plugin/plugin/PySrc/code_tracer.py ;-) So
you should treat any promise I may have made with a grain of salt.

What definitely interests me is the ability to fully reload Leo, or any
other Python app, "instantly", that is, using only reload plus localized
support code.  This, I take it, is what Offray wants.  It would be a great
thing to demonstrate.

Edward

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.