Re: For new Leo users / Tagged topics in this forum / useful resource

Nice tip. Thanks. I am indeed new to google groups and appreciated that tip. It gets me nowhere that I can tell with my current issue with which I hope you can help. I would like to respond to a topic that may not have been addressed since 2011. On Tuesday, February 2, 2016 at 2:39:36 PM

Re: I've been working on the make_stub_files project

On Saturday, February 6, 2016 at 11:41:38 AM UTC-6, Edward K. Ream wrote: > > This project > > (the code is here , scroll > down for the docs) has taken *all* my attention. > >

Re: For new Leo users / Tagged topics in this forum / useful resource

David, in the most basic case Leo doesn't install. You simply run "python launchLeo.py" from the main Leo directory and you should be good to go assuming python and Qt are installed correctly. On Thursday, February 11, 2016 at 5:43:18 AM UTC-5, David Pietz wrote: > > > BTW: The topic is No

I'm back. Ask me anything :-)

I have just declared the make-stub-files project to be code complete. I'll be working on docs, but I'll also be coming up to speed with recent Leonine developments. I'm back monitoring Leo's irc channel, so *ask me anything*, here or on irc. Edward -- You received this message because you

Re: Leo reimagined: a tree/dag/view for every attribute!!!

I'm trying to see the use case. I know you use clones to gather scattered bits which are relevant to an issue. I'm seeing this 'colored threads' concept applying like this: The 'black' thread has nodes arranged in code-correct order, as they would need to be presented to the interpreter. The

Re: Leo reimagined: a tree/dag/view for every attribute!!!

Sounds very interesting. Might be worth a look at the backlinks plug-in, which provides a mechanism and gui for superimposing a general graph on the tree. Graphcanvas plug-in is just another gui for the same mechanism. Bit entirely sure I follow the 'attribute' part vs nodes, and of course

Leo reimagined: a tree/dag/view for every attribute!!!

John Lunzer's recent remarks has triggered one of the biggest Aha's in Leo's history, one that was totally unexpected until this afternoon. Leo's fundamental data structure is a tree of nodes. More accurately, it is a Directed Acyclic Graph or dag. Links in such a graph can point "down" the

Re: New directions suggested by make-stub-files project

On Thu, Feb 11, 2016 at 11:20 AM, john lunzer wrote: Really interested in your ideas for creating views. I think clones do have > a place and they're great to have when you need them but I don't think > think they are the answer for views and I think using them as such is a >

Re: Leo reimagined: a tree/dag/view for every attribute!!!

On February 11, 2016 6:20:52 PM CST, 'Terry Brown' via leo-editor wrote: >Bit entirely sure I follow the 'attribute' part vs nodes, and of course *Not* entirely, phone email autocomplete :-/ -- You received this message because you are subscribed to the Google

Re: I'm back. Ask me anything :-)

Welcome back. Can't wait to see what your thoughts and developments are on task oriented docs. On Thursday, February 11, 2016 at 10:57:06 AM UTC-5, Edward K. Ream wrote: > > I have just declared the make-stub-files project to be code complete. I'll > be working on docs, but I'll also be coming

New directions suggested by make-stub-files project

I'm decompressing from the intense programming I've done recently. The decompression phase is often the time when new ideas arrive. Here are some recent ones: 1. I love clones, I hate clones. I used clones intensely in the make-stub-files project. - For unit testing, I moved clones of all

Re: New directions suggested by make-stub-files project

Really interested in your ideas for creating views. I think clones do have a place and they're great to have when you need them but I don't think think they are the answer for views and I think using them as such is a workaround to a cleaner view functionality. I recently also thought about