Looks like the best time for all will be on Thursday at 2pm Pacific. I'll send the logistical information to all who have expressed interest in joining.
Thanks folks! -Richard On Wednesday, January 27, 2016 at 5:54:14 AM UTC-8, Kent Tenney wrote: > > Same here. > > On Wed, Jan 27, 2016 at 7:52 AM, 'Terry Brown' via leo-editor > <[email protected] <javascript:>> wrote: > > On Tue, 26 Jan 2016 17:06:17 -0800 (PST) > > Richard Andersen <[email protected] <javascript:>> wrote: > > > >> It looks like a conference call on Thursday, 1/28 at 12 noon Pacific > >> will work best for those that I've heard from. > >> > >> Any and all are welcome and encouraged to join, just let me know. > >> I'll send out the logistical details via email to those who'd like to > >> join. > > > > Can't promise I'll make it but send me the details and I'll see what > > I'm up to then. > > > > Cheers -Terry > > > >> Thanks, > >> > >> -Richard > >> > >> On Monday, January 25, 2016 at 11:18:26 AM UTC-8, Richard Andersen > >> wrote: > >> > > >> > [continuation of prior thread "Looking to engage a Leo expert in a > >> > paid project" with new thread subject] > >> > > >> > 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 > > > > -- > > 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] <javascript:>. > > To post to this group, send email to [email protected] > <javascript:>. > > Visit this group at https://groups.google.com/group/leo-editor. > > For more options, visit https://groups.google.com/d/optout. > -- 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.
