It's been a long time since I saw something that showed features not easily duplicated in Leo. Now we all have many to chew on.
Hi,
Hi,
On Tue, Jan 17, 2017 at 4:21 AM, Edward K. Ream <edre...@gmail.com> wrote:
It's been a long time since I saw something that showed features not easily duplicated in Leo. Now we all have many to chew on.
The emacs demo is the first time I have seen org-mode headlines"properly" used as functional meta-data as in Leo's @x conventions. Furthermore, the hidden "properties" section seems more flexible/nimble that Leo's directives.
Both demos are first real challenge to Leo's capabilities I have ever seen. No, they don't have clones, but they aren't essential, are they? One can imagine a literate devops script that would simulate the cff command.
I am happy about all this. It means that Leo has serious competition. This kind of competition is healthy. It should spur us all on.
Edward
It's been a long time since I saw something that showed features not easily duplicated in Leo. Now we all have many to chew on.The emacs demo is the first time I have seen org-mode headlines"properly" used as functional meta-data as in Leo's @x conventions. Furthermore, the hidden "properties" section seems more flexible/nimble that Leo's directives.
Hi all,
Edward and John is nice to see this crosspollination of ideas and renewed inspiration. Thank you both for the responses.
I think that the core idea of live coding is talking back and
forth to computing engines/languages, using ZeroMQ, Babel, Yoton,
or similars (I don't know if Babel is based on something that is
emacs exclusive). With Grafoscopio, my computing engine is the
same available to build and run the outliner (Pharo Smalltalk), so
I don't know if the first try should be to make live coding
possible, by enabling interactive python nodes inside Leo (which
is already running and build on python) and then abstract it for
more diverse computing engines/languages.
On simplifying Leo format, I'm all for it. As I said, I have
problems remembering what acronyms like gnx, uA p, g, c mean, so I
can not go into implementation details here. But org mode, YAML
and STON have shown that is possible to have complex outliners
with a simple storage format and dedicated, but simple, objects to
store node metadata.
Cheers,
Offray
--
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+...@googlegroups.com.
To post to this group, send email to leo-e...@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
tl;dr: Leo must support Emacs Babel concepts.