I will meditate on what feels the least confusing and least cluttered.

On Wednesday, August 26, 2015 at 12:07:46 PM UTC-4, Terry Brown wrote:
>
> On Wed, 26 Aug 2015 08:50:13 -0700 (PDT) 
> john lunzer <lun...@gmail.com <javascript:>> wrote: 
>
> > As C.S Lewis put it, “if you do one good deed your reward usually is 
> > to be set to do another and harder and better one.” 
> > 
> > I can certainly attempt to extend that dropdown to add in "below 
> > current node" or something a little shorter. 
> > 
> > For the other functionality what did you have in mind? Were you 
> > thinking "Changed" and "Timeline" buttons over next to the combo box? 
>
> Well, I'd be inclined to sneak them into the combo. just to save 
> space... would mean checking the change event on that combo, but 
> otherwise similar to buttons.  Unless you think it's confusing vs. what 
> should happen when search text is entered - I guess when "Changed" or 
> "Timeline" was selected it could just display the relevant list and 
> then change the combo. back to "All". 
>
> Cheers -Terry 
>
> > On Wednesday, August 26, 2015 at 11:32:28 AM UTC-4, Terry Brown wrote: 
> > > 
> > > On Wed, 26 Aug 2015 07:53:09 -0700 (PDT) 
> > > john lunzer <lun...@gmail.com <javascript:>> wrote: 
> > > 
> > > > I've done limited testing. This is my first commit that is likely 
> > > > to affect many other people's daily flow. Please let me know if 
> > > > I've broken anything. 
> > > > 
> > > > Also comments are welcome on my changes. I had to copy out some 
> > > > code out of leo core into one of the quicksearch classes to 
> > > > enable subtree and node only searching. It's a little messy... 
> > > > 
> > > > Anyway this is a feature I've wanted for quite some time. 
> > > 
> > > Very nice - I've often found myself wanting subtree only in 
> > > quicksearch. Now that you've got the UI set up, another variation 
> > > would be "Following nodes" only - hmm, hard to pick a descriptive 
> > > term, but I mean sometimes I've wanted quicksearch to only search 
> > > this node and nodes "below" it in the outline, i.e what you get 
> > > from calling p.threadNext until p becomes invalid.  That would 
> > > iterate clones multiple times though. 
> > > 
> > > In fact... now you've extended the interface, I wonder if there's a 
> > > convenient way to provide access to some of the other things you 
> > > can display in the Nav pane - find-quick-changed and 
> > > find-quick-timeline show nodes that have changed since last save, 
> > > and nodes in most to least recent creation order.  See how you good 
> > > work is rewarded ;-) 
> > > 
> > > Cheers -Terry 
> > > 
> > 
>

-- 
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 leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Reply via email to