been granted two Summer of Code projects. This is exciting
news for me, and I am grateful to all the people who helped
make this happen.
In this post I'll present the hackers who presented those
two projects and give you some perspective about their
Seemanta has been active on the mailing list of the Nemiver
project for quite some time now. He has shown great
interest in the project and has contributed ideas and code.
When you are debugging a program and you hit "Quit" in
Nemiver while the debugged program is still running, the
debugger kindly reminds you that said debugged program is
still around and alive. This has saved me from accidentally
quitting the debugger quite a number of time. Seemanta is
the person to thank (warmly) for this feature.
At some point in time some people have shown interest for
having a command line interface in Nemiver, coupled with a
way to script debugging actions. I have kind of dragged
feet in that matter because my attention is taken by
nurturing more basic features.
I was excited to see Seemanta rolling up his sleeves and
proposing to look into supporting (Python) scripting in
Nemiver. Think about it for two seconds. This could have
some interesting impacts in debugging interactions for
Nemiver users. Imagine a command line interpreter for the
graphical debugger, totally written (and extensible) in a
scripting environment. I like the fresh air that this new
horizon is bringing.
- Fabien Parent
Fabien has been active in the Nemiver project for a while
now. He has been instrumental in testing and providing
astute feedback for features like remote debugging and, more
recently, the integrated disassembler of the debugger. It
took me quite some energy to add that disassembling feature
so I did really appreciate the feedback of Fabien -- and
others (hey Luca Bruno!) -- about corner cases that I left
over here and there. Without them the damn thing would
certainly be less streamlined than it is now.
More recently he added support for GSettings to the code
base, effectively taking his share of the effort of porting
Nemiver to the GNOME 3 platform. Not only did he do that,
but he did it in a clever and maintainable way. The code
base basically supports GConf *and* GSettings. Both of
which are "just" backends of the internal configuration
interface of the Nemiver project. And there is zero #ifdef
in the client code of said configuration interface, for
those who care. This allows me (as a maintainer) to
contemplate -- with some serenity -- the support of Nemiver
on systems that will not necessarily jump to GSettings soon.
Looking at the Bugzilla activity around Nemiver, one could
sense that the way it uses the screen estate is not
necessarily optimal today, especially when you consider the
use cases of "wide" monitors that is getting more and more
the norm rather than the exception. In other words, there
are people out there who would like to make a better use of
their horizontal screen space, during their debugging
I was thrilled when Fabien stood up to tackle this task of
providing Nemiver users with a better way of managing their
horizontal space during their graphical debugging sessions.
Please join me in congratulating Seemanta and Fabien!
Happy Summer Hacking!