Looking to engage a Leo expert in a paid project

[Richard Andersen]

Hello all.

I'm checking to see if there are any members of the community who'd be interested in working on / supporting / contributing to what I think will be a great project, and one that aligns well with Leo's amazing capabilities.

I am a long-time EccoPro user and have recently discovered Leo.   I'm getting a lot of benefit from Leo already and have effectively utilized a couple components...

- quicksearch (which creates the "Nav" tab)

- nodetags (which creates the "Tags" tab) -- many thanks to Jake Peck for his help! 

... and have a few other coding/configuration changes in mind which, I think, will make Leo a great alternative to EccoPro for many users.    I saw an earlier posting from some "Ecco refugees" which seems to indicate some wider interest in this.

I'm planning to use Leo for coding as well, but am tackling this "organizer" task as a first priority.

Please respond if you're interested.    I am open to whatever combination of paid / other efforts can help move this along.

Cheers,

-Richard

[Terry Brown]

For organizer use, there's the todo.py plugin as well, but perhaps that's not the direction you mean?

I have some unreleased kind of messy code which makes a calendar interface to the todo items, with cross file editing etc., although it never really seemed to help the deluge that much - have now switched jobs and hoping that will work ;-)

Cheers -Terry

---

From: Richard Andersen <mont...@gmail.com>
To: leo-editor <leo-e...@googlegroups.com>
Sent: Friday, January 15, 2016 11:21 AM
Subject: Looking to engage a Leo expert in a paid project

--
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.

[Richard Andersen]

Thank you for chiming in, Terry.

It's good to know about your calendaring code.    Will keep in mind as calendaring seems to be something other EccoPro refugees have been looking for.    I'm using some basic Leo nodes for recurring tasks but can envision how a calendar would be more elegant.

I have looked into the todo.py module but found it difficult to do parameter-based searches with it.   For example, "show me all To-do's I need to do Today for Others".    With nodetags.py and some use of @button commands and tag-based queries, I am able to do those types of searches quickly as needed.

It's also nice to be able to search across my Leo file with quicksearch.py in one tab and have another tab populated with a parameter-based search like the one above.

-Richard

[Edward K. Ream]

On Fri, Jan 15, 2016 at 11:21 AM, Richard Andersen <mont...@gmail.com> wrote:

Hello all.

I'm checking to see if there are any members of the community who'd be interested in working on / supporting / contributing to what I think will be a great project, and one that aligns well with Leo's amazing capabilities.

​I would be happy to talk to you more about your project.

Edward

[Largo84]

I'm interested in your project as an 'ECCO refuge', but I'm not much of a programmer, so I don't know how much help I can be (except as an interested observer and possibly beta tester).

Rob............

[Richard Andersen]

Sounds good, Rob.

I'll show you what I've put together so far to get your input.    Will PM you to find some time.

Thanks for offering to participate!    Beta testing and providing input will certainly help.

-Richard

[jkn]

You'll have seen my name in some of the 'Ecco Refugees' type threads, although I came to Leo independantly of that. I *am* something of a programmer, if that helps, although only a beginner as far as working within Leo.

Would be interested in hearingmore of your work via PM or whatever.

    Regards
    Jon N ('jkn')

[Richard Andersen]

Thanks for your interest, Jon.

A small group is coming together, so let's pool some ideas and see what can be done.

I'm going to schedule a demo of what I've done for a few who are interested to kick things off.    Edward (creator of Leo) was generous in spending some time with me to discuss this and it seems like the Leo architecture + some existing plug-ins make it suitable to accomplish quite a bit without a ton of work.

-Richard

[Don Dwiggins]

Thanks for tackling this, and keep me in the loop.  I'm a programmer (and one of the "Ecco refugees"), but with little time to spare.  Still, with proper motivation, I might be able to free up a block of time now and then to implement something.


Don

Question: given the range of features that Ecco has, what do folks think would be the priorities?

--

[Don Dwiggins]

On 1/21/16 10:13 AM, Don Dwiggins wrote:

Thanks for tackling this, and keep me in the loop.  I'm a programmer (and one of the "Ecco refugees"), but with little time to spare.  Still, with proper motivation, I might be able to free up a block of time now and then to implement something.

One additional thought: there's an Ecco template that supports David Allen's }"Getting Things Done"; I've been learning it to improve my own effectiveness.  It has a combination of features that would make a good test case for this project (probably down the road a bit).


Don

[Richard Andersen]

Hello Don.

Glad you're interested in this initiative.    Rob and I (see above) had a good/productive conversation today and it seems like we're converging on a short list of items that will really help bridge the Ecco to Leo gap.   

I'm going to see if we can get a call set up, for those who'd like to contribute ideas / time / etc., sometime mid to late next week.

Looking fwd to connecting further on this.

-Richard

[Richard Andersen]

Also, I do agree that a GTD use-cased based model is a great way to focus and validate the Leo mods we're aiming for.

-Richard

[Edward K. Ream]

On Thu, Jan 21, 2016 at 8:52 PM, Richard Andersen <mont...@gmail.com> wrote:

Also, I do agree that a GTD use-cased based model is a great way to focus and validate the Leo mods we're aiming for.

​Yes.  This would be an interesting project.

EKR

[Jacob Peck]

I know it's not quite exactly the same, but for a while I was using a home-brewed system I called LTD (Leo Things Done), that leveraged the power of Leo and a few custom plugins (now part of the codebase) to organize my life.  I fell out of the habit, but it was quite effective for me for a while.

Here's a writeup, in case someone finds it handy:

http://blog.suspended-chord.info/2013/11/18/leo-things-done-revised/

-->Jake

[Largo84]

I think Leo can be the killer PIM of all time (no, not an exaggeration). It seems there could be ways to 'hook' into other APIs (like CardDav and CalDav), I just don't have the programming 'chops' to do it. However, I'd be willing to pitch in on a crowdfunding project (as long as the final product remains Open Source). I don't know what the protocols are for defining the scope of work and the specifications.

I'm very excited about the possibilities to extend Leo! What a cool thing if the 'ECCO Refugees' (and others who need/want what ECCO provided) could move on from a program that was abandoned 20 years ago.

Rob.............

[Richard Andersen]

Thanks, Jake.

I enjoyed your blog article and I have set up your LTD hierarchy in my Leo file.   I'm using it mainly for recurring tasks at the moment, but would probably use it more if we could find ways to tie it into calendar apps like Rob mentioned.

-Richard

--
You received this message because you are subscribed to a topic in the Google Groups "leo-editor" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/leo-editor/Yu_SxN05UQs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to leo-editor+...@googlegroups.com.

[Don Dwiggins]

On 1/22/16 5:34 AM, Jacob Peck wrote:

I know it's not quite exactly the same, but for a while I was using a home-brewed system I called LTD (Leo Things Done), that leveraged the power of Leo and a few custom plugins (now part of the codebase) to organize my life.  I fell out of the habit, but it was quite effective for me for a while.

Here's a writeup, in case someone finds it handy:

http://blog.suspended-chord.info/2013/11/18/leo-things-done-revised/

-->Jake

Dang! At a first scan, your LTD looks similar to the way I use Ecco outlines for my various tasks (and have been for several years).  If/when I get a moment, I may play with it to see if I'm right.  If so, I might be able to start using Leo/LTD for part of what I need.


Thanks,
Don

[Richard Andersen]

Thanks to Jake, Rob, Terry, Edward, Jon, and Don, for expressing interest in taking Leo further in the direction of being an optimum personal organizer.    Several of you have used Ecco Pro regularly for years and like elements of it, such as...

- outline centric interface

- elegant node manipulation

- rich context (parent nodes presented in certain views)

- robust search

- robust tag / metadata handling

- integrated contact file

- integrated calendar

... and struggle with some of the other aspects of a 23 year old program (history here --> http://eccopro.com/history/arabesque/) which still amazes most of us who have used it.

- challenges exporting formatted outlines

- challenges moving nodes around from file to file

- lack of some modern capabilities (e.g. hoisting) without some additional code / config

- difficulties handling node headers and bodies simultaneously (without some additional code / config)

The goal of this project, as of now, is not to replace Ecco Pro per se, but rather to inform a direction for Leo in the area of personal organizer (a purpose for which, out of the box, Leo is very well-suited).     Having spoken with a few of you, there is interest in getting together and discussing what can be done, and which ones of us could take on various sub-projects (design, dev, testing, doc, etc.).    It appears that quite a bit could be done in a few weeks, so this doesn't need to be a massive, long-term project.

I'd like to see how many can make a call this Wed or Thurs.    I can set up a conf bridge.    I'll also demo how I'm using nodetags.py + quicksearch.py with really good results.    Perhaps others can share some of the techniques they use as well.

Please let me know if you're interested in joining and how your calendar looks for those days or, alternatively, next week.

-Richard

[Don Dwiggins]

On 1/25/16 11:07 AM, Richard Andersen wrote:

 (snip)

The goal of this project, as of now, is not to replace Ecco Pro per se, but rather to inform a direction for Leo in the area of personal organizer (a purpose for which, out of the box, Leo is very well-suited).

Good characterization of the project.  Replacing Ecco Pro, while worthwhile, should be a separate downstream effort, once we have something that's solid and working well, and undertaken with the folks on the current ecco_pro mailing list (many of them are using Slang's work to extend Ecco's functionality in ways that would need to be "ported" in order to replace the combination).

I'd like to see how many can make a call this Wed or Thurs.    I can set up a conf bridge.    I'll also demo how I'm using nodetags.py + quicksearch.py with really good results.    Perhaps others can share some of the techniques they use as well.

Please let me know if you're interested in joining and how your calendar looks for those days or, alternatively, next week.

Yes, I can make it those days; I'm in the PST zone, if that's an issue.


Don