Qt-Only Version?

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent

Qt-Only Version?
by Rahim on Monday 08/Jan/2007, @19:04

Hi,

Glad to see that OOo might be getting some tougher competition! Does anyone know if it is possible or if it will be possible to create a Qt-only version of Koffice, which does not require all the KDE deps? I ask this because a low-resource office suite is desperately needed in the Linux world, and I imagine that most users who are using an old computer aren't going to be running KDE.

Thanks!

Related Links

·   Articles on KDE Public Relations and Marketing
·   Also by Rahim
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )

Re: Qt-Only Version?
by redeeman on Monday 08/Jan/2007, @19:08

a few kde libraries wont really do much damage, a full loaded kde desktop isnt required.

[ Reply To This | View ]

Re: Qt-Only Version?
by Rahim on Monday 08/Jan/2007, @19:25

So, on Debian, it would require kdelibs or something like that? It's just I remember when I used to use XFCE on an old computer, if I opened even something little like Kcalc, it took ages to load. But I suppose with DCOP being gone, that will help the initial overhead quite a bit?

[ Reply To This | View ]

Re: Qt-Only Version?
by Aaron J. Seigo on Monday 08/Jan/2007, @19:51

it's not dcop, it's loading all the libs and starting necessary support daemons such as kded and what not.

you're probably not saving as much with xfce as you think if you're running kde apps in it.

[ Reply To This | View ]

Re: Qt-Only Version?
by Rahim on Monday 08/Jan/2007, @19:59

Yes, I agree. I guess that's sort of my point, is there any way to make Koffice compile as Qt-only or something?

[ Reply To This | View ]

Re: Qt-Only Version?
by Robert Knight on Monday 08/Jan/2007, @21:10

No, but you could try AbiWord perhaps?

[ Reply To This | View ]

Re: Qt-Only Version?
by Troy Unrau on Monday 08/Jan/2007, @21:12

The simple answer is no.

The long answer is due to all the functionality that KOffice pulls in from kdelibs so it doesn't have to do all that work itself. Like the file dialogs, config dialogs, toolbars, printing, auto-saving, config backend, kparts, and so forth... removing the kdelibs dependency would cause KOffice to re-implement this all in-house, so you really wouldn't be saving anything.

[ Reply To This | View ]

Re: Qt-Only Version?
by Aaron Seigo on Tuesday 09/Jan/2007, @15:46

indeed; you'd get open office all over again at the cost of a gargantuan development effort.

[ Reply To This | View ]

Re: Qt-Only Version?
by superstoned on Wednesday 10/Jan/2007, @08:10

and - Koffice with the KDElibs is still smaller than OO.o itself...

[ Reply To This | View ]

Re: Qt-Only Version?
by otherAC on Monday 08/Jan/2007, @23:37

You could load kdelibs with xfce, so that you won't have the startup delay when launching a kde application.

[ Reply To This | View ]

Re: Qt-Only Version?
by Diederik van der Boor on Tuesday 09/Jan/2007, @01:09

XFCE uses less memory when you start a clean session. With more apps open, XFCE can use more memory because every application (AbiWord, OpenOffice, Firefix) has it's own set of libraries. At some point KDE wins here. See the following: http://ktown.kde.org/~seli/memory/desktop_benchmark.html

For starting KDE applications outside KDE, also try:
http://wiki.kde.org/tiki-index.php?page=Performance%20Tips#_Faster_startup_of_KDE_applications_outside_of_KDE
http://wiki.kde.org/tiki-index.php?page=Performance%20Tips#_Directory_prescanning_in_KDM

[ Reply To This | View ]

Re: Qt-Only Version?
by Thomas Zander on Tuesday 09/Jan/2007, @02:54

Not depending on the kdelibs would not actually mean less code (in total) or a lower functionality requirement.
So its like saying you want to eat a full meal, but don't want to gain any weight. So lets only eat crackers!.
Well, in both cases all you are doing is move the requirement to another place and you'll just be adding lots of code in KOffice itself. Just like you'll eat a whole lot of crackers to be able to sustenance you.

As another poster in this thread said; sharing the libraries with many other applications will in the end save you space since not every application will load a _different_ set of libraries even though they all need a large total amount of libraries.
So you can see it like you are carpooling libraries. You save in fuel money by sharing the car with your neighbor. That doesn't change the fact that you both need to travel a long distance, it just means it has less of an impact.

Carpooling is the real solution; buying a smaller car of your own doesn't actually help much.

Hope that explains this rather complex mental model a bit better :)

[ Reply To This | View ]

The Fine Print: The previous comments are owned by whomever posted them.
( Reply )


		"He may be a Hotmail user, but the patch works, so who am I to argue?" -- Charles Samuels
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.