faq
flatforty
contribute
subscribe
configure
search
rdf
main
parent
|
so
by anon on Thursday 28/Feb/2008, @00:20
|
so kword might not make the first offical release. Hmmmm. That's not exactly a smart idea, especially when a word processor is the main reason people have for office software.
Personally I tried KOffice 2, what ever alpha or beta it is up to now, and it really was a waste of my time. It's like comparing an apple (microsoft office) to a peach (open office novell edition) to a sour old dried up lemon (koffice) I really do not think any windows users will be using that software, and the vast majority of linux users wont either, it's so lacking, and well, ugly. The GUI looks dated a decade compared to how office suits look now. |
|
|
The Fine Print: The following comments
are owned by whomever posted them.
( Reply )
|
Re: so
by Terracotta on Thursday 28/Feb/2008, @01:00
|
What do you expect from ALPHA quality software? It is lacking feautures and the GUI indeed needs some attention, but they are working on that. And if you've got good ideas... just let them know by bug reports.
Although I agree that a word processor is the key element of an office suite it might be usefull to have the base libraries and base programs (without kword then) out, just to make other developers aware of the infrastructure, IIRC Koffice 2 is using new baselibs and infrastructure, just like KDE 4 is using a new base.
I do like though that kpresenter has gotten a bit of love, the 1.6 version wasn't that great at all.
Just my 0.02€
|
[
Reply To This | View ]
|
Re: so
by Stefan Majewsky on Thursday 28/Feb/2008, @01:03
|
With "how office suits look now", do you mean these cluttered icon conglomerates and menu trees? If you think this interface is bad, improve it, or at least make suggestions, or shut up.
|
[
Reply To This | View ]
|
Re: so
by jospoortvliet on Thursday 28/Feb/2008, @01:17
|
I really don't get how you got to that impression. Didn't you by any chance try OpenOffice and mistake it for KOffice? I mean, that one looks like MS Office 96, sure. But KOffice looks rather different, and has a few pretty cool things. I just gave the latest SVN a try. It's not ready for use, sure, but some stuff is incredibly cool - esp vector graphics stuff in there. I'm really looking forward to a more stable KOffice.
|
[
Reply To This | View ]
|
Re: Joining force with openOffice
by Bobby on Thursday 28/Feb/2008, @01:22
|
FIrst i would like to show my appreciation to the KOffice devs for the wonderful work that they are doing, for their time sacrificed and their talents. They are few and therefore have come a long way but it's just not enough compared with openOffice like you pointed out.
I am just wondering if it wouldn't be a smart idea and more productive to join force with the openOffice guys. I mean, openOffice is improving so fast that I think it will be impossible for KOffice to catch up with it's present resources.
I am not a coder so forgive me if I am wrong but wouldn't it be easier to develop a Qt interface for openOffice and have it better integrated in KDE than to programme a whole office suite?
I personally think that there is too much duplication of efforts and wasting of resources in the opensource world.
|
[
Reply To This | View ]
|
Re: Joining force with openOffice
by Anon on Thursday 28/Feb/2008, @01:31
|
OO.o's codebase is so huge and wretched that I honestly can't imagine anyone volunteering to work on it on their own time, and there's no guarantee at all that Sun would grant commit-rights to outsiders (OO.o is developed very much in a Cathedral-style). Frankly, I consider working on KOffice a vastly more appealing prospect, *and* in terms of technology it is by far the "best bet" if you want to make rapid progress. The lack of money spent on it is the *only* thing keeping it from absolutely crushing OO.o, in my opinion.
|
[
Reply To This | View ]
|
Re: Joining force with openOffice
by eds on Thursday 28/Feb/2008, @01:34
|
No, it would be much harder to rewrite OpenOffice with Qt. OpenOffice.org codebase is so complex that it will really take away good developing time only to port it to Qt. In contrast, KOffice 2.0 is being rewritten and easier for developers to code (cleaner code base as well).
I believe currently KOffice has a very good technology (flake, pigment, etc) that will create a superior office suite in the future (given enough developers to pursue the dream). For example, using Flake technology you can embed any shape (chart, spreadsheet, vector graphics) in any KOffice application. This technology enables good component reuse and also better interaction among application.
|
[
Reply To This | View ]
|
Re: Joining force with openOffice
by Birdy on Thursday 28/Feb/2008, @14:27
|
1.) I don't think OOo is improving fast. They have to invest huge efforts to clean up the code and architecture (there a lot of work left for several years). And to be honest, I didn't see a lot of real improvements from 2.1 to 2.3 (and even the upcoming 2.4).
2.) Imagine the few KOffice developers helping the huge OOo team. That wouldn't make a lot of difference for OOo. Especially as the KOffice's developers expertise is in slihgtly differnent topics.
3.) KOffice has a extremely nice basis. Just a little bit more development power, and it would show up as a nicely polished Office package.
4.) It's very nice to have several different office packages. They can serve different purposes and thus have differnet focus/strengthes/GUI (does OOo have something like Krita, KPlato or Kivio?). And having different bases helps to detect defects (like ODF support in the past in OOo an KOffice). Imagine a piece of software that has no competition - progress stalls!
To sum it up: If KOffice would "join" OOo, it would mean very very little gain, but a big loss.
|
[
Reply To This | View ]
|
|
The Fine Print: The previous
comments are owned by whomever posted them.
( Reply )
|
|
![[KDE Dot News]](http://www.kde.org/dot/Images/kdedotnews.gif)
