Don't you think nodes should have attributes? I know each node has a dictionary, which is very handy, and I know about the attributes plugin, which shows the selected node attributes. But this is not what I mean.
I mean standard attributes. IMO, directives should also be attributes of a node. This would be a problem since directives wouldn't be easy to spot, so I then we should set an open source icon<http://www.veryicon.com/icons/system/red-orb-alphabet/>for each directive. When a node has attribute "invisible", it has also an invisible icon on the left of the main icon. When a node has "button" directive, it has a button icon on the left of the main icon. (I call main icon to the current existing icon). Etc. For this to work, the given icons should keep the size ratio (right now, if you put 3 or more icons on a node, they will begin to shrink). Just wanted to share the thought, I think it could be more straight forward than now for newbies, since the name of the nodes would be cleaner that way, and the visual information goes quicker to the brain than the "@blabla " directives. Also, a right-click menu with the list of all possible directives (attributes) with their icons, would be very handy when you want to create "special" nodes and you are newbie. The no-edit, invisible, @rst, and the rest of directives, are what usually in other programs you can right-click then specify, because they are properties of the item you are right-clicking on. I found very tough when I was starting to hit right-click then only find a few posibilities, and not been able to set standard properties such as those. Hope this was not too much off topic. On Thursday, September 19, 2013 4:25:29 PM UTC+2, Terry wrote: > > On Thu, 19 Sep 2013 09:02:05 -0400 > Jacob Peck <[email protected] <javascript:>> wrote: > > > As the subject states, I'm wondering if there's any way to create a > > hidden node in an outline, one that's not visible to the user through > > the tree pane, but still accessible through the API. > > p.v.u, but the node's still visible, and subject to deletion. > > What about... > > c.hiddenRootNode.u - nope, .u isn't saved on that, too bad, that would > have been a handy spot for 'in the .leo file' hidden data. It's not > just a matter of changing the code to save .u for c.hiddenRootNode, the > parent of "top level" nodes, c.hiddenRootNode has no representation in > the .leo file. > > Seems like the simplest would be > p.h = "SETTINGS - DON'T DELETE" > p.b = "Invisible settings attached to the node - don't delete" > p.v.u['your_data'] = your_data > > Cheers -Terry > > > I'd like to store some data in an outline that shouldn't (easily) be > > editable by the user. I don't want to use the db for this, as I want > > the outline to be sharable. > > > > Any clues? Or is this a lost cause? (If it is, I'll just create a > > @please-dont-edit-this node or something). Or encrypt it. > > > > Thanks, > > -->Jake > > > -- 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/groups/opt_out.
