Hi,

On 17/01/17 05:57, Edward K. Ream wrote:
On Tue, Jan 17, 2017 at 4:21 AM, Edward K. Ream <[email protected] <mailto:[email protected]>> 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.

I think so. @-directives were my inspiration for Grafoscopio "node tags", with let me to easy embed live coding playgrounds inside the notebook. The implementation is clumsy in my case, but I have found that having a different place for such tags and properties (like node links) decreased the code complexity that trying to search for @ in the headers, or in the body and interface looks better: the presence of a particular tag/meta-data could be illustrated with a particular icon or visual remark. (I still use "%keywords" for extending markdown with my own emergent markup).


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 haven't used clones in my own Grafoscopio notebooks, despite of using them widely in Leo (mostly because they're not yet implemented! :-P). But for live coding, they don't seem a first necessity.

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

I share your happiness. Interesting times ahead!

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 [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Reply via email to