Re: g.findNodeAnywhere() question
On Tue, Mar 10, 2009 at 6:33 PM, Kent Tenney wrote:
> I've been wondering how to do a global search for headline text,
> I was pleased to see this mentioned.
>
> What would the preferred way to be to deal with multiple nodes
> with the same headline text?
>
> Is there a method like g.findNodeAnywhere_iter() ?
Perhaps this would be the time to move my 'select()' proposal forward:
http://groups.google.com/group/leo-editor/browse_thread/thread/d8362a15c05697ff
The code is already done, all it needs is adding c.find_h() to controller.
So basically, you would find nodes by:
c.find_h('Gui wrap.*').select(".*Qt").select('Font')
I can add it to trunk if it's ok for Edward / others.
Let's avoid function names like findNodeAnywhere_iter... they are an
absolute nightmare to remember.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To post to this group, send email to leo-editor@googlegroups.com
To unsubscribe from this group, send email to
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---
Re: Execute command on node
Using the nodeActions plugin you can run the 'write-restructured-text'
command when an "@rst ..." node's icon is double-clicked.
nodeActions' pattern = "@rst "
Pattern's script = "c.executeMinibufferCommand('write-restructured-
text')"
See the documentation on the nodeActions plugin in the Leo Users
Guide.
(Access your local copy of the Users Guide from the "Help" menu. The
web version has not been updated with the latest changes.)
TL
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To post to this group, send email to leo-editor@googlegroups.com
To unsubscribe from this group, send email to
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---
Re: "Mylyn" for leo (ineresting vs. uninteresting nodes)
On Tue, Mar 10, 2009 at 2:14 PM, Ville M. Vainio wrote: > > Mylyn is particularly cool plugin for eclipse: http://www.eclipse.org/mylyn/ > > What's the most compelling feature from leo perspective is that some > nodes are more "interesting" than others. Interesting nodes are: > > - Nodes that have been edited recently (today? this week?) > - Nodes that have been "looked at" (scrolling around the node, trying > to "find" something in the node, nodes that give good match in search > results...) > - Nodes you explicitly mark as interesting > - New nodes, nodes you have pointed clones at > - Parents of interesting nodes > > Mylyn maintains "interest score" for files/ functions, which map > directly to leo nodes (though having persistent gnx's for auto nodes > would help). This would be so nice, I really like gnx's being timestamps, I really like @auto, I really wish the gnx for @auto was useful as a timestamp. All you need to do is to maintain an interest database > for nodes, and colorize the nodes by interest (interesting nodes are > bold, very uninteresting ones are italic). You would also have "expand > interesting nodes to view" button. > > Note how interest is calculated continuously & automatically, contrary > to systems where you need to "bookmark" interesting nodes explicitly > e.g. with icons. > > Interest score decays with time, as the focus of your work moves on. > > Mylyn's interest database can be switched according to task at hand > (e.g. "now I'm working on task bugfix_123, set interest db > accordingly"). This is of course a piece of cake to implement by just > switching the interest db. > > All in all, this should be pretty easy to do with what we have > currently. Now it just has to be done :-). > > -- > Ville M. Vainio > http://tinyurl.com/vainio > > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-editor@googlegroups.com To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~--~~~~--~~--~--~---
"Mylyn" for leo (ineresting vs. uninteresting nodes)
Mylyn is particularly cool plugin for eclipse: http://www.eclipse.org/mylyn/ What's the most compelling feature from leo perspective is that some nodes are more "interesting" than others. Interesting nodes are: - Nodes that have been edited recently (today? this week?) - Nodes that have been "looked at" (scrolling around the node, trying to "find" something in the node, nodes that give good match in search results...) - Nodes you explicitly mark as interesting - New nodes, nodes you have pointed clones at - Parents of interesting nodes Mylyn maintains "interest score" for files/ functions, which map directly to leo nodes (though having persistent gnx's for auto nodes would help). All you need to do is to maintain an interest database for nodes, and colorize the nodes by interest (interesting nodes are bold, very uninteresting ones are italic). You would also have "expand interesting nodes to view" button. Note how interest is calculated continuously & automatically, contrary to systems where you need to "bookmark" interesting nodes explicitly e.g. with icons. Interest score decays with time, as the focus of your work moves on. Mylyn's interest database can be switched according to task at hand (e.g. "now I'm working on task bugfix_123, set interest db accordingly"). This is of course a piece of cake to implement by just switching the interest db. All in all, this should be pretty easy to do with what we have currently. Now it just has to be done :-). -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-editor@googlegroups.com To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~--~~~~--~~--~--~---
Re: Proposal: making tree widget color, tooltip, whatever plugin configurable
On Mon, Mar 9, 2009 at 10:15 PM, Ville M. Vainio wrote: > Should I push a demo implementation (few small changes to core & a plugin)? I have now pushed an example plugin & necessary core mechanics to trunk (and ran unit tests ;-). Included is colorize_headlines.py, a plugin that makes @auto, @shadow, @thin nodes bold. This can be used as starting point for cleo-like functionality (i.e. provide ui for setting node colors). The (trivial) meat of the plugin is here: http://pastebin.com/m69844a62 -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-editor@googlegroups.com To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~--~~~~--~~--~--~---
Re: Execute command on node
Thanks c.selectPostion(p) works P.S. Is there a read-at-auto-node with no 's' to work on a single node, I think the nodes plural case finds and operates on all @auto nodes in a tree --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-editor@googlegroups.com To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~--~~~~--~~--~--~---
g.findNodeAnywhere() question
I've been wondering how to do a global search for headline text, I was pleased to see this mentioned. What would the preferred way to be to deal with multiple nodes with the same headline text? Is there a method like g.findNodeAnywhere_iter() ? Thanks, Kent --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-editor@googlegroups.com To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~--~~~~--~~--~--~---
Re: Execute command on node
On Tue, 10 Mar 2009 08:37:51 -0700 (PDT)
mdb wrote:
>
> How can I make a minibuffer command operate on a particular node
> I.e. turn
>c.executeMinibufferCommand('write-restructured-text')
> into
>p.executeMinibufferCommand('write-restructured-text')
> where p is a node
>
> If I use c.executeMinibufferCommand('write-restructured-text')
> I can get log message 'No @rst nodes in selected tree'
oldp = c.currentPosition()
c.selectPosition(p)
c.executeMinibufferCommand('write-restructured-text')
c.selectPosition(oldp)
would be my guess, possibly
oldp = c.p
c.p = p
c.executeMinibufferCommand('write-restructured-text')
c.p = oldp
is an alternative now, can't recall, try it and see.
Cheers -Terry
> >
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To post to this group, send email to leo-editor@googlegroups.com
To unsubscribe from this group, send email to
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---
Execute command on node
How can I make a minibuffer command operate on a particular node
I.e. turn
c.executeMinibufferCommand('write-restructured-text')
into
p.executeMinibufferCommand('write-restructured-text')
where p is a node
If I use c.executeMinibufferCommand('write-restructured-text')
I can get log message 'No @rst nodes in selected tree'
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To post to this group, send email to leo-editor@googlegroups.com
To unsubscribe from this group, send email to
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---
Re: Importing an @thin file
> Please explain what you are trying to do, and why simply using an @thin node > won't work. I see I have created some confusion so let me try to be as clear as possible. I am trying to use @thin nodes but I am trying to create them by importing existing @thin files. In more detail -- I work with a bunch of @thin files that are housed in an SVN repository. It is not infrequent that I want to work on one of the @thin files in some temporary .leo file or that I want to create a new .leo file that may contain n of the @thin files. The only way I know to get existing @thin files into a new .leo file is to use the import derived file command. My problem is that doing that is not working (for me) with the QT version of leo. For some reason, it appears to import the @thin file into the @thin node but the only structure under that @thin node is the top level nodes -- all the rest of the @thin file is missing. Again, to be as clear as possible, I do this all the time in the tk version and it works so there is something about the qt version or in my particular installation that is causing the import of an @thin file to produce an incomplete representation of the @thin file. I realize now that I should try saving the .leo file with the apparently incomplete @thin node and see if saving or saving and reopening the new .leo file causes the full @thin file to appear but that shouldn't be necessary. Existing .leo files which point to these @thin files behave normally in the qt plugin -- what is broken for me is importing existing @ thin files into a new .leo file using the import derived file command. Steve --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-editor@googlegroups.com To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~--~~~~--~~--~--~---
Re: RST3 -- Latex -- Beamer -- PDF
Nevermind on
> Where can I find a list of all c. p. and at. functions
I think
c.executeMinibufferCommand('open-outline')
will be enough. Minibuffer commands seem easier to find
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To post to this group, send email to leo-editor@googlegroups.com
To unsubscribe from this group, send email to
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---
Re: RST3 -- Latex -- Beamer -- PDF
Thanks I'll try > p = g.findNodeAnywhere(c,headline) and/or > p = g.findNodeInTree(c,p,headline) > > (2) read each line in a node as if it was a text file or input > > stream > > I'm not sure I know what you mean. Can you explain? I simply wanted the node body as a string to manipulate in a python script and s=p.bodyString() does what I need Where can I find a list of all c. p. and at. functions like the list shown with Help-Print Commands I am assuming Chapter 7 Scripting with Python does not have everything or do I need to simply explore LeoPy.leo. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-editor@googlegroups.com To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~--~~~~--~~--~--~---
Re: Importing an @thin file
On Mon, Mar 9, 2009 at 6:51 PM, Steve Zatz wrote: > > > I don't see this behavior, either on Ubuntu or XP. > Well that just makes it more interesting ... Please explain what you are trying to do, and why simply using an @thin node won't work. Edward --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-editor@googlegroups.com To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~--~~~~--~~--~--~---
Re: RST3 -- Latex -- Beamer -- PDF
On Tue, Mar 10, 2009 at 6:17 AM, mdb wrote: > > Never mind about > > To move forward, how can I > (1) find a node with a certain headline > You can use p = g.findNodeAnywhere(c,headline) and/or p = g.findNodeInTree(c,p,headline) > > (2) read each line in a node as if it was a text file or input > stream > I'm not sure I know what you mean. Can you explain? Edward --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-editor@googlegroups.com To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~--~~~~--~~--~--~---
Re: Proposal: making tree widget color, tooltip, whatever plugin configurable
On Mon, Mar 9, 2009 at 3:15 PM, Ville M. Vainio wrote: > > On Mon, Mar 9, 2009 at 8:12 PM, Edward K. Ream > wrote: > > >> This would configure individual nodes - e.g. allow storing colors in > >> uAs, as in cleo plugin. > > > > Oh. I'm with you now. > > Should I push a demo implementation (few small changes to core & a plugin)? Yes, provided all unit tests pass. Edward --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-editor@googlegroups.com To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~--~~~~--~~--~--~---
Re: Moving clones
On Mon, Mar 9, 2009 at 2:07 PM, vitalije wrote: > > > I think you should use command "Paste Node as clone" from outline menu > instead of Paste Node. Yes, you could do that, but p.moveAfter, p.moveToNthChildOf, etc, are much more efficient: a few links are changed and nothing is written to the clipboard. Edward --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-editor@googlegroups.com To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~--~~~~--~~--~--~---
Re: Problems manipulating nodes
On Mon, Mar 9, 2009 at 7:55 PM, mdb wrote: > > -- double clicking a node does not work as it should (i.e. write a > @file node) Interesting. I never thought of doing that. It would make sense. There are two ways of writing @ nodes: save the .leo file (ctrl-s) or write-at-file-nodes (ctrl-shift-w) > > -- can not drag and drop nodes You can do this with tk, but not yet with qt. > > -- commands in mini-buffer do not work Clicking in the minibuffer will not work, I think. Instead, enter the minibuffer with Alt-x. Edward --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-editor@googlegroups.com To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~--~~~~--~~--~--~---
Re: RST3 -- Latex -- Beamer -- PDF
Never mind about To move forward, how can I (1) find a node with a certain headline (2) read each line in a node as if it was a text file or input stream I figured out how to use p.headString() and p.bodyString() --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-editor@googlegroups.com To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~--~~~~--~~--~--~---
