[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cdt-dev] Project proposal (Google Summer of Code)
|
Hi Yuriy,
I've only been a CDT committer for about three months
now and I am not personally aware of how GSoc is being
handled
for the CDT. However, I thought I bring a couple
of points to your attention.
At the end of 2008, a new GDB integration was moved
from the DSDP/DD project to the CDT. DSF-GDB is an
integration
of GDB into the CDT which is based on DSF (Debug
Services Framework.) The original GDB integration (CDI-GDB) is
still
available in the CDT. However, the current
consensus is that we will gradually increase the use of DSF-GDB as the
main
CDT debugger, while decreasing the use
CDI-GDB.
I suggest you have a look at DSF-GDB by using the
latest CDT build and eclipse 3.5M6. With that build, when you
launch
a debug session, you will see a link at the bottom of
the page where the tabs are. This is where you select which
debugger
to use. (Note there is currently a bug that make the OK
button grey, but you can workaround by setting your
workspace
preferences.)
I went through your proposal, and as I said I'm too new
to the CDT to have a clear opinion, but the formatter stuff looks
interesting. As for the "Other usability
enhancements":
* Adding a variable/_expression_
watch directly, omitting "Edit _expression_" dialog box.
This is already part of DSF and therefore it is part of DSF-GDB (which
proves it was a good idea :-))
*
Hovering mouse over a variable will show its content similar if it was added to
expressions watch.
Where is this hovering action? Is it in the
editor? If that is what you are talking about,
many people have requested this feature for
DSF-GDB. There is a bug about it:
However, this bug mentions that CDI-GDB already does
this, so I'm guessing you are referring
to something else?
* Expressions watch will be
editable directly, without "Edit _expression_" dialog box. TODO: screenshot.
Another good idea which is part of DSF and
therefore part of DSF-GDB.
* Rearrange default
Debug perspective to reserve more space for code.
You are very
right that screen real-estate is important. A new feature part of the
Debug Platform has
been added to 3.5M5. It is caleld the
debug view breadcrumb. It allows you to make the debug view one line
high.
You can have a look at the
following for details:
I hope this helps making your proposal move
forward.
Feel free to send any questions.
Thanks for you interest in the CDT, it is great to have
people willing to help.
Marc
Hello,
Google is conducting Google Summer of Code in which
it encourages students to participate in Open Source development. Basically
students have to:
1. Choose open source organization.
2. Propose a
project for it.
3. Find a mentor which would help him to complete the
project.
4. Pass validation to get a stipend.
5. Complete project by
August 18.
I was using Eclipse CDT as my primary programming contest
environment for past four years. It's a great tool and it was pleasure to see
how it was developing through time. But there are some issues which I'd like
to help with.
Basically I'd like to make some enhancements for CDT's
debugger. I've made a project proposal (only a draft yet) at http://wiki.eclipse.org/CDT/Better_Debugging_(GSoC_project)
. Could you please review it and help me with answering following
questions:
1. Is it worth doing at all?
2. Is it possible to finish it
by August 18?
3. Who could mentor me with this project?
4. Is there
anything you would suggest me to change in that draft?
Thank you.
--
Best regards,
Yuriy Znovyak
mailto:oberon.ua@xxxxxxxxx
