Re: Need input from the community for anjuta (was Re: Proposed module: anjuta)

["Mikkel Kamstrup Erlandsen" <mikkel kamstrup gmail com>]

On 06/01/2008, Vincent Untz <vuntz gnome org> wrote:
> Hi,
>
> Le jeudi 20 décembre 2007, à 04:52 +0100, Vincent Untz a écrit :
> > Homepage: http://anjuta.sourceforge.net/
> > svn/git/bzr/...: http://svn.gnome.org/svn/anjuta/trunk/
> >                  http://svn.gnome.org/svn/gdl/trunk/
> >                  http://svn.gnome.org/svn/gnome-build/trunk/
> > Proposal on d-d-l: http://mail.gnome.org/archives/desktop-devel-list/2007-September/msg00252.html
> >
> > Short description:
> > ==================
> > Anjuta is an integrated development environment for GNOME. It's purpose
> > is to make developing applications for Gtk+/GNOME easier. It integrates
> > other GNOME technologies such as devhelp, glade and gtksourceview.
> >
> > Summary so far:
> > ===============
> >  + nothing :-)
> >  + FWIW, anjuta was proposed for 2.18, but there were no 2.x release at
> >    this point and the 1.2.x versions were unmaintained.
> >  + Comments from the thread on the old proposal:
> >    - anjuta 2.x is way better than the old 1.2.x one
> >    - there used to be no real release cycle for anjuta. It's my
> >      understanding that things are better in this area, but I didn't
> >      check.
>
> Based on this thread, the release team could not decide what to do with
> anjuta: we need input from the community.
>
> Here's what we got so far:
>
>  + anjuta (devtools)
>   - no real comments from the community
>   - we want an IDE in the devtools suite
>   - good documentation
>   - really hard to translate, and many strings could be improved
>   - proposal to create an incubation suite and to put anjuta there until
>     there's a clear consensus on the fact that it's ready. Some people
>     don't like the idea.
>   => will get back to d-d-l to get more input from the community
>
> One problem is that the release team members either have no use for an
> IDE (they don't code) or are old and {vim,emacs,whatever}-addicted, so
> it's hard for us to know.
>
> If you use anjuta, speak up. If you have tried anjuta, speak up. If the
> name anjuta makes you feel something, speak up. If you want to be the
> next big movie star, speak up. Now.
>

I use Anjuta as my primary code editor and I like it very much.

On top of other integration stuff that has been mentioned elsewhere in
this thread, high profile features are also:

 * Auto-foo integration. You can set up a fully autotooled project
with a few clicks. You can even import an already autotooled project!
It is a good way to start if you are not really comfortable with
autotools.

 * Integrated debugger. I can use gdb for some basic stuff, but I am
far from adept in CLI/gdb debugging. With Anjuta's integrated debugger
I can inspect variables, manage breakpoints, browse the stack and what
not. This is really helpful.
 The debugger is also great for stepping through running code. It can
even jump out to external code with hearders installed under /opt but
with the code in my home dir (glib trunk in my case). I don't know how
this works, but it just does :-)

Being polished from top to bottom should not be a criterion for
inclusion. Anjuta is good enough and feels quite professional to me.
Putting it in an official release is pretty sure to give it the last
push it needs for the final touches.

+1 from me.

Cheers,
Mikkel