Well I’m not sure this really qualifies as an update, because it is actually a new plugin. And the plugin I’m talking about is the Search plugin. This is going to be mostly a series of screen-shots.
The first shot contains the “new” feature differentiating itself from the other one. You can now select to search in the currently open files. This is especially good if you are working on files on a remote server.
The “Find in files” plugin opens new searches in new toolviews while this one has a button for adding new tabs if you want to save the old search.
Of course you can also search in a folder as before 🙂 When you select to search in a folder the folder searching specific options are displayed. Those options can also be toggled with the rightmost tool-button.
And the final screen-shot is to show that it is possible to use regular expressions.
The “Replace” feature is not yet implemented, but who knows 😉 Ideas for a UI are welcome.
And that was it for this time. I hope you like the updates 🙂
Second out in the this series of plugins update is the GDB plugin which has gained a view for local variables. If you have GDB pretty printes in use, you can even get various Qt types displayed nicely. Here are direct links to the relevant printers and an example .gdbinit: qt4.py, libstdcxx.py and kde4.py.
The locals view does not (yet?) have any fancy features as editing the values and does not show which variables have changed.
The handling of breakpoint and execution markers has also improved a bit.
Last but not least in this series will be the new “Search in files” plugin.
KDE SC (or was it Platform?) 4.7 will bring some enhancements to Kate plugins. First up is the build plugin. The new thing for the build plugin is the ability to specify multiple targets per session. This means that you can build debug/releas/… targets without having to jump between sessions. The default setup/targets contain a configure target with a CMake command and a build target that runs make.
Targets can be added, copied and deleted. If the last target is deleted the default targets will be re-added.
When the targets are set up, you can of course select a specific target by selecting the settings tab and there select the desired target from the small combo box. To make target switching faster, there is a “Next Target” action. This action will switch to the next target in the target combo-box. If the settings tab is not visible it will open the tab to display the current target. There is no default shortcut-key for the actions, but fortunately it is not hard to change a shortcut in KDE applications 🙂 My personal shortcut-setup can be seen in the build-menu screen-shot.
Have you, like me, had to switch to an external debugger or run raw gdb in the terminal plugin to debug the C/C++ application you develop with Kate? That might not be necessary any more. There is now a “GDB Plugin” in trunk that gives you the power of raw GDB with some QAction candy for the most common actions.
I have always been a bit frustrated with not having a debugger directly in Kate, but too lazy/busy to start a debugger plugin project. Fortunately Ian Wakeling started this GDB plugin and got it off the ground. When I got introduced to it at Akademy, it triggered an itch in me to get this plugin into kdesdk and to add some features for the more point and click type of persons. As it seemed I had a bit more free time to spend on the plugin, Ian let me take over as maintainer.
Main features of the plugin:
– Jump to the corresponding file and line whenever gdb stops.
– Insert and remove breakpoints.
– Tool-bar buttons for the most often used actions like step into/over/out. Those actions can of course also be assigned to keyboard shortcuts.
– Execution markers and breakpoint markers on the icon border.
– A call stack tab for point and click navigation of the call stack.
– Optional IO redirection to a separate tab.
– Printing the value of the currently selected variable or expression. QStrings and friends are not supported (yet?).
– And last but not least. A GDB console for the full power of GDB.
And now the screen-shots
GDB Console, execution marker and a breakpoint marker.