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

List:       kde-commits
Subject:    Re: KDE/kdevelop/lib
From:       Andreas Pakulat <apaku () gmx ! de>
Date:       2007-05-26 20:29:44
Message-ID: 20070526202944.GA24380 () morpheus ! apaku ! dnsalias ! org
[Download RAW message or body]

On 26.05.07 16:57:12, Thiago Macieira wrote:
> Andreas Pakulat wrote:
> >Thats not possible at the moment either because it breaks using
> >KDevelop3 for KDevelop4. I'm not sure what to do once K3Process
> >subclasses from QProcess, either we will maintain a copy of the old
> >K3Process in KDevelop4 until its usable for everyday development or ????
> >(Yes I know thats not nice, but I need to be able to run and debug my
> >kde4 apps inside kdev3 and there's no way to make KProcess/KDE3 work
> >with QProcess/qt3 or qt4 in the same application).
> 
> The reason K3Process is switching to QProcess is that you're *required* to 
> use the same QProcess implementation.
> 
> If you keep using the old one or if you keep the old implementation, 
> you'll have problems. You'll have to make sure that *nothing* else in 
> KDevelop -- including the KDE libraries, plugins, loaded modules, etc. -- 
> uses QProcess.

I know all that and as I said this would be a temporary solution until
KDevelop4 is in a state where its usable at least for debugging.
Unfortunately currently it doesn't look too bright on that front because
our debugger-guru doesn't have time. I'm certainly not suggesting to
ship a beta of KDevelop4 with a custom *Process class, but its important
(at least for me) to be able to debug KDevelop4 inside KDevelop3 and
that is unfortunately only possible by using the current implementation
of K3Process in Kdevelop4. Sorry but I will not switch to plain
commandline gdb.

If that means I have to keep this *Process class and apropriate patch on
my own local disk thats fine with me.

Andreas

-- 
It may or may not be worthwhile, but it still has to be done.
[prev in list] [next in list] [prev in thread] [next in thread]