I think it would be excellent if we could spend more time on in the
summit on debugging and as long as there's a receptive audience we
could talk about DSF architecture and the MI implementation pretty much
indefinitely :-).
However, what Dominique is asking for is not so much a
presentation/discussion session, but rather a coding camp in model of
what we had in California in May. There we spent the first day in
white board discussions about architecture and after that we spent
three days split into groups to work on specific coding exercises
stopping along the way to answer questions. We obviously won't have
time for such an exercise during the CDT summit, but since we are all
going to be at the same location we're trying to take advantage of that
to accelerate some of the DSF/MI development.
Perhaps the best thing to do would be to use the time at the conference
to cover these topics in order and as time allows:
- Demo DSF/MI implementation
- Discuss integration between DSF and CDI and the UI presentation
- Any general Debugging UI workflow improvments, which could span
Platform, CDT, and TM
- DSF architecture using code walk-throughs and Q&A
Then on Friday after the conference we could have an additional day of
mini-coding camp to talk about specific problems in the DSF/MI
reference implementation. We could host this last day at the Wind
River Ottawa office and have it open to anyone interested.
Cheers,
Pawel
Doug Schaefer wrote:
I think
we’ve done enough work on
build and core in CDT 4.0 to last a lifetime. I don’t anticipate
needing
much discussion on that at this year’s summit, certainly not ¾ of it.
The time has
come to spend a lot more time
on debug and make sure we address the deficiencies we have with the
user
experience and to have a road map for new debugger integrations that
come along.
In other words, we need to find a way out of this DSF versus CDI thing
for the
good of the community. But, before this can happen, people need to
understand
DSF, which with its high level of abstraction and use of generics has
made that
no easy task. So spending a whole day on it at the CDT summit,
hopefully
walking through the GDB/MI integration and dealing with other debug
issues is
not out of the question, and I actually believe it needs to happen.
These
emails need to
be sent to the dd-dev list so that others who want to attend can
comment.
I
agree with Pawel
that we use try to do this in conjunction with the CDT summit. Whether
it’s
a parallel session or part of the CDT meeting depends on the topics to
be
covered, IMO.
Dominique
–
can you propose a list of items that you’d like to see covered?
From:
Piech, Pawel
Sent: Tuesday, August
07, 2007
5:49 PM
To: Dominique Toupin
(QA/EMC)
Cc: Gaff, Doug; Veenu
Verma
(AS/EAB); Francois Chouinard (QA/EMC); Marc Khouzam (QA/EMC)
Subject: Re: CDT
Summit?
Hi Dominique,
Since Francois and Mark are already at location I think it definitely
makes
sense for us to have a workshop on DSF/GDB specifially. But do you
think
we need an extra day, or would it be enough to set up a parallel
session during
the CDT summit. Last year about 3/4 of the summit was on non debugger
issues, so I could easily see us having a parallel session. I'm only
worried that some people (especially Doug S.) will say that they want
to be
included in any and all debugger discussions, so they may take
exception to
being left out. Still, if you think a parallel session would be OK, we
could propose to Doug S. and see what he thinks.
Cheers,
-Pawel
Dominique Toupin (QA/EMC) wrote:
Hi Pawel,
At the CDT Summit Sept
25-27 the second bullet on the agenda
is the incorporation of DSF in CDT: http://wiki.eclipse.org/CDT/summitfall2007
I guess you
will be attending?
Could we
have a small face to face workshop for DSF/GDB implementation?
Dominique
Toupin M.A.Sc., Eng.
Software
Quality Assurance Manager
Group
Function Technology
R&D
PM&T, Software Design & Implementation
Ericsson
America
Tel: +1 514 345 6123, ECN: 810 56123
America
Mobile: +1 514 240 3464
Europe Tel:
+46 8
757 0388, ECN:
850
70388
Europe
Mobile:
+46
7
610 11388
MailTo:dominique.toupin@xxxxxxxxxxxx
|