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

​​On Thu, Feb 11, 2016 at 6:20 PM, 'Terry Brown' via leo-editor < leo-editor@googlegroups.com> wrote: 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

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

​​ On Thu, Feb 11, 2016 at 7:03 PM, Kent Tenney wrote: > I'm trying to see the use case. > ​So am I ;-) ​ > 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

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

Hi Edward, Fascinating stuff. I'm unclear on one thing though -- what you mean by 'attribute'. Is this just some arbitrary, user-definable key that would act as a name for a particular view/colored-thread? UI would be of paramount importance in this scheme -- there's lots of places

How do I add a child node to comment parrent in @clean?

Hello everybody, lets say I want to create a @clean (Python) file and I want to attach comments to some nodes. I imagine those comments being child nodes of nodes to be generated. But I don't want the the nodes containing comments to be part of the created external file. I'd assume this to

Re: How do I add a child node to comment parrent in @clean?

Probably only because it just came up in another thread, it occurs to me that you could use the backlinks plugin for this.  I.e. the answer to your question is no, there isn't really a way to do that directly, but backlinks would allow links from nodes in you @clean code tree to nodes somewhere

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

From: Jacob Peck To: leo-editor@googlegroups.com Sent: Friday, February 12, 2016 8:40 AM Subject: Re: Leo reimagined: a tree/dag/view for every attribute!!! Hi Edward, Fascinating stuff.  I'm unclear on one thing though -- what you mean by

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

Well, I'm certainly happy to have been part of the conversation. On Thursday, February 11, 2016 at 6:12:20 PM UTC-5, Edward K. Ream wrote: I see these three statements as fundamental to the data structure: *Important*: some nodes may not have any thread running them for some > colored threads

Re: How do I add a child node to comment parrent in @clean?

A limited but simpler solution is to put your comment in the headline and have an empty body. You can have as many nodes as you want with empty bodies and they don't affect the output to the @clean file at all. Like it said it's pretty limited. On Friday, February 12, 2016 at 11:56:30 AM

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

Probably overstepping here, but my input is mixed in below: On 2/12/2016 1:38 PM, john lunzer wrote: Well, I'm certainly happy to have been part of the conversation. On Thursday, February 11, 2016 at 6:12:20 PM UTC-5, Edward K. Ream wrote: I see these three statements as fundamental to the

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

Thanks for your reaction, very much agree about all nodes have at least one attribute. Really just trying to work through it and hoping to further incite Edward's brain to help with any clarification, hopefully pointing out where I'd gone wrong in my buildup. On Friday, February 12, 2016 at

Re: How do I add a child node to comment parrent in @clean?

Hi guys, thanx for the swift answers. Cheers, Nenad Am Freitag, 12. Februar 2016 15:07:28 UTC+1 schrieb Propadovic Nenad: > > Hello everybody, > lets say I want to create a @clean (Python) file and I want to attach > comments to some nodes. > I imagine those comments being child nodes of

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

Very nice "aha!". My take on this: In effect, consider starting with a bunch of entities, with no particular structure relating them to each other. (I don't say "nodes", because that already implies a structure.) For example, imagine a community of people, each an individual, but who