Skip navigation.

The anjuta story

Anjuta
Anjuta

It was back in 1999 when Naba Kumar released the first buggy alpha version of Anjuta, an IDE for GNOME which should pack together all the great command line development tools in linux and make software development easy on GNOME desktop.

Anjuta2 Screenshot

Many people were interested in the project as Naba was very productive. Eventually the codebase grew, features were added, bugs were fixed and the IDE began to become very usefull. Anyway the frist stable release was made in 2002, Anjuta was not complete but it was an easy to use IDE, supported GNOME and GTK Projects in C/C++ and could also handle a couple of other languages.

After the release there were many discussion on how to improve the IDE and soon it came up that the design was too limited for future additions. Being based on old technologies, extending the IDE to add new features was becoming more and more challenging and less interesting. Then a decision was made to re-implement the architecture using newer gtk+ technologies which were not available then.

Incidentally, at that time revival of another project, gIDE, to attend the similar goal of an extensible IDE was undergoing. On 11/9/2001 the former gide developers and the Anjuta team decided to merge the two gnome ide projects. The new base for the development was the anjuta2 module but the new plugin code came mainly from the gide project.

In this time GNOME 2.0 was released which meant that Anjuta 1.0 did no longer fit very good into the rest of the Desktop because it used the old gnome 1.4 libraries. It became clear that anjuta2 would take a long time until it could replace Anjuta 1.0 so the developers decided to port Anjuta 1.0 to GNOME2 and to develop anjuta2 in parallel.

While this was a good decision development concentrated on Anjuta 1.2 the GNOME2 branch of Anjuta 1.0 because many people used Anjuta 1.0 and wanted to improve it and it was much easier to work on a working platform than on a design skeleton. Besides porting, many new features where added to Anjuta and Anjuta 1.2 became a much better application than Anjuta 1.0. On the other hand development of anjuta2 stopped more or less.

After Anjuta 1.2 was released in 2003 development of anjuta2 became more priority but there were disagreement between the two developer groups which ended up in the renaming of anjuta2 to scaffold. Scaffold was mostly developed by the former gide developers while Anjuta 2.0 was now developed on top of the old Anjuta codebase but with a new architecture. The goal of Anjuta 2.0 is to utilize all features of older Anjuta and to maintain the [release] continum, albeit in a new framework. All this resulted in some confusion in the community and people eventually started to think that both projects were dead.

Anyway, Naba always believed in his vision and implemented the plugin system and ported some older functionalities as plugins for Anjuta 2.0. Some codes were reused from former anjuta2 and the design is totally based on GTK+. Beginning fall 2004, the codebase reached some kind of usability and other developers were again interested at the project. The number of commits raised and now many functions of the IDE are working and it's getting better every day. After going low for about a year, Anjuta 2.0 is now finally ready for the prime time.

A Beta release is expect in early Febuary.

There is an unfortunate rumor that scaffold is no longer an active project. However, it should be noted that Anjuta 2.0 utilizes some cool libraries mainly developed during gide/scaffold era, namely gdl (gnome-development-library) and gnome-build framework.

What to expect from Anjuta 2.0?

Here is a wiki article that describes changes in Anjuta 2.0, along with some screenshots:
Anjuta2 Wiki

For more information about anjuta visit http://www.anjuta.org, post a message to anjuta-devel@lists.sourceforge.net or join #anjuta channel at GimpNet.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Abstract descriprtion of languages

The emacs development environment contains a package named named semantic. This package allows you to add parser and lexer support for a new language without recompiling everything. Would it be possible/meaningful to add something similar to Anjuta?

http://cedet.sourceforge.net/semantic.shtml

PS: Thanks to the developers for a great program.

MOST important feature

Please clean up the whole preferences dialogs. They were a mess in 1.x and brought much aggrivation when a persion wants to change an annoying feature and it takes him 15 minutes to find it!

Most important feature!

Tab working like Emacs. Right now you can choose multiple ways to indent your code - which all sucks.
If Anjuta worked like Emacs, I would be in heaven. And, no, I do _not_ want to use emacs in anjuta. I just want anjuta to use emacs tab.

What's so special about emacs

What's so special about emacs tabs? I don't think Anjuta tabs suck. In fact, to me they looks like all the other tabs around :)

In fact, to me they looks lik

In fact, to me they looks like all the other tabs around :)

This is exactly the problem.

In emacs, when you press tab, it indents it intelligently according to the code, no more, no less.
This can also serve as a quick way of checking that the syntax is correct, and you haven't forgotten to close a parenthases - if the indentation is back or forward from what you expect, check again.
It means you can open a bit of code you wrote and see what parts are inside a loop, what are part of the main program instantly.
If you press tabs twice, it indents only once.
Very useful when breaking large statements on several lines -
for example print(something,
another something, something3);
The print statement looks perfect in emacs, since "another something" is alligned with "something".

Gedit tabs (I haven't used Anjuta, but you claim that they're the same) indent a fixed amount everytime you press tabs. No degrees, no difference between the if statement and the block it runs (which is more indented in Emacs), unless you line up the tabs manually.

To summarize - emacs tabs equal "indent this line according to syntax".

If Anjuta can indent code, then implementing this should be easy. If it can't indent code logically, than Anjuta isn't so hot anyway.

Emacs tab style

Hi!

Possibly anjuta will support this in the future as an option. I found it very useful in emacs but I don't know how it is implemented. If someone can give me a hint I will try on it. But please don't tell me I have to scan the emacs code because that's far to much code and I don't know anything about it.

glade3 and gtkmm

hello gnomers,

anjuta2 is looking really nice. got some questions though: what's the status of glade3? last time i looked it seemed like a dead project... and will anjuta2 have a more integrated c++ support, particularly with gtkmm?

cheers,

marco

If you look at the CVS you wi

If you look at the CVS you will see some work in the before the last 4 weeks.
One great things in glade 3 is the widgets pallet widget :)

Eduardo de Oliveira Padoan
http://edcrypt.cjb.net

Ruby with anjuta?

Hi,

I am looking for a good IDE for Ruby-Programming. There is a ruby-plugin for eclipse, but eclipse is too slow for me on my machine and gedit has not enough features. Do you know, if it will be possible to use Anjuta for Ruby?

Currently Anjuta does not support any kind of ruby-files.

The Anjuta-2 screenshots really look fantastic. Powerful but not too much buttons and toolbars. Just Gnome/Gtk :)

Can't await

Mike

IRC channel doesn't exist

There is no #anjuta on irc.gimp.net

Code completion/IntelliSense

Will Anjuta2 support code completion/IntelliSense, ala Borland Delphi? For example, type gtk_button_cl, press Ctrl+spacebar, and a list box will pop up with all function names that start with "gtk_button_cl". We have tools for creating dependancy graphs, syntax highlighting, API documentation, etc. but why STILL no code completion in 2005?

The "tag" support is almost there, but not quite. Why do you have to manually generate a tag file? Why can't it parse headers on-the-fly like Delphi does? Why do I have to use a project in order for it to work?

But I'm definitely looking forward to the Glade integration. Delphi allows me to jump to a control's callback function just by doubleclicking. On Linux I have to Alt+Tab, open my text editor, open the right file, and scroll to the right line.

Implemented a long time ago..

Will Anjuta2 support code completion/IntelliSense, ala Borland Delphi? For example, type gtk_button_cl, press Ctrl+spacebar, and a list box will pop up with all function names that start with "gtk_button_cl"

You mean like this ?

RE: Code completion/IntelliSense

Funny. This works for me when editing PHP files with Anjuta, using the default build of Debian Testing!

Claus

Anjuta 2.0-pre screenshots

More screenshots here.

Integrated Glade 3 ;)

bye bye Kdevelop .. (bye bye QT)
this will rock solid ;)

I use Anjuta a lot myself, mo

I use Anjuta a lot myself, mostly for javaprogramming. I realy think it's a nice working, nice looking project, but I haven't jet discovered the use of the debugger. Once whith the borderland program, I just pressed F7 or something, now when I ask Anjuta to start the debugger it says: No runable file for this file. What am I suposed to do?

Maybe you haven't heard of ec

Maybe you haven't heard of eclipse but in my experience it is one of the best of not the best dev env for Java. It also does some C/C++ but it is fairly limited. I prefer Anjuta for Gnome and gtk+ dev. Well for pretty much any C/C++ program. It it not quite as usefull as VS6 but it is getting there. Plus I really hate the newer versions of VS and some features of VS.
Anyway, great job anjuta developers! I can't wait for anjuta 2 ... now if only all my clients would switch to gtk+/gnome ...

Well I've heard a litle about

Well I've heard a litle about eclipse, but I don't realy know what it is and what it looks like. I'd very much like to try it, as I sometimes think Anjuta isn't that Java optimized, when I'm typing Java functions, it allways gives me the name of some C function etc.
I've tried to install eclipse, but I went into some large dependency nightmare. Maybee adding jPackage to apt will help, but what exactly is eclipse?

www.eclipse.org You can down

www.eclipse.org
You can download gtk version of it (use libswt library)

Its about 80MB. Just download it, and execute.

Khiraly

Hm, it's 92MiB, and I would h

Hm, it's 92MiB, and I would have liked it as an rpm, but well, I'll try it. Is it as beatyfull as Anjuta?

Re: Eclipse

Eclipse/GTK is better looking than Anjuta.

It also has the best plug-in/extension architecture of ANY IDE... ever. IBM really hit one out of the park with Eclipse, SWT and JFace.

When you get a chance, google for Eclipse plugins. It has everything. :)

Check the wiki

The wiki says that file navigation has been changed and is now based on mime so that should help some. Also you would apparently be able to change the editor to say emacs so I really don't see any reason why you wouldn't be able to work with large projects. After all huge chunks of almost everything you see in linux were written with emacs.

The wiki says that file navig

The wiki says that file navigation has been changed and is now based on mime so that should help some.

Yeah, I saw that, but MiME doesn't mean that subdirectories are now supported, so i was wondering...

Also you would apparently be able to change the editor to say emacs so I really don't see any reason why you wouldn't be able to work with large projects.

Of course I would be able to use something other than Anjuta, but this article is about Anjuta, right? Or do you mean that an Emacs mode is being integrated? I haven't found that information. Then still, I don't see why that should mean that subdirs are supported.

Could somebody please shed some light on the issue?

-knipknap

> Could somebody please shed

> Could somebody please shed some light on the issue?

Did you try to follow the link above?

* Building of C source files with autotools: The new build plugin allows building all autotools based projects and can operate without projects being opened. That means you can simply open a file and build the directory. Or simply right click in file manager and build (without having any project at all). Multiple parallel builds are possible.

* Autotools project manager: Based on gnome-build, current project manager is powerful comprared to the earlier project manager. Project files and target are managed in the way one would expect for an automake based project. Makefiles are automatically managed by the project manager. However, not everything is working yet.

Regards,
chris

Great, so there are improveme

Great, so there are improvements in the build process. But I fail to see how that answers my question.

Project files and target are managed in the way one would expect for an automake based project.

That may mean that projects now do support directories, but it also may not.

-knipknap

Does automake support sub dir

Does automake support sub directories?

Ok, case closed

Automake support has nothing

Automake support has nothing to do with the Anjuta project manager.
It is perfectly possible to support Automake, including Automake's "subdirectory support" (if you can call it that) without having that reflected in the Project manager.
Even Anjuta 1.x does support Automake, however, it does not support subdirectories.

What I am asking is whether the project manager does support directories, that is, you open a project an have the directory tree presented in the manager.

Re: Automake support has nothing

Yes, Anjuta 2.0 will support multiple directories. It will also support multiple targets.

hmm

Link please.