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

List:       kde-devel
Subject:    Re: Drag and Drop and KDE 2
From:       David Faure <faure () alpha ! tat ! physik ! uni-tuebingen ! de>
Date:       1999-05-05 6:39:52
[Download RAW message or body]

On Wed, May 05, 1999 at 01:22:00AM +0200, David Faure wrote:
> On Tue, May 04, 1999 at 05:17:31PM -0600, Christopher Wiegand wrote:
> > >Alex Zepeda <garbanzo@hooked.net> wrote:
> > >
> > This brought to my mind some concerns. Many, many, things are changing (for
> > the better) in KDE 2.0/1.89/etc.. Has anyone started a list of things
> > PROGRAMMERS need to change in their docs? Something like:
> > 
> > KToolBar::foo removed. Use KToolBar::bar instead.
> > KToolBar::bar(int, int, char) changed to KToolBar::bar(int,int,int,char).
> > KToolBar::foobar is no longer child of ::foo, now child of ::bar.
> > KToolBar superceded by KFooBar. All members the same.
> > KFooBar contains all code for everything. Always link -lkfoobar.
> > 
> > Just an idea. I don't use CVS, can't get the thing to work, and I'm not sure I
> > want to use CVS. I'm sure there are other programmers out there who also have
> > KDE programs that aren't in CVS. This kind of document could make things
> > easier on us when KDE 2 is near release. (We can start to prep our code for
> > it.)
> 
> This IS needed, for sure.
> But the problem is that even TT didn't do it, yet, for Qt.
Oops, just found doc/portings.doc in qt...

> And most of the porting problems come from the changes in Qt's API.
> Ok, there are also some changes in kdelibs (especially kdecore).
> And the person doing the change should document it publically, but for that 
> we need to start a document first.

Let's start a KDE document for this, possibly keeping TT's document layout.
Anybody has one minute to do it ?

-- 
David FAURE
david.faure@insa-lyon.fr, faure@kde.org
http://www.insa-lyon.fr/People/AEDI/dfaure/index.html 
KDE, Making The Future of Computing Available Today

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