[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-devel
Subject:    Re: Debbuger
From:       Aleix Pol <aleixpol () kde ! org>
Date:       2009-02-03 14:28:50
Message-ID: 757d9a550902030628j6d5798eehfbd8b5bd745d2303 () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Maybe it would be easier to check what's being done in qt creator instead of
kdev3... isn't it?

On Tue, Feb 3, 2009 at 7:36 AM, Hamish Rodda <rodda@kde.org> wrote:

> Hi,
>
> I've decided to try to make the debugger work for kdevelop 4.0, it would be
> a
> shame if we couldn't provide a working debugger as it's one of the
> strengths
> of having an IDE.
>
> In analysing what happened to the debugger after my initial port from
> kdevelop
> 3.x, it seems that the major problem was that I had ported it to a pure
> model/view implementation, however Volodya preferred it to be based on some
> base classes to decrease complexity.  This is fine, but it seems the change
> was never completed - some parts were rewritten, and some were just
> commented
> out.  This left us with a debugger unable to display variables, which is
> not
> very useful.  I feel it is too much effort for me to fix all of the
> problems
> with head, especially because I don't understand why some parts were
> seemingly
> rewritten.
>
> I've started a branch which aims to provide something that is working, and
> we
> can discuss whether we go back to HEAD if/when someone steps up to fix the
> problems with head.  I'd even be open to helping with a port away from a
> pure
> model/view implementation, as long as it is planned well and doesn't
> involve
> wholesale re-writing of code (without a good reason).
>
> The major deficiencies of this branch (if it gets to a working state) will
> probably be:
> 1) use of the old breakpoint widget
> 2) variable tooltip feature missing
> which could also be ported over, if the branch is to continue on...
>
> The branch is in playground.
>
> Cheers,
> Hamish.
>
> _______________________________________________
> KDevelop-devel mailing list
> KDevelop-devel@kdevelop.org
> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
>

[Attachment #5 (text/html)]

Maybe it would be easier to check what&#39;s being done in qt creator instead of \
kdev3... isn&#39;t it?<br><br><div class="gmail_quote">On Tue, Feb 3, 2009 at 7:36 \
AM, Hamish Rodda <span dir="ltr">&lt;<a \
href="mailto:rodda@kde.org">rodda@kde.org</a>&gt;</span> wrote:<br> <blockquote \
class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt \
0pt 0.8ex; padding-left: 1ex;">Hi,<br> <br>
I&#39;ve decided to try to make the debugger work for kdevelop 4.0, it would be a<br>
shame if we couldn&#39;t provide a working debugger as it&#39;s one of the \
strengths<br> of having an IDE.<br>
<br>
In analysing what happened to the debugger after my initial port from kdevelop<br>
3.x, it seems that the major problem was that I had ported it to a pure<br>
model/view implementation, however Volodya preferred it to be based on some<br>
base classes to decrease complexity. &nbsp;This is fine, but it seems the change<br>
was never completed - some parts were rewritten, and some were just commented<br>
out. &nbsp;This left us with a debugger unable to display variables, which is not<br>
very useful. &nbsp;I feel it is too much effort for me to fix all of the problems<br>
with head, especially because I don&#39;t understand why some parts were \
seemingly<br> rewritten.<br>
<br>
I&#39;ve started a branch which aims to provide something that is working, and we<br>
can discuss whether we go back to HEAD if/when someone steps up to fix the<br>
problems with head. &nbsp;I&#39;d even be open to helping with a port away from a \
pure<br> model/view implementation, as long as it is planned well and doesn&#39;t \
involve<br> wholesale re-writing of code (without a good reason).<br>
<br>
The major deficiencies of this branch (if it gets to a working state) will<br>
probably be:<br>
1) use of the old breakpoint widget<br>
2) variable tooltip feature missing<br>
which could also be ported over, if the branch is to continue on...<br>
<br>
The branch is in playground.<br>
<br>
Cheers,<br>
Hamish.<br>
<br>
_______________________________________________<br>
KDevelop-devel mailing list<br>
<a href="mailto:KDevelop-devel@kdevelop.org">KDevelop-devel@kdevelop.org</a><br>
<a href="https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel" \
target="_blank">https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel</a><br>
 </blockquote></div><br>



_______________________________________________
KDevelop-devel mailing list
KDevelop-devel@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic