SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I think you guys are way too quick to bash Koffice. I've never used Libreoffice, but I HATE OO.o. It's ridiculously slow and trying to mimic the completely idiotic MS Office interface doesn't do it any favors, either. Koffice 1.6 was a very good office package; I used it almost exclusively up until recently. Koffice 2.x is obviously not ready for prime-time (although certain apps such as Kexi are there), but it's got a very smart UI layout and a lot of potential. The only thing slowing it down is a very small dev team.
Ugh. Perhaps something good will come of the split, but I'm not hopeful. I really wanted to like Koffice, but I couldn't get it working as well for me as Open Office. Go-OO and LibreOffice aren't as stable for me as Open Office right now either, so I think I'm going to keep using OO.o until things shake out a bit more.
I wonder if Koffice will no longer be part of the base KDE now.
I installed it manually and it seems to work fine (extracted rpms and copied to somewhere locally). It's actually faster than go-oo now.
Ah. I'm using the version that Eric (Alien Bob) compiled from source. Obviously, I won't know if that's the issue unless I install the same way you did to see if the issue pops up again. I probably won't get around to that for a few months, though.
I wonder if Koffice will no longer be part of the base KDE now.
I dont think its been for a while..
Quote:
Originally Posted by http://lists.kde.org/?l=koffice-devel&m=128837660923333&w=2
koffice iteslf is not a strategically significant component for KDE. that may
sound harsh, but i believe it to be true today. the user base is small, years
of releases did not culminate into a (market-)significant product over the
same time span in which 2.0-4.0 of the KDE SC was develped and released, etc.
it has provided some great value for KDE, however: it has helped strengthen
kdelibs, it has brought KDE some very positive light and recognition via key
involvement with ODF and some apps like Krita and Kexi have had their well
deserved moments of shining in the press. and of course those of us who use
KOffice applications are deeply grateful for it.
however, the truth is that without KOffice, KDE itself would continue on
without a huge shift in direction or even a huge hit on brand values. ergo, it
isn't (today) strategically significant. but it could be.
Ugh... I read through most of the thread. Bad stuff. My guess is that this will wind up sinking the whole project. I'm also thinking that trying to mix commercial interests (the deal with Nokia) with a group of mostly unpaid developers was probably not the smartest idea.
Ugh... I read through most of the thread. Bad stuff. My guess is that this will wind up sinking the whole project. I'm also thinking that trying to mix commercial interests (the deal with Nokia) with a group of mostly unpaid developers was probably not the smartest idea.
In this particular case you may be right, but in general Linux wouldn't be what it is without participation and contributions of enterprises with commercial interests. And I don't think, that Nokia should be blamed here as whole for the behaviour of one of its employees.
To my knowledge, Nokia usually maintains a relatively fair relationship with the FOSS community. Compare that to what Oracle currently is doing: In this case the whole company has caused a fork, LibreOffice, in just a few months, whereas the KOffice fork comes after years.
I hope for the best, maybe, after a phase of consolidation, development may be accelerated, if the fork attracts more developers. I really hope so, as the UI of KOffice is much more user-friendly than that of OOo and all its derivatives.
And as LibreOffice clearly demonstrates: A fork can be a good thing. It has replaced OOo on three of my machines, 32-bit Slackware Laptop, 64-bit Slackware64 Desktop/Server and a 32-bit WinXP laptop. Up to know, I don't see any problems, that OOo didn't have (such as inferior UI), but it runs A LOT faster. I haven't checked the said improved MS Office compatibility, but I'll have the opportunity to do so, soon.
In this particular case you may be right, but in general Linux wouldn't be what it is without participation and contributions of enterprises with commercial interests. And I don't think, that Nokia should be blamed here as whole for the behaviour of one of its employees.
To my knowledge, Nokia usually maintains a relatively fair relationship with the FOSS community. Compare that to what Oracle currently is doing: In this case the whole company has caused a fork, LibreOffice, in just a few months, whereas the KOffice fork comes after years.
I hope for the best, maybe, after a phase of consolidation, development may be accelerated, if the fork attracts more developers. I really hope so, as the UI of KOffice is much more user-friendly than that of OOo and all its derivatives.
And as LibreOffice clearly demonstrates: A fork can be a good thing. It has replaced OOo on three of my machines, 32-bit Slackware Laptop, 64-bit Slackware64 Desktop/Server and a 32-bit WinXP laptop. Up to know, I don't see any problems, that OOo didn't have (such as inferior UI), but it runs A LOT faster. I haven't checked the said improved MS Office compatibility, but I'll have the opportunity to do so, soon.
Show us your rsync commandline... my guess is that you forgot some parameters. Running rsync without parameters will list the remote files but not download them.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
