Anjuta 2.4

15. March 2008

So, I haven’t yet written about our new release, the first one that is included in mainline GNOME. Partly motivated by Miguels’s post on MonoDevelop (which would actually share a lot of code with anjuta in case they hadn’t rewritten all the libraries in C#) I will present the new and improved features. Some were already mentioned in an older post.

Editing

Code editing is probably the most essential part of an IDE. While it’s pretty unlikely to convert people using vim/emacs to an IDE we at least try to make people happy that have used IDEs on other operating system or are coding using GEdit. There have been plenty of improvements in code completion and auto-indentation in this release and it should work pretty well for C/C++ now. We always look for people to write language-support plugins for more languages (yeah, it’s easy…). This release also features the latest and best version of GtkSourceView.

Autocompletion and calltips in action

In addition we also improved the way to quickly search in a file using the new “Quick Search Bar”. (c) of this is probably from the vim/emacs and firefox developers, but why shouldn’t we copy it if it’s good!

Quick search bar

UI Design

With this release we made a big step towards better glade integration also thanks to the glade-3 developers. The old and ugly “Glade”-menu is now gone and instead the “File” and “Edit” menu items will now also work on the opened glade file. And the glade file is displayed like any other source file in the central editor window.

anjuta-glade.png

But there is still room for improvements!

Version Control

The Subversion plugin was improved in many ways and it a pleasure to use now. It gives you much better control over operations then the command line frontend. You can for example select which files to commit, resolve conflicts and view logs now in the GUI:

anjuta-subversion.png

The great work on subversion plugin was done by James Liggett (who is looking for a part-time job in case you need a talented GTK+ hacker…).

Debugger

With this release, the debugger doesn’t suck any more. You can debug your code with nearly all features available from gdb, inspect variables, set breakpoints, set watches, etc. And it’s rocking stable now and should make your live on killing bugs much easier:

anjuta-debugger.png

Thanks!

Thanks to everyone who made this release possible, especially, Naba, Sébastien, Massimo, James, Tom, Rob and all the translator who fought this 1700 string monster (and reported all these l10n bugs).

Future

Anjuta follows the GNOME approach to try to keep things simple and our Roadmap reflects that. The goal is to make the existing features perfect before adding yet another. Of course that does not mean we are not interested in new plugins. Everybody who wants to contribute is highly welcome, especially for supporting more languages.

12 Responses to “Anjuta 2.4”

  1. Marcelo Lira Says:

    >>While it’s pretty unlikely to convert people using vim
    Of course you can! Just embed the vim editor and make it an option to gtksourceview. ;)

  2. knipknap Says:

    > Just embed the vim editor and make it an option to gtksourceview. ;)

    Heh, I was going to suggest that. I’m still waiting for a “:vs”-capable embedded editor.


  3. Fantastic update on Anjuta!

    I wish people blogged more frequently about it, as it does not get all the exposure that it deserves.

    Miguel.

  4. Rui Says:

    > (which would actually share a lot of code with anjuta in case they hadn’t rewritten all the libraries in C#)

    Can the gobject introspection work help with this? I mean, woulnd’t it enable us to use a widget written in python inside a C app?

  5. Rui Says:

    [hit the Submit button too soon]

    Obviously you’d have to load the python runtime onto the C app. I think that would still leave out the use of a C# widget on a python app… This balkanisation surely isn’t good :-(

  6. jhs Says:

    @Rui:
    It’s not the problem of the language. They could have used gdl (written in C) in MonoDevelop but for some reason they decided to rewrite the whole library in C#.


  7. Hello,

    Correct, we did rewrite a number of libraries that used to be written in C in C# because it gave us more agility and allowed us to quickly fix bugs, fine-tune the IDE and get the desired user experience that we were looking for.

    Miguel.


  8. Update: as it turns out, for some reason we never used the unmanaged Gdl, someone ported that code to C# from the start. Michael Hutchinson provided some of the feedback.

    Over the years there were a few issues with this port, I quote Michael:

    “1. It was GPL, because it was forked before GDL was relicensed; 2. there were some issues related to crashing with certain styles due to the way it used the style object; 3. it wasn’t easily possible to implement autohide; 4. and because the pads were grouped using a GTK notebook, there was a border that we were unable to remove, and we wanted to reduce dead space in the layout. So there were a whole bunch of reasons, basically”

    As to why we ported Gdl initially, it is going to be hard to track that down as Todd who seems to be the author has long left the project.

    Miguel

  9. reinouts Says:

    Arggh! Close buttons do NOT belong on toolbars, whether the Mozilla guys do it or not. We just got this fixed in Yelp, now Anjuta comes along with this nonsense. :(

  10. jhs Says:

    @rainouts: What would you propose instead of gthe close button? There is no other way to hide the search bar (which is no toolbar in the technical sense).

  11. Ray Says:

    It’d be cool to see Anjuta also have optional support for the ZeroBUGS debugger (http://www.zero-bugs.com/) along side GDB.

  12. Naba Kumar Says:

    Hi Johannes, Very nice write up. Thanks and you rock :)


Comments are closed.