Okay, going to try to keep this short and simple(both being subjective). Basically, I went through the last Find Bar thread and couple of JIRAs(but not all), and tried to come up with a list of options, suggestions, and discussion points, so that, hopefully, we can reach a consensus on a way to make the new find bar work as well as it can for everyone. This is just a bit of brain storming, so, well, you know how that goes....
So, please, if you can, keep an open mind and keep on topic, and lets see if we can come to some mutual agreements. Let's assume the new find UI is here to stay and build constructively on that.
And, if you already have a JIRA opened for one of these, please posted to this thread.
The following, I would say, would be set in Setting, under Editor, on the Behavior Tab. They are for general behavior characteristics of the find bar: when, where, and how.
1 - Default - What is currently does today - Appears for the current tab and stays there until you close it(ESC, click the X)
2 - Persistent: Is always there, on all edit frames/tabs. Ctrl F simple takes to your the text entry box. ESC and clicking the X(which probably would not be there) don't make it go away.
3 - Transient: As soon as it loses focus, it goes away; usually after the user has pressed Enter or clicked Find Next/Prev.
4 - Pop: Back to the old pop-up window.
Note, item 4 might not be an option, but simply an available key binding.
Focus on Find:
1 - Find Box/Bar - basically the default as it is now, the cursor stays in the find box.
2 - Editor window as soon as Enter/Find Next/Find Previous is used - That way, you can begin editing without.
Focus on Find is not available for Transient Mode.
1 - Top of Edit Window
2 - Bottom of Edit Window
3 - Toolbar(for those that have room)
4 - *Floating - Remember Position - Always appears in the same spot when opened
5 - *Floating - Above/Below cursor(only available when Mode is Default or Transient)
4 and 5 might be a bit extreme, but it might solve the problem for those that liked the old pop-up and don't want the find bar attached to their edit/edit windows. In short, using 4 or 5 in the default or transient mode gives behavior somewhat like the old find popup.
The following are for the find bar(and some already exist).
Find Bar Options:
- Case Sensitive
- Whole Word Only
- Highlight All - If turned off, then it just goes from match to match, no highlighting or marks.
- Scroll to match while typing - If this option is turned off, idea does nothing until the user presses Enter or Find Next/Prev
- *Find In "Selection"
- Ability to perform a Find All. This could be a button next to the Find Next/Prev buttons
- Key Bindings specific for the find bar(when it has focus), such as using Ctrl-R to toggle Regex, instead of having to click with a mouse.
- I think you could make the find bar a little more compact if you replace the check boxes and text with toggle buttons(with tool tips), just like those you used in the project or structure panes.
Lastly, a few general issue/concerns I read about, but did not have any additional thoughts on. So, if you have any additional thoughts on these, now is the time.
There were some issues expressed about Regex. Not sure if they have been addressed or not.
Concerns about Incremental Search. Again, not sure if they have been fully addressed.
Anything else I forgot.
As a final thought, because, depending on their implementation, there is a risk of the find bar getting too busy; though using toggle buttons instead of check boxes and text would help.
However, it might not be a bad idea to have an option on the Find Bar UI(like and Advanced button) that points the user to the old Find popup or an updated version of the Find In Path, where maybe some of the less used options would be located.
Though, if that was done, I would love to see the Find popups made non-modal; not even sure why they are modal.
Message was edited by:
zmbs - Added Find In "Selection" as a find bar option. Also added some Closing Thoughts