[patch] QHttp and QFtp forbidden in KDE

Kevin Krammer kevin.krammer at gmx.at
Sat Aug 30 13:16:30 BST 2008

On Friday 29 August 2008, Thiago Macieira wrote:
> On Sexta 29 Agosto 2008 14:05:19 Dirk Mueller wrote:
> > On Friday 29 August 2008, Thiago Macieira wrote:
> > > Those two classes are not allowed in KDE code. They won't follow the
> > > KDE settings, so using KIO is mandatory.
> > >
> > > The attached patch will accomplish this by causing any code using them
> > > to fail to compile.
> >
> > And thereby screwing all 3rd party users that still try to keep up with
> > KDE and use it?
> >
> > I don't think that enforcing a policy by technical tools is the right way
> > to go. I'd be fine in adding those #define's to kdebase/*, but not to
> > kdelibs so that anyone trying to compile his 3rd party app against
> > kdelibs has to suffer.
> To tell you the truth, I don't want anyone (3rd parties included) using
> QHttp.

So you are going to add a deprecation warning and respective changes to the 
API docs in Qt 4.5?

Can't you wait with the KDE side of things until we require that version and 
can point 3rd party developers to the revised API docs?


Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20080830/c5621d82/attachment.sig>

More information about the kde-core-devel mailing list