Possibly interesting to Eve people: Leo editor

[0joshua...@gmail.com]

Leo is a project I follow. Although it's built on Python scripting and IPython integration, the reason I brought it up here is how it builds a text/data workflow around extremely configurable views of an underlying (directed acyclic) graph. So it's like a semantic wiki where the user specifies the semantics and filters, the external files, etc.

[Zubair Quraishi]

I took a look at Leo. looks very interesting, but I think they need to work on their presentation if they want to catch a wider audience. It is amazing how many great tools never see the light of day as they are released without any "polish" (as in Shine) . I just hope that Eve has the right shine to it when released, but after seeing Light Table I am sure that Eve will be a polished product!

[Chris Granger]

Sorry for the slow response here, we've been heads down getting a demo together.

When I was doing research for LT, I came across Leo and looked into it. It definitely exhibits some of the original tenants of LT :) I didn't actually play around with too much as it seemed to be positioned in kind of a weird way and it seemed like SmallTalk's browsers were a better implementation of what Leo tries to present. That being said, I'd love to hear what someone who really uses it thinks about it.

Cheers,

Chris.

--
You received this message because you are subscribed to the Google Groups "Eve talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to eve-talk+u...@googlegroups.com.
To post to this group, send email to eve-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/eve-talk/fdae291c-d12c-4fc8-8a99-675917c23565%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[lun...@gmail.com]

I am a semi-regular contributor to Leo (mostly I complain to Leo's patient creator). I can clear up what Leo is, but not by telling you what it is rather what it gives you. Leo gives you the tools to build organization around information. For many, the information is code and code bases. Leo's code base is itself generated from Leo. You can send information into Leo, for example you can import code into Leo from just about any programming language and Leo will chop it up into an outline (the mentioned directed acyclic graph) for you based on the syntax of the language itself. You can generate files from Leo, for example you can generate a source code file from an outline.

For programmers, Leo gives you a way to add arbitrary levels of organization to code. With that come the tools to navigate through the organization you've created. Leo contains millions of lines of code and without Leo to organize it the code base would have crumbled under its own weight ages ago. But it hasn't and now has been under development in Python for 15 years. This is because the structure you can create with Leo provides a global view of your code and allows you to dig down to a single line and see how that line exists in relation to the entire code base. Leo has fantastic search capabilities, different and better than most other tools. If I need to dissect an unfamiliar code base Leo is one of the first tools I turn to. 

But this organization is not in any way limited to code. The information you organize can be anything. Leo is great for managing projects. I use Leo daily in my professional work to organize hundreds of json and xml files representing work done over a period of years. I have near instantaneous access to files and can identify work done at any point, my colleagues are bewildered by my "memory" and how I manage so much information. I've told them about Leo but they still for some reason think I have some special ability. 

Still others use it to organize their thoughts, whether that be: their life, writing, notes, etc. Leo is not a unique tool for any of the actions described but its foundations are now so strong that it makes it a great tool for these purposes. One of the most exciting aspects of Leo is that it doesn't exist in a bubble, it can take in the world and spit it back out again. Leo is slightly biased towards Python because that is the language it is developed in but for the most part Leo remains language agnostic. I have used Leo to help me structure assembly language to great effect.

I encourage the Eve developers to open LeoPyRef.leo, Leo's code base. It may provide some insight into how powerful the organization can be. I've only just begun to explore the concepts and design behind Eve and it really seems promising and tries to address many of the same challenges that Leo tries to address. I'm excited to see where Eve goes and look forward to trying it out myself for inspiration and hopefully someday as a powerful tool.

[0joshua...@gmail.com]

The link is LeoPyRef.leo and the raw text isn't nearly as illustrative without a Leo viewer. There's an online one but it doesn't handle anything of size like the actual program can.

[Dee]

On Saturday, April 30, 2016 at 10:48:31 PM UTC-4, 0joshua...@gmail.com wrote:

Leo ... builds a text/data workflow around extremely configurable views of an underlying (directed acyclic) graph.

FYI, there's an interesting discussion here in which Leo's creator is considering re-engineering Leo to allow multiple directed acyclic graphs to be superimposed on the data and visualized independently (as trees).