DevHeads.net

getting rid of qt3support in kde-workspace

hi :)

i just finished pushing a set of changes to the (ironically named?) qt3support
branch in kde-workspace which leaves no traces of qt3support or kde3support
left in that module. huzzah!

i'm ok with holding on to the branch until 4.8, but if there is interest in
getting this into 4.7 it should be a fairly safe merge and would allow
distributors to ship kde-workspace without a dependency on qt3/kde3support.

my concern is that we have beta1 out now and it might be too late in the
release cycle for this.

i'm fine either way, though i wouldn't mind seeing it in 4.7, and look forward
to your suggestions ...

Comments

Re: getting rid of qt3support in kde-workspace

By Alex Richardson at 05/25/2011 - 15:36

Am Mittwoch, 25. Mai 2011, 17:48:42 schrieb Aaron J. Seigo:
I have a mostly finished port of kmenuedit on my machine. It uses a model/view
based interface instead of the QTreeWidget.

I could push it to a repo so that you can test how well it works.

Alex

Re: getting rid of qt3support in kde-workspace

By Aaron J. Seigo at 05/25/2011 - 17:46

On Wednesday, May 25, 2011 22:36:58 Alex Richardson wrote:
that would be better than a simple port of the existing code. i'd be
interested in it when it's all the way fnished :)

this is one of my biggest fears with git: people work in little "caves" on
their own machines and the code they write doesn't get published somewhere
others can access it. yes, please, do share sooner rather than later.

worst case scenario is that you don't finish, but then someone else might be
able to if it is published somewhere :)

Re: getting rid of qt3support in kde-workspace

By Alexander Neundorf at 05/25/2011 - 14:26

On Wednesday 25 May 2011, Aaron J. Seigo wrote:
Cool :-)

I'd stay on the safe side and keep it for 4.8...

Alex

Re: getting rid of qt3support in kde-workspace

By Albert Astals Cid at 05/25/2011 - 13:27

A Wednesday, May 25, 2011, Aaron J. Seigo va escriure:
Is there a real demand for this? i.e. which distributions out there does not
ship with kde3support and needs kde-workspace?

Albert

Re: getting rid of qt3support in kde-workspace

By Boudewijn Rempt at 05/25/2011 - 13:32

Yes, I'd say there's a real demand. qt3/kde3 support takes space and
qt3-support doesn't exist on OSX anymore, and is going to disappear
everywhere else. After Qt 4.8, no Qt3 support anymore. Best get it removed
everywhere as soon as possible. (As well as QWidget/QPainter code, too,
of course.)

Boudewijn

Re: getting rid of qt3support in kde-workspace

By Albert Astals Cid at 05/25/2011 - 13:46

A Wednesday, May 25, 2011, Boudewijn Rempt va escriure:
That's just facts, not saying who is demanding KDE 4.7 to have no qt3support.

Yes, but KDE 4.8 will come before Qt 5 does so that's a non issue too.

Disagree, removing it for the sake of removing it, is just opening the can to
bugs for no real reason.

Hope you are really joking with this one.

Albert

Re: getting rid of qt3support in kde-workspace

By Boudewijn Rempt at 05/25/2011 - 14:27

On Wednesday 25 May 2011 May, Albert Astals Cid wrote:
Yes, it's a fact that on OS X there's no qt3support.

No, it is not a non-issue. It took many years to port from Qt3 to Qt4. It took me about a year to get rid of most qt3/kde3-support use in calligra. It's much better to start now and make code that uses kdelibs, like kde workspace, qt3/kde3-support free.

Well, and I obviously disagree with that. Get your stuff cleaned up as soon as possible makes a lot of sense to me.

No, I'm not joking. If QWidget/QPainter are declared "done" now, then with Qt6, they will be gone, just like qt3support will be gone in Qt5. And that will be in a relatively short period of time: five years or so. Which might sound like a long time, but isn't when porting complex, real world applications.

Re: getting rid of qt3support in kde-workspace

By Leo Savernik at 05/26/2011 - 10:57

Am Mittwoch, 25. Mai 2011 schrieb Boudewijn Rempt:
Well this really sounds like a bad joke. I took from Qt5's message QPainter is
"done", i. e. frozen for good.

Now you're saying that QPainter will be marked deprecated in Qt5 and dropped
in Qt6?

That'd be similar to POSIX proclaiming to deprecate "open()" and drop it next
year.

Can any Trolltech official confirm that QPainter is going to stay just like
open() in POSIX, stable, non-morphing, and reliable? Or confirm the opposite?

mfg
Leo

Re: getting rid of qt3support in kde-workspace

By Thiago Macieira at 05/26/2011 - 02:40

On Thursday, 26 de May de 2011 17:57:30 Leo Savernik wrote:
There are no Qt 6 plans. Anything you may say about that is pure speculation.

I can't say anything about Qt 6, 7, 8 or 9. I can say that QPainter will be
there in Qt 5.

Re: getting rid of qt3support in kde-workspace

By =?ISO-8859-1?Q?... at 05/26/2011 - 11:31

On Thu, May 26, 2011 at 12:57 PM, Leo Savernik <l. ... at aon dot at> wrote:
Yep it seems so.

Dropped doesn't mean you won't get any replacement. You can get
something better.

POSIX is a bad example. It's not a "product" per say.

There will still be a need for a simple drawing API so yes there will
be something.

Re: getting rid of qt3support in kde-workspace

By Alexander Neundorf at 05/25/2011 - 14:50

On Wednesday 25 May 2011, Boudewijn Rempt wrote:
I don't think so.
The switch from Qt3 to Qt4 was big, i.e. really big. I mean "big".
But IMO it would be nothing compared a switch from Qt with QWidget to Qt
without QWidget.
So I think QWidgets are here to stay.
Especially with the "Open Governance" I think about every current Qt user will
want to keep them, not only us, but also all commercial Qt users.

Alex

Re: getting rid of qt3support in kde-workspace

By Albert Astals Cid at 05/25/2011 - 14:40

A Wednesday, May 25, 2011, Boudewijn Rempt va escriure:
We totally agree, it should have been done 3 years ago. What i'm just saying
is that without a good reason i don't see why we need to do it in the middle
of a release.

Albert