On Fri, 6 Nov 2015 05:17:03 -0800 (PST) john lunzer <[email protected]> wrote:
> I've never used ECCO or heard of it before using Leo so I'm in the > dark regarding its features. > > That said, I think it would be appropriate to lay out the > functionality you're for in a "calendar view". I do a couple of calendar related things with Leo. I use `remind` https://www.roaringpenguin.com/products/remind for managing appointments and reminders. So I have a list of Leo nodes with first lines like # 2015 oct 12 +1 at 14:00 sched one5 i.e. event on 2015-10-12 14:00, start showing on upcoming events list +1 days before, and `sched` identifies the times you want to be reminded before the event, I use a function `one5` to supply a list that causes reminders at 60, 40, 20, and 5 minutes before the event. So I just have a Leo button that exports those nodes to the `remind` reminders file (basically just adds the node headline to the above). To view the calendar, I use a browser to view remind's HTML output. remind handles repeating events, which is handy. The other calendar thing I do with Leo - a calendar Qt view which operates on the `Due date` and `Next work date` fields in Leo's todo.py plugin. You can drag items around to change the dates etc. But I was having a hard time working out the "right" way to use Qt drag-and-drop and Qt's MVC framework, so I kind of feel the code's a mess. Perhaps a generic widget like the one I just described, where you supply a list of items with titles, gnxs, and dates, and the widget calls your callback when one's dragged between two dates, or deleted maybe, so you can update the tree. A small wrapper function could handle getting dates into and out of the nodes. The doesn't address the end user interface issue, but maybe the todo.py plugin would be sufficient if the widget just described existed. I guess there should be a signal for the widget when the user changes the date on a node while the widget's displaying that node already. Cheers -Terry > If you found that > feature useful and you miss it my guess is that others would find it > useful as well. It is potentially a feature that could benefit us > all. As I've been writing the basis for a new plugin recently I've > found that because Leo is based on Qt/PyQt that it is extremely > flexible and that most requested/imagined features are possible. Also > keep in mind that a new view/plugin needn't conform to Leo's frame > system (though in most cases it is preferable), just a thought to > keep your mind open to all possibilities of implementation. > > If we start the discussion of the layout in the forums then it could > be moved to github as an enhancement request if anyone has anything > else to add. > > On Thursday, November 5, 2015 at 8:37:01 PM UTC-5, 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............. > > > -- 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.
