KDev4 Debugger Status

Hi,

The initial port of the debugger is done, at least it
compiles and loads ok.  
There's much breakage, and people are encouraged to dive in
and help - i've 
even turned on the qt3 support warnings, so those are good
places to start.

(it can't be used at the moment, btw, before you try to use
it)

Also, I'm currently stuck on why the gui won't merge... any
ideas?

Cheers,
Hamish.

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On 26.11.07 22:55:40, Hamish Rodda wrote:
> Hi,
> 
> The initial port of the debugger is done, at least it
compiles and loads ok.  
> There's much breakage, and people are encouraged to
dive in and help - i've 
> even turned on the qt3 support warnings, so those are
good places to start.
> 
> (it can't be used at the moment, btw, before you try to
use it)
> 
> Also, I'm currently stuck on why the gui won't merge...
any ideas?

Currently I know this much: The gdb plugin isn't known to be
an xml gui
client of kdevelop. I'm not sure why it is that way though,
especially
as its not clear yet how the clients get hooked into the
parent :(

Andreas

-- 
Your goose is cooked.
(Your current chick is burned up too!)

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On 26.11.07 20:40:13, Andreas Pakulat wrote:
> On 26.11.07 22:55:40, Hamish Rodda wrote:
> > Hi,
> > 
> > The initial port of the debugger is done, at least
it compiles and loads ok.  
> > There's much breakage, and people are encouraged
to dive in and help - i've 
> > even turned on the qt3 support warnings, so those
are good places to start.
> > 
> > (it can't be used at the moment, btw, before you
try to use it)
> > 
> > Also, I'm currently stuck on why the gui won't
merge... any ideas?
> 
> Currently I know this much: The gdb plugin isn't known
to be an xml gui
> client of kdevelop. I'm not sure why it is that way
though, especially
> as its not clear yet how the clients get hooked into
the parent :(

ROFLMAO. Guess what, you created that problem in the first
place 


The problem is that the order of events in
Mainwindow::initialize is
wrong. It first creates the status bar, which results in
asking the
plugin controller for a plugin for IStatus, this in turn
loads the
debugger plugin. And after that the mainwindow hooks itself
up to the
plugincontroller signals, like pluginLoaded to call
xmlgui->addClient()
when a plugin is loaded to merge its gui.

God, I can't believe it took me 2 hours to find this out.
Though it
actually took me 1,8 hours to find out where
XmlGuiFactory::addClient is
called in the first place :(

Solution was easy: Move the statusbar creation to the end
of
MainWindow::initialize(). I also added a couple of kdebug
calls, which
should help to spot such problems sooner in the future (i.e.
problems in
the order of initialization of things)

Andreas

-- 
Is this really happening?

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On Tue, 27 Nov 2007 08:07:15 am Andreas Pakulat wrote:
> On 26.11.07 20:40:13, Andreas Pakulat wrote:
> > On 26.11.07 22:55:40, Hamish Rodda wrote:
> > > Hi,
> > >
> > > The initial port of the debugger is done, at
least it compiles and
> > > loads ok. There's much breakage, and people
are encouraged to dive in
> > > and help - i've even turned on the qt3
support warnings, so those are
> > > good places to start.
> > >
> > > (it can't be used at the moment, btw, before
you try to use it)
> > >
> > > Also, I'm currently stuck on why the gui
won't merge... any ideas?
> >
> > Currently I know this much: The gdb plugin isn't
known to be an xml gui
> > client of kdevelop. I'm not sure why it is that
way though, especially
> > as its not clear yet how the clients get hooked
into the parent :(
>
> ROFLMAO. Guess what, you created that problem in the
first place 

Oops, just goes to show how hard creating the proper init
sequence can be I 
guess.

> The problem is that the order of events in
Mainwindow::initialize is
> wrong. It first creates the status bar, which results
in asking the
> plugin controller for a plugin for IStatus, this in
turn loads the
> debugger plugin. And after that the mainwindow hooks
itself up to the
> plugincontroller signals, like pluginLoaded to call
xmlgui->addClient()
> when a plugin is loaded to merge its gui.
>
> God, I can't believe it took me 2 hours to find this
out. Though it
> actually took me 1,8 hours to find out where
XmlGuiFactory::addClient is
> called in the first place :(
>
> Solution was easy: Move the statusbar creation to the
end of
> MainWindow::initialize(). I also added a couple of
kdebug calls, which
> should help to spot such problems sooner in the future
(i.e. problems in
> the order of initialization of things)

Thanks for the fix 

Cheers,
Hamish.

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On Tuesday 27 November 2007 04:41:11 Andreas Pakulat wrote:
> On 26.11.07 22:55:40, Hamish Rodda wrote:
> > Hi,
> > 
> > The initial port of the debugger is done, at least
it compiles and loads ok.  
> > There's much breakage, and people are encouraged
to dive in and help - i've 
> > even turned on the qt3 support warnings, so those
are good places to start.
> 
> I've started to do a few things (and plan to do more
tomorrow). I guess
> due to the different timezones we won't step on each
others toes when
> doing this (as you seem to be getting to bed when I get
up and
> vice-versa).
> 
> Andreas, who can't wait to rip out the breakpoint
table, 

Why? It seems like there's some use of it.

- Volodya

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On 11/27/07, Vladimir Prus <ghostcs.msu.su> wrote:
> On Tuesday 27 November 2007 04:41:11 Andreas Pakulat
wrote:
> > Andreas, who can't wait to rip out the breakpoint
table,
>
> Why? It seems like there's some use of it.
>
At least Qt3 QTable had that bad focus bug where it randomly
stole
focus when its fields were updated. This turned up in KDev3
as the
editor losing focus when the user hit 'enter'. A really bad
bug. Dunno
if this is still a problem in Qt4 though..

// jens

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On 27.11.07 08:57:06, Vladimir Prus wrote:
> On Tuesday 27 November 2007 04:41:11 Andreas Pakulat
wrote:
> > On 26.11.07 22:55:40, Hamish Rodda wrote:
> > > Hi,
> > > 
> > > The initial port of the debugger is done, at
least it compiles and loads ok.  
> > > There's much breakage, and people are
encouraged to dive in and help - i've 
> > > even turned on the qt3 support warnings, so
those are good places to start.
> > 
> > I've started to do a few things (and plan to do
more tomorrow). I guess
> > due to the different timezones we won't step on
each others toes when
> > doing this (as you seem to be getting to bed when
I get up and
> > vice-versa).
> > 
> > Andreas, who can't wait to rip out the breakpoint
table, 
> 
> Why? It seems like there's some use of it.

I knew I should've elaborated just before sleeping in  I'm not
going
to remove the widget as whole, just rip out the QTable
implementation
and replace it with some MVC stuff. I don't know wether its
fixed in
Qt4, but in Qt3 that QTable had a nasty focus-bug.

Andreas

-- 
You will experience a strong urge to do good; but it will
pass.

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel