KDevelop presented at CeBit exhibition in Hannover, Germany

Benoit Cerrina Benoit.cerrina at writeme.com
Mon Feb 28 21:13:01 UTC 2000

----- Original Message -----
From: jbb <jbb at ihug.co.nz>
To: <kdevelop-devel at barney.cs.uni-potsdam.de>
Sent: Monday, February 28, 2000 7:52 AM
Subject: Re: KDevelop presented at CeBit exhibition in Hannover, Germany

> On Mon, 28 Feb 2000, Walter Tasin wrote:
> > Ralf Nolden wrote:
> (...)
> > > BTW: Talking with the other developers about our roadmap, I came to
> a roadmap for kdevelop2? - is this written down somewhere?
> > > conclusion that we might take some time longer than the KDE 2 release
> > > finish KDevelop 2. I would be willing to port the KDevelop 1.1 version
> > > to KDE2 (ONLY porting) which could be done quickly and we could
> > > a running version for KDE 2 within a few weeks. Ohter KDE developers
> > > KDE2 are already switching to use KDEStudio....;-(   We could leave
> > > tag as it is, just start porting from tomorrow on.
> >
> > When will KDE 2 be released... or at least a stable (non switching in
> > principles) kde2libs?
> > Do you know this?
> > It would be useful to know this... because if you are porting 1.1 to
> > kdelibs 2 and KDE is switching again in some principles you would have a
> > new branch, which needs to be supported.
> > (See the KAction and K(Dev)Accel problem in KDevelop 2)
> Hmm
> Which will be harder
> porting the new bits of kdevelop1.1 into kdevelop2.0
> or
> porting 1.1 then adding the new pieces from the current kdevelop2.0
> There was a lot of work from the kdevelop 2 branch point (which was quite
> some time prior to 1.0 IIRC) to the 1.1 version, so finding and changing
> not obsoleted by new code) is going to be difficult.
> I think the amount of work will be a bit of a toss of the coin as to which
> easier, but if a 1.1 port is done then you'll have a better platform to
> continue developing kdevelop2.
> With either of the two approches, kde2 changing will probably be about an
> pain.
> --
> Regards,
> jbb
> http://homepages.ihug.co.nz/~jbb
> ICQ: 60412209

If you think that what will happen is an evolution from kdev 1.1 to kdev2.0
rather than the abrupt jump which was first envisaged, one of the first
thing which should be taken care of is the project management and the
If you remembered, at one time I offered to work on the performance issue as
far as switching from document to document is concerned.  The way it is done
is both slow and error prone.

More information about the KDevelop-devel mailing list