Gideon under KDE2

[Richard Dale]

On Tuesday 13 November 2001 9:08 am, you wrote:
> On Mon, Nov 12, 2001 at 10:03:03PM +0100, F at lk Brettschneider wrote:
> > Hi,
> >
> > Roland Krause wrote:
> > > I'd suggest to try and keep it KDE-2 compatible as long as possible. At
> > > least until the first beta release of KDE-3. Actually we will not
> > > release anything with KDE-3, or?
> >
> > Until there's nothing comparable we'll release KDevelop-2.0.x with KDE-3
> > because it's already now ready to use, stable and the same full-featured
> > as with KDE-2.
>
> I see a pattern here ;-)

As far as I can see the main issue Roland and Falk have with switching from 
KDevelop 2.0.x to Gideon for KDE 3, is that Gideon doesn't support the 
qextmdi UI style at the top level. Is it just a matter of changing the code 
below from src/core.cpp?

Change core.cpp:

    manager = new KParts::PartManager(win);
    connect( manager, SIGNAL(activePartChanged(KParts::Part*)),
             this, SLOT(activePartChanged(KParts::Part*)) );
    connect( manager, SIGNAL(partAdded(KParts::Part*)),
             this, SLOT(partCountChanged())),
    connect( manager, SIGNAL(partRemoved(KParts::Part*)),
             this, SLOT(partCountChanged()));

To:

    if (qextmdiOption) {
      manager = new QExtMDIPartManager(win);
    } else {
      manager = new KParts::PartManager(win);
    }
...

What are the technical issues involved in implementing this? I see no need to 
change the Core api or the KParts plugins that already exist in Gideon - they 
all look pretty tidy to me. The only thing needed is a QExtMDI part manager, 
which will manage KParts in the MDI UI style.

KDevelop 2.0.x is fine, but it doesn't support Objective-C and Java 
programming - I can do patches and go back to working on the KDevelop 1.x/2.x 
series. But I'd rather get Roland and Falk on board, and move forward to 
KParts component/multi language development with Gideon ASAP. It is 
important to me that we try to release Gideon in some form for KDE 3, even if 
we release KDevelop 2.0.x as 'KDevelop Classic' as well.

-- Richard

-
to unsubscribe from this list send an email to kdevelop-devel-request at kdevelop.org with the following body:
unsubscribe »your-email-address«