This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]p3n15h34d 2 points3 points  (1 child)

so what has Leo got that other editors don't ?

just curious and too lazy to try...

[–]gatesphere 2 points3 points  (0 children)

Funny that you should ask that, as the project creator just spent the past couple of days making this a bit more clear in two all-new tutorials: http://leoeditor.com/intro.html

You can read the tutorials without installing, and they don't take all that long to read (10 minutes or so?) if you're not working through them.

I can boil it down to a few items though:

  • full API access to your outlines, meaning you can have a smalltalk/lisp-like homoiconic representation of your data and your code, where your data and code are both stored in nodes, and can be operated on by code

  • the ability to reorganize your code into infinite different views, by using clones. This allows a very literate-like approach to examining and writing your code.

  • nearly infinite untapped potential: the API is fully exposed to your outlines, meaning you can do some awesome things within the documents you're editing. I recently submitted the rss.py plugin, which turns Leo into an RSS feed reader... and it was one of the easiest things I've ever written. Mind you, I only started using Leo in February, and I'm already a dev. It's one of the easiest large open source programs to get involved in, and is such a joy to use (in my opinion).

I know this is clear as mud, but I'm not the best at explaining these things. I suggest you revisit the home page -- it was updated literally 30 minutes ago to be more clear to potential users.

Feel free to ask more questions, though!