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

List:       kde-devel
Subject:    Re: Writing from 2.0 -> 1.1.2
From:       Mosfet <mosfet () mandrakesoft ! com>
Date:       2000-01-11 23:38:53
[Download RAW message or body]

It's really not going to be all that easy to actively maintain two
versions. While the new Qt/KDE API is easy to learn, there are a lot of
minor things like you can't cast (const char *) from QString, stuff has
been moved out of KApplication and into places like KGlobal, some things
are in new namespaces like KPixmap stuff, new HTML widget, etc... All
things that needed to happen, but makes maintaining two code bases a
pain. I would suggest just coding for KDE2. Users will upgrade as soon
as there is a relatively stable version, they are already trying the
alphas ;-) All KDE developers I know are on KDE2, so we can test and by
the time KDE2 is stable and ready to release you will be as well :)

Another option you have is doing both a KDE2 and Qt2.x only version if
that is possible with your app. While KDE2 is still in the devel stage
most new dists come with Qt2 or it's not unreasonable to ask users to
install it. If I had to choose between maintaining a Qt2 only or KDE1.x
app along with a KDE2 version I would choose Qt2.

Ian Zepp wrote:
> 
> Hi.
> 
> I have been working at porting a few of my apps to the kde 2.0 libs in the
> last week or so, and an issue came up that I didn't know how to handle.
> 
> I've read through most of the headers for kde 2 and it seems to me that
> the API is a lot cleaner and consistant than it was for 1.1.x, so it
> naturally follows that I would rather write for kde 2. I'm aware that
> there is a KDE2PORTING document, but is there some sort of guidance for
> writing an app to use both kde 1 and 2?
> 
> I guess my question is: for new applications, should I use the kde 1 libs
> as a base and port forwards, or should I start with kde 2 libs and try to
> work backwards? It is only reasonable to expect most people NOT to upgrade
> KDE soon after 2 comes out, so we (as a devel community) will have to
> support both kde 1 and 2. Which way should I (we) work?
> 
> >From kde 1, porting to 2?
> Or from 2, backporting what's needed?
> 
> On a related note, are their any guidelines for this, or should we just be
> dyslexic and read KDE2PORTING backwards?
> 
> Regards
> 
> Ian
> 
> --
> Ian Zepp - KDE devel
> email: icszepp@islc.net
> web:   http://www.islc.net/~icszepp

-- 
Daniel M. Duley - Unix developer & sys admin.
mosfet@mandrakesoft.com
mosfet@kde.org
mosfet@jorsm.com

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