Hi Rob
On Friday, 6 November 2015 01:37:01 UTC, Largo84 wrote:
>
> To Don (and others who have already migrated or are considering migrating
> to Leo from ECCO Pro):
>
> ECCO Pro was a terrific program back in the '90s that allowed for multiple
> views of the same data in an outline-centric display with most of the
> capabilities of a PIM. Unfortunately, the developers abandoned it. There
> was some expectation that the code would be released as open source, but
> that never happened. Even today, it's still a remarkable program. I started
> experimenting with different replacement programs and finally settled on
> Leo. Except for the lack of a calendar, it does everything I used ECCO for
> and MUCH more (I still wish there was a way to integrate a calendar view,
> but that will have to be another topic I suppose).
>
> I have found that one major difference between how I used ECCO and how I
> use Leo is that I now keep information in separate files (mostly plain
> text) instead of inside the ...eco file. That allows me to use Leo for so
> much more than I ever could do with ECCO, like write LaTex documents, HTML
> pages and CSS files.
>
> I'm probably the wrong person to offer any suggestions to others on how to
> migrate from ECCO to Leo as that would depend on the particular use case
> and the specific needs and expectations. However, I'd be happy to answer
> any questions if I'm able, though. Post in this thread or contact me
> directly.
>
> Rob.............
>
I too am a fan of Ecco - I still use it under Windows and (via Wine) under
Linux. I would love to find the 'sweet spot' between Ecco and Leo
As you know, Ecco's main pane is more of a hierarchical indented list
[together with, simplified, their respective folders and their values]. In
comparison, Ecco has hierarchical nodes, each with a headline and content.
Both seem to have their uses to me. Ecco is fantastic (to me) for rapidly
creating hierarchical lists. The Leo equivalent would be many, many
headlines, few of which have any body text. I find the Ecco key shortcuts
extremely intuitive for this purpose (I realise that I could/should work on
the Ecco key bindings I use...)
I use Leo more for when I have more information in the node body, and/or I
want to do more intelligent things with the data. As you probably know,
Ecco can be programmed (with the EccoExt extension) in Lua. I have never
got this working under Linux, and in any case the interface, although an
extremely impressive bit of work technically, is a bit painful. It is
delightful to know that I can process the data in a .leo file in python...
I find myself slightly resistant to doing the first kind of use (rapid
heirarchical lists) in Leo, for some reason. On reflection, this might be
because the Ecco layout encourages this. The view
This has made me wonder a couple of things:
- any idea what the Qt(?) limits to the number of nodes in an outline
widget might be? does performance take a hit if you have, say, tens of
thousands of nodes
- is it possible to style the widget to have rules lines between the
node headlines? a bit like the main part of :
http://www.adlerian.us/outline%20view.jpg (ignore the 'attribute' columns,
they are sort-of the equivalent of body text)
I do feel slightly apologetic about keeping mentioning Ecco in this forum -
Leo is a great bit of work and I have not put the work in to mould it to my
needs sufficently to make many sensible contributions/suggestions. It is
interesting how such an old program as Ecco still has adherents, nearly
twenty years after it was discontinued...
Jon N
--
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 http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
