Editor Improvements
Collection of ideas how to improve the new QScintilla based editor.
Add pop-up search/replace screen with functionality similar to the Notepad++ one. The core functionality should be available via the QScintilla find function.
Allows session-dependent or persistent bookmarks for each code file
- Bookmarks are set on specific lines in the code and marked in the margin area
- Tricky bit: they need to move when code is added above them (hopefully there's some support in Scintilla)
- Needs Button / Shortcut to:
- Toggle bookmark in one place
- Go from cursor to next bookmark
- Go from cursor to previous bookmark
- (Maybe later) display list of bookmarks
A drop-down list in the "Find" text box to list the history of past find;
Backward (<=) and forward (=>) buttons like what we see in browsers.
Quote from Mailing list: "What I have in mind is to go to previous/next cursor location. Say if a function b( ) uses function a( ), but something goes weird, I wanna check what's wrong about a( ), so I browse to a( ), make some changes, then wanna go back to b( ), This process might go some back-and-forth several times. Back/forward for switching file is a good idea, too"
Quote from Mailing list: "It first I though tabs wouldn't be good, noting MDI. Each file needing it's model display. But now thinking of use cases where you have include files, but will need to have, say the first tab as the master tab - hence that which is displayed in the 3D view. ??"
Able to open a predefined set of files.
One way to speed up the navigation is to be able to split the screen. Or, if the screen gets too small after the splitting
Displaying different parts of the same file into different tabs so we can edit different parts separately. I've never seen anything like this, though.