KOffice 1.3 has been released today. See the
and the complete list of changes.
KOffice 1.3 consists of the following applications:
- KWord - A frame-based word processor
- KSpread - An advanced spreadsheet application
- KPresenter - A full-featured presentation program
- Kivio - A Visio®-style flowcharting application
- Karbon14 - A vector drawing application
- Kugar - A tool for generating business quality reports
- KChart - An integrated graph and chart drawing tool
- KFormula - A powerful formula editor
Big improvements have been made in KOffice 1.3 with respect to
interoperability with other office file formats. It is now for
example possible to import as well as export OpenOffice.org
documents. Also new is the ability to import PDF files into KWord
and make changes to the document. Support for Microsoft document
formats has improved as well.
Is there any active development on Karbon14?
A bit, yes. The author of Karbon14 has been *very* busy with KSVG, I guess Karbon will get more attention in the furure.
should mean karbon is well integrated with ksvg :)
But why is karbon in koffice and not in kdegraphics? Illogical surely: the bitmap editor kpaint is in graphics, not office, so why is the vector editor different?
Well, the bitmap editor Krita is also in KOffice...
I think it would be nice to have something like KDE Graphic Suite or KStudio. A collection of programs for graphic work like KOffice. With
- vector programm
- pixel programm
- a autotrace.sf.net frontend
- a SANE frontend
- a gphoto frontend
- an image viewer
- image organizer
+1 for this
Would be great if the PyQT and PyKDE bindings would go into the KDE standard-distribution. Then a lot more people (like me) would be able to contribute code to the KDE-project, something like an image-organizer would profit from a lot of input of different people.
"a gphoto frontend"
There is camera:/ in konqueror. :)
To have a "ral" gphoto frontend there is digikam (http://digikam.sourceforge.net/) which is pretty powerful. With all it's plugins of version 0.6 it's becoming a real suit...
Is ther a WebCVS browser for KOffice?
For what do you need it? I mean, you have eg. Konqueror as the browser, no need for a special integration in KOffice.
Or do you simple mean: http://webcvs.kde.org/cgi-bin/cvsweb.cgi/koffice/
http://webcvs.kde.org/cgi-bin/cvsweb.cgi/koffice/ was what I was searching for.
Congrats, but some of the screenshots are sooooooow ugly...
Personally I don't make prettiness my primary concern when I'm picking out, say, a spreadsheet application...
I agree. First of all, because it is an office suite, all the screenshots should be taken using the same theme. Hopefully the current theme, and not the kde 2.x theme or beos theme.
Screenshots are supposed to convey good things about the application, these convey nothing but uglyness.
Also, I thought the issue with the lack of anti-aliasing on bold and italic buttons was resolved years ago. I guess not.
That issue has been resolved, at least in my KDE 3.2 RC1 installation...
Check out the attached screenshot.
Ahhh.. another Plastik fan?
Yup. Keramik is definitely an interesting and unique style, but I find Plastik easier on the eyes for everyday usage. Thin Keramik also looks interesting but I haven't taken the time to install it and try it out. Plastik comes with KDE now so it takes no effort to switch.
I was going to rebuttle this, but then I did went and checked out all of the screenshots. The applications themselves are fine, but they are quite inconcistant in widget theme, widget color(s), icon set and window manager theme. Maybe it wouldn't be a bad idea to re-generate them using the latest release and KDE 3.2 :) Are the files in the screenshots located cvs (if not, why not :)? Might there even be a way to automate the capture of screenshots?
I agree. I think I only saw one screenshot that used the current default KDE theme. The crappy quick 5 second PNG picture, KDE RULEZ, Wazzzzaaaauupp!!!, poorly laid out spreadsheets/photos/etc needs to go and visually appealing content needs to replace it. Screenshots with a huge number of toolbars needs to be reduce to the essentials (simplicity).
An office suite should show consistency across the applications .. these screenshots do not show that.
A new release announcement should show off new features visually .. I'm hard pressed to see them in these shots (ie alpha channel images in KPresenter).
How does KDE-Enterprise ever expect to be successful with this level of official PR material? For as talented as the KDE developers are, they need equally as talented PR/Marketing people that can take all that is so great about KDE and get users and non-users truly excited about it.
well maybe they need more PR/Marketing people. Ever thought of that :)
> well maybe they need more PR/Marketing people. Ever thought of that :)
Hold on a second there Fab... this is a pretty revolutionairy thought. The point of the conversation is about what *other* people should do... you're getting uncomfortably close to suggesting that our large and productive number of contributing critics should take on the mantle of (shudder) performer on this great stage. Great googly moogly man! Do you realize the terrible commitment and risk here? I think you should stop making such controversial veiled suggestions... before you upset some critics and they don't show up for work tomorrow... especially if their busy helping a project. For shame!
hehe..pretty funny.. i'm doing my share tho i think with packaging kde for cAos (www.caosity.org), but maybe someone else has time?
It's not a bug, it is a feature :P
If you want better screenshots on koffice.org and you are a volunteer to take care of it, then contact us on one of the koffice mailing lists.
Otherwise it is and will remain provisory.
Have a nice day!
seems Slashdotted. Or should I say: K-Dotted?
This should be posted on slashdot.
Isn't this the only open source office suite developed from scratch?
I mean, open/star-office was proprietary in the beginning...
There is even Gnome Office.
GNOME Office is an ancient joke, just go and try to find a reference to it on http://www.gnome.org - not even the GNOMEs believe in it.
Abiword is a very solid word processor. Gnumeric blows away all of the spreadsheets I have used on Linux. It has better support for Excel files than OpenOffice.org.
These are single applications. There is no integration to an office suite.
agreed.. however, gnumeric and abiword almost have nothing to do with each other :(
> Abiword is a very solid word processor
Well, yes and no.
In a fair comparison, it is a solid text editor with extra features (fonts etc..).
But, it does not have the frame capabilities of eg KWord.
And it doesn't integrate with anything.
This is what people would expect from an office tool today.
Abiword is a great standalone app though! :-)
No, that is what people expect of an office suite when they want to bash GNOME office.
I have used Office suites quite extensively, and can state with reasonable authority that most people do not use the intergration features of an Office suite. In fact, they use them as they used them 10 years ago. As standalone apps. People rarely use the features that are constantly hailed as the next big thing. If they really did, people would not even talk about KOffice when talking about good office suites. Because it offers nothing. The last time I tried Koffice, or kspread to be specific, I could not vlookup, hlookup, lookup or a bunch of other VERY IMPORTANT functions. How they heck do you use a spreadhseet without being able to lookup. It is a bunch cells, and looking up is the most basic thing I do with a spreadsheet. Now Gnumeric, there is a spreadsheet. Better than oocalc and some people rate it higher than Excel in some ways. Intergration can come later, I am sure its not too difficult. The infrastructure is all there. The problem is that many of these GNOME office apps are also meant to be cross platform anyway, and they were all developed by people to scratch an itch as it were.
Abiword is very good at what it does, and is developing logically forward. I think integration is good, but I rate a complete coverage of Excel functions far higher than integration any day.
You do have a point there.
But don't forget the aim of Koffice. From the start, to make an integrated suite
for quality compositions.
And with frame based KWord, integrating sheets etc from KSpread is great.
Especially for making desktop publishing swift.
This is partly why this project is so cool.
And also, that few users actually use a feature doesn't mean that they don't need that feature. It might just mean that it's not obvious how to use it. Usability. If there is an easy way to use eg integration, users could just as quickly start using it saying "Hey, great feature!".
Can you put a single KSpread cell in a KWord document?
Can you have a figure in the middle of a sentence in a KWord document and have it linked to a cell in a KSpread file?
Why does each application have its own file format?
How do I make a chart with KChart using the figures in a KSpread file?
If we want a true integrated office suite, we need to design one, and then implement one (probably well over 90% of the work done so far can be used).
KDE provides the technology to have a truly integrated office suite. But, we need to use it. If we can somehow accomplish this we will have *THE* killer application.
I have to agree with you and disagree with you.
KOffice is lacking a lot of features -- to the point that I can't see why it has a version number > 0.5.
However, since with KParts, integration should be the major feature of KOffice. This should have been developed first.
Now as it stands, version 1.3 lacks both features and real integration.
Where do we go from here? I think that the integration is the most important issue. However spreadsheet functions seem like an independent development track which could be implemented without affecting the main development path.
I think we're really going to have to get our heads together and come up with some ways to fund KOffice more and push it forwards. There is some stuff in here that is not in Open Office, and Kivio in partiular, looks marvellous. You can't tell me that stuff like Kivio and Kugar are not going to useful to businesses.
Quite frankly, with the time, resources and manpower available, KOffice is a huge advertisement for the development power of Qt and KDE.
I'd really love to. I just have all my time and funding wrapped up in Quanta. However it's also a great advertisement, and unlike office products is aimed at a less mature moving target. So it can more easily out pace windows market leaders. I wish I had resources for both, but never understimate how many web developers there are on the web. ;-)
Yes, we need to design first and code second -- rather than the other way around.
Specifically about Krita: Should this be an application suitable for artists, or should it just contain the basic paint functions needed to make office presentation slides and for desktop publishing?
Karbon14 & Krita: I think that these should be unified into a single application -- if they remain separate applications and they have the features which I want, they will have a lot of redundant code.
Killer application: I realize that KOffice was assembled from several applications, but I do not understand why it is structured as separate applications since they are not really applications but rathere KParts. It would be much better to have it structured as a single application with a single file format like gobeProductive. This doesn't have to be an either/or question; it would be possible to develop that type of interface in addition to the current separate application interface.
NOTE: if you don't know what gobeProductive is, there is a preview:
This will run with WINE, but you have to install MSI first. Be sure that you have fonts installed in your fake: "C:\Windows\Fonts" directory.
After about five years of development, I don't think it's a good idea to stop development on Krita and go back to the design stage... I think it's an amazingly bad idea, in fact. If you want to design a paint app from the ground up, fine, please do. And if you want to base it on the KOffice libs, nobody will stop you. And when you're done and it's better than Krita, I won't oppose swapping your app into KOffice, and Krita out -- no problem.
Meanwhile, I'll just quietly (or rather, not quietly, but that's because I'm a verbose kind of person) go on hacking Krita in my amateur way, first trying to implement what's needed most to do simple pixel-mangling, learning how this entire graphics wheeze works, and then going on to make it the application I feel is still missing from the entire OSS/Free Software portfolio. Rather than the app you feel is missing. Can't help that, the chemise being closer than the trousers.
(By now Krita now supports the layer effect thingy -- a bit limited, but that's just because I haven't implemented fancy composition operators like 'bumpmap' yet (or rather, haven't ported them from GraphicsMagick yet), and a Krita image can now consist of layers of different image types -- a grayscale layer over a CMYK is now entirely possible. Still no eraser too, though.)
I think that you confuse the application which your are developing -- which IIUC will be a great application -- with the question of what should be included in KOffice.
Should KOffice include a paint application that will ultimately be a larger application than The GIMP? While such an application will be a nice addition to the list of KDE applications, I simply do not think that it belongs in KOffice. A possible solution to this would be to have a light version included with KOffice and the larger application be a stand alone application.
The same idea probably applies to Karbon14.
No worries for the moment... Krita won't become bigger than the Gimp for years.
Why would we set some size restraints on what may be included in KOffice? If it's useful to people I don't see any problems including it.
You do talk a lot considering the amount of work you're doing...
> Why would we set some size restraints on what may be included in KOffice?
Because it is an *office* application, not an artists painting application.
> If it's useful to people I don't see any problems including it.
It it is too complicated -- like The GIMP -- it won't meet the needs of those users that normally use an office suite. My perception of the needs of office users might not be correct, but I think that it is a reasonable position.
> You do talk a lot considering the amount of work you're doing.
I fail to see your point. I think that we could use several more people to think about things and discuss their thoughts.
Don't worry -- it's just one of James' favourite hobby horses. His flogging the beast now and then does no harm -- after all it's not talk that determines what happens, and I see very little danger of the powers that be (if they be, which I sometimes doubt) deciding to evict Krita for being too capable. For being too immature, incomplete and so on after five years of development, yes. But not for being too capable. Not on your nelly.
For the point of combining a vector app with a bitmap app you realy dont have to, when speaking of Krita and Karbon. You only have to connect the dots :-). Both apps use KOffice libs, eg they are kparts and they have layers. Then the only ting needed is to have the apps accept a layer wich is an kpart.
As I don't have a clue of the code involved perhaps I'm talking nonsens :-)
put that in /usr/portage/app-office/koffice and enjoy :)
emerge koffice-1.3.ebuild digest
emerge -pv /usr/portage/app-office/koffice/koffice-1.3.ebuild
It is building for me now and I am happy!
And if you happen to have Debian (Unstable?), use this:
deb http://rs.fuzz.nl/muesli/686/kde_head/ unstable/
It will also install KDE 3.2 CVS, however.
I am running Mepis Linux (a debian offshoot) and I have added
the following line to the end of my /etc/apt/sources.list file:
deb http://rs.fuzz.nl/muesli/686/kde_head/ unstable/
Then I ran
% apt-get update
% apt-get -V upgrade
And it did not find the kde-3.2 or koffice 1.3.
Do I have to do something else to pick up the packages path