The KOffice team is proud to announce KOffice version 1.5. With this release, KOffice starts its ascent into the office suite hall of fame. This version sports OpenDocument as the default file format, accessibility, a new project planning tool KPlato, professional color support and adjustment layers in Krita and the long awaited Kexi 1.0. You can read more about it in the press release and the full announcement. Packages are available for Kubuntu and SUSE.
KOffice was the first to support, and now with 1.5 the second office suite to announce full support for OpenDocument (ODF) as the default file format. With two independent implementations of ODF now available it is now a true industry standard. KOffice 1.5 is therefore the version that lets enterprises and organisations all over the world choose the office suite that fits their needs best.
Great care has been taken to ensure interoperability with other office software that supports OpenDocument, most notably OpenOffice.org. We acknowledge, however, that the ODF support and interoperability is not yet perfect. We hope to be able to quickly identify and fix the incompatibilities that do exist in the upcoming 1.5.1 and 1.5.2 bugfix releases.
KOffice is already the most comprehensive office suite in existence. In addition to the basic productivity applications mentioned above, it also includes a creativity application suite featuring Krita, a paint application with lots of image manipulation features, Karbon, a vector graphics application and Kivio, a flowcharting application. Other components are Kexi, an integrated environment for creating database applications and KPlato, a program for project management.
Thank you for this. I love Koffice, its usabilty, speed and general niceness.
Whuhuu, Debian unstable has also packages already. Good work everyone!
The i18n packages will be uploaded soon too :)
Day started with good news! It's really great day, IMHO:)). I love KOffice for it's stability on mypreferred platform (i386-OpenBSD) and I'm glad that now I have truely KDE-integrated stable (I hope... I believe!:)) office suite! THank you, guys, and thanks again!
Together with other KOffice developers I have put together a comprehensive tour through new features and improvements of the KOffice 1.5 release - the most exciting highlights, check it out here:
Brilliant! Thank you!
I dont really understand the purpose of koshell. Its in the way and unbelievable cluttered - its not any help at all. In fact i dont uderstand why much else than kword is included as they are hardly usable. Please concentrate on kword and dump the rest.
Ah the smell of troll in the afternoon.
How childish of you to take the easy way out, ziggy boy. The lack of quality of koffice is no secret due to the lack of developers. It would simply be a better idea to concentrate on kword - an excellent and different type of editor- instead of wasting ressources on kpresenter, kexi or whatever. At least reduce koffice to two or three official apps and get the others out of the way - nobody uses them anyway and they lower the overrall quality. And dump koshell - it does not serve any purpose when its implementet so lousy.
c'mon... the lack of quality... that's not true! you might say Koffice doesn't have all features MS office or OO.o have, but it certainly is not bad, it's already very complete, and even has some points in which it surpasses both mentioned office suites. Krita is a wonderfull app, goin' for world domination. kpresenter is very decent, and so are most other components. plus, there is no office suite that has half the integration Koffice has.
There is an obvious lack of quality even in kword. I dont complain about that - i just complain about the fact that kword is so much better than the other apps in the suit, that the other apps are not in the same league. Since they obviously lack developers - a complaint koffice devs often air - the solution is clear - dump anything other than kword!
I use word daily at work and dont miss any features in kword og oowriter.
Koshells problem is the GUI - its really unfriendly the besides being butt-ugly. I really fail to see the purpose for it - as someone else pointet out -there is kicker why is that shell needed?
Putting aside the ridiculous nature of your conclusions, you make the incorrect assumption that many others have made about open source software which is that if developers weren't working on something you don't want then they would automatically start working on the stuff that you do want.
Open source developers tend to work on things that they are personally interested in. I'd imagine that many of the KOffice developers would not be as keen to work on KOffice if it only included KWord, so nothing would really be solved by "dumping" the other applications.
I dont make any assumptions. I just conclude that anything else than kword, that i have tryed, does not live up to kwords quality. Its not that kword is that good either but its usable and fullfills the needs i have with it.
Exactly the same conclusions have been made by others here and in other places. I think its a bad idea to join half-baked apps to a suit just to have a suit.
Your ridiculous conclusions about what i want do not matter since I did not mention what i want. I dont intend to formulate "demands" to people that develop for free.
Why don't you *try* some apps before trolling? Get the new release and try, let's say, Kexi and Krita, and tell me they are not good apps.
Then we can talk. The only app I can say is not really up to speed is KSpread. It is not fast and reliable enough for large spreadsheets. But it is getting better, and I would encourage its developers, never say it is crap.
One of the main advantages of KOffice is the wide range of apps. Different people have different interests. A developer may want to work on the formula engine of KSpread, other in Krita's tablet support and another in KWord footnote support. If you kill the other apps, you will end up with less developers, not more, as they will not automagically change their interests.
I'm not trolling. I've been using Koffice since the beginning and KDE since the summer of 98. Some of you guys here seem to think that any critique is an attack. Sad for you.
The thing im saying is dump koffice and concentrate only on a few apps. The only app that works fine is kword so concentrate on that one - the others are an enbaressement.
I dont use krita - i find it ugly and unpleasent to use. I prefer inkscape and the old killustrator. Kexi i dont see the purpose for it. I dont even know anyone that uses those type of apps. Is access really used that much in offices?
>I've been using Koffice since the beginning and KDE since the summer of 98.
So you use it since it was actually unusable...
>The thing im saying is dump koffice and concentrate only on a few apps. The >only app that works fine is kword so concentrate on that one - the others are >an enbaressement.
If you think they are bad then don't use them. To say to a developer to drop
some apps not even caring to tell him why is simply stupid. You say krita and
kexi are an embarassment. Care to explain why? How do you think they could
improve? If you don't have anything constructive to say other than "I don't know anyone that uses it" then, better shut up.
>I dont use krita - i find it ugly and unpleasent to use.
And who cares what YOU find ugly and umpleasant?
>I prefer inkscape and the old killustrator.
And who cares what YOU prefer? KOffice developers keep you from using the
software you prefer?
>Kexi i dont see the purpose for it.
Amusing. You have the nerve to criticise a program you don't even know the
purpose of it. If the fact that "Josel don't see the purpose of it" were
enough reason to force devs to drop their apps, I'm afraid that 99% of the
software in the world would disappear in a fortnight.
>I dont even know anyone that uses those type of apps.
And, obviously, you believe that the fact that YOU don't know anyone that uses
an app is more than enough reason for the developers of that app to drop it.
>Is access really used that much in offices?
Go tell Microsoft to drop Access an concentrate on Word because "Josel don't
see the point of that kind of app".
You are a laugh my friend.
> So you use it since it was actually unusable...
I used it since before version 1.0. You dont find any complaints from me prior to that. And you wont even find many complaints after that. I just get frustrated with the stupid marketing speek.
>you think they are bad then don't use them. To say to a developer to drop
>some apps not even caring to tell him why is simply stupid. You say krita and
>kexi are an embarassment. Care to explain why? How do you think they could
>improve? If you don't have anything constructive to say other than "I don't know >anyone that uses it" then, better shut up.
I dont use them them because i find them bad and their equivalents superior and not so krash prone. I couldnt even open karbon whithout running kbuildsysca - hey im no developer. So no i dont shut up
>And who cares what YOU find ugly and umpleasant?
>And who cares what YOU prefer?
>Amusing.... bla bla bla
Relax. Thats just my opinion. Im not that important
>You are a laugh my friend.
No you are. Im just expressing my opinion. You go bananas because of it? Go eat your pill.
>>And who cares what YOU find ugly and umpleasant?
>>And who cares what YOU prefer?
>>Amusing.... bla bla bla
>Relax. Thats just my opinion. Im not that important
Well, I see you got the point: Nobody cares about your opinion.
That could be different if you were an informed user who actually knows
what he is talking about. Unfortunately that's not the case...
> Kexi i dont see the purpose for it. I dont even know anyone
> that uses those type of apps. Is access really used that much in offices?
Here you show your ignorance. Access is widely used by businesses who in many cases don't have in-house professional developers, and find Access much easier to deal with than something like VB for developing simple data-driven applications. Users have been clamouring for a long time now for an open-source Access replacement, and IMO until Kexi came along there wasn't really one piece of software that satisfied that need. In fact Kexi goes further than Access in many areas and may even be easier to use in many respects.
Wow. I would like to see some numbers for "users" that want Access and especially for end-users in buzinezzzzz that are able to make anything interesting with Access and dont have a developer/geek background. The last cathegory i dont think exist.
There is lots of in-house developed Excel stuff but praticaly no Access stuff. I only ever came ocross one Access app - and not developed by business people.
But this discussion is pointless. Developer develop whatever they want. I simply think that there should be no Koffice since the quality of software other than kword is too low.
Josel, your experience is very, very limited. If you have seen only one Access application you simply haven't seen much of the world. In the fourteen years since I translated the first edition of the Access Bible into Dutch I've seen scores of Access applications created by secretaries, sales people, but also engineers and scholars. And programmers, yes, them too. Not to mention the number of Access frontends to Excel spreadsheets. In the real world, both get a lot of use.
As for thinking that there should be no KOffice, well, make a noise like a hoop and roll away, will you? This silly nonsense is getting tiresome.
I am an Oracle developer, but I use Access every day. I have to process data from many different sources, and Access is the lingua franca for all of them. I can write a complex query in just a few seconds and get the results in an editable recordset. I can write custom functions using regular expressions, xml, and all the VB6 and VBA functions. I can quickly create interfaces using tree-views, drop-downs, sub-forms etc. People that denigrate Access just haven't seen it used competently. My only complaint is that Microsoft has neglected it lately in order to promote sqlsvr and dot-net. Will KOffice ever provide a coding interface comparable to VBA?
But the object model will in all probability always be different from VBA, because the object model of the underlying application is different.
In fact, some people would be surprised to know the amount of people who actually earns a living with MS Access.
Just because you don't use or want a presentation or database application that is nicely integrated with KDE, doesn't mean that everyone else shares that view.
Very strange of you to use Kexi as an example. Kexi is the program that is truly unique in KOffice, and the one that very many people have been waiting for. Besides, one of the main strengths of KOffice is its breadth and integration, something that many mention as the direct reason to use KOffice from the beginning.
Regarding koshell, we would be interested in hearing how you think it could be improved.
> Regarding koshell, we would be interested in hearing how you think it could be improved.
Drop it. It's crappy and useless. :)
The problem is that it was the result of users -- just like you -- complaining "I'd use KOffice if it were more like Outlook". (Seriously -- go back in the mailing lists and even on this board). That integration that you dislike so much? That's the result of listening to users.
So, you're a user, eh?
> So, you're a user, eh?
Sure. You aren't!? ;) I'm not interested digging into the history of koshell, but always assumed it should become something similar to the dead old MS Office toolbar. If there was a well defined goal to reach with koshell (no, the Outlook quote doesn't count imho), the result failed to deliver.
> "I'd use KOffice if it were more like Outlook".
Probably an example, that it's not always fruitful to listen to every weird wish/opinion. An office suite simply isn't a PIM.
> That integration that you dislike so much?
No. Koshell is just wasted space on the desktop. When I want be able to start an applicaton quickly, I add it to Kicker. When I want to insert another (KOffice) object I do it from within the application. I haven't even a clue what you mean with the integration stanza in context of koshell. To me it's a weird, unusable thing I never have used and never heard or read that anyone is using it.
if there is something you don't like about any aspect of koffice or any kde application you are more than welcome to change it to fit your needs our kde developers code for them selfs and the community as a selfless act something they do not have to do.
Another option is to pay a developer to implament the changes you wish to be made im sure there is a c++/Qt developer more than willing to take your money.
You really should not speak bad of the koffice project it is free.
If you wish to learn about the resources you will need to be able to contribute
to the koffice project there are to very good books you can get.
1. C++ without fear
2. C++ GUI Programming with QT3
3. Just google for all the free c++ and kde/qt tutorials.
Untill you have the motivation to find out what it is like to be in there shoes
i wouldn't complain about koffices quality.
Last but not least have just a little bit more respect when you post here all
your doing is showing everyone the type of jackass you really are :).
I can't hear this sort of blah, blah anymore. Everyone has an opinion on everything. Calling one to hold his mouth, because he gets something for free is extremely stupid, but unfortunately not uncommon in the FOSS world, when someone isn't able to grok opinions of others.
> You really should not speak bad of the koffice project it is free.
I haven't done so. I spoke about a single, minor, unusable part of it. I haven't even a problem with koshell being a part of KOffice. It's just not worth developers time / maintenance.
And just how can YOU tell a developer what is worth his/her time? If they are developing it, it is obviously worth the time to THEM. Especially given the fact that they are working on it for free and aren't being mandated by a company to do it. Just because you see no value in it does not mean there is no value in it.
So you're another one, who doesn't know what an opinion is. I tell no one what to do. I simply answered Inge's question from my point of view. What the KOffice developers do is up to them.
Oh I know what an opinion is. I also know that most people don't mind criticism or advice if it's viewed as constructive. Saying someone's work is a waste of time just comes across badly. I personally never use Koshell, but I won't trash the developers efforts if they choose to develop it.
Well if koshell is the part of koffice you do not like then remove it from your copy.
And upload the changes somewhere others can also make use of your changes better yet supply the community with a patch.
You can install KOffice without koshell already (when the distributor supports it or when you compile from source). This wasn't my point anyways.
No i get your point.
But i cant bring myself to agree, see i think ms windows is a useless peice of software and a huge waist of time i fought windows users for years trying to show them alternatives but in the end people just get mad and i learned a valuble lesson if even 1 person finds value in something then everything that had to be endured in the process of its creation was worth it.
Even if the only person that found any usefullness for say koshell was a single developer then it creation has been justifyed. no matter what!
I am having all kinds of broken dependencies when trying to install this on Suse 10.0.
libmysqlclient.so.14 is needed by koffice-database-mysql-1.5.0-2
libpqxx-2.2.7.so is needed by koffice-database-psql-1.5.0-2
kdelibs3-devel is needed by koffice-devel-1.5.0-2
libruby.so.1.8 is needed by koffice-ruby-1.5.0-2
libgsf-1.so.113 is needed by koffice-wordprocessing-1.5.0-2
libwv2.so.1 is needed by koffice-wordprocessing-1.5.0-2
libgsf-1.so.113 is needed by libwpd-0.8.4-3
libgsf-devel is needed by libwpd-devel-0.8.4-3
glib2-devel is needed by libwpd-devel-0.8.4-3
libgsf-devel is needed by libwpd-tools-0.8.4-3
glib2-devel is needed by libwpd-tools-0.8.4-3
libgsf-1.so.113 is needed by libwpd-tools-0.8.4-3
Anybody have any tips?
Broken dependencies? kdelibs3-devel etc.? You must be joking.
> Anybody have any tips?
Install the required rpms? Skip packages you don't need (devel, mysql, pysql)?
Use a packet manager like YaST to resolve/install dependencies?
Did You upgrade via YaST? I did, and all dependencies were resolved (SUSE 10.0, AMD64.
I am having the exact same problem installing Koffice write. YAST does not resolve the problems. I have also tried separately installing the missing links but seem to be in an endless loop of one requiring the other (i.e., libgsf-1.s0o.113 and libwpd-0.8 are both broken links needing each other).
One reply here hints that only stupid people would have trouble. Well, it really doesn't matter because I am another user who cannot get Koffice to work and if the Koffice people really want to develop any loyalty they should fix the difficulty. I've spent several hours trying to get this to work and there is high likelihood that I will not get back to this in the near future. I'm left with the feeling that Koffice is not worth the bother and I wonder how many other people will feel the same way.
By the way, I have been programming in many languages and operating systems beginning with IBM 1620 in 1965 so I can usually hack my way through problems.
You have to install KDE 3.5.2 from supplementary repository.
Sorry, but try to understand: the KOffice people (meaning me, David, Thomas, Rob, Laurent, Thorsten, Peter, Alfredo, Ariya, Tomas, Jaroslaw and a host of other people) cannot do a thing to fix the SuSE packages. We don't make those packages, creating packages is a whole different kind of expertise, one that a developer doesn't have, in general.
You're not stupid for not getting the SuSE packages to work, in fact, I, and I'm a KOffice developer, cannot get Krita not to crash when doing color adjustment under SuSE. It works perfectly with Kubuntu...
That said, SuSE is a great distribution and the distribution I prefer to use on my server and I simply wouldn't be able to create better packages. I can code nor do documentation; I cannot create packages. Other people cannot code; they do documentation, other people can do packages.
But things get broken, errors do occur. It's impossible to develop software and not depend on external libraries -- unless you're a one hundred man strong team, paid to do development fulltime, and do everything yourself, like the OpenOffice team -- and even then, I would question the wisdom of doing without libraries. Libraries are a fact of life: and outside our control. Sorry for that.
I'm a recent "switcher" sort of, from Windows to Linux Suse 10. I am having trouble installing anything on Suse then finding it, and making it work. It is so much easier in Windows to install a program.
I am otherwise very impressed with Suse Linux. I also have high hopes that Linux will soon offer an everyday user a alternative to Windows. I think Linux is close but for me at least installing "stuff" on Linux Suse is a complete puzzle.
Very good news. Anybody offering package for Tomahawk Desktop?
With Tomahawk Desktop, you don't have to wait until somebody package it for you. Just do following:
1. Open a Konsole, type su and login as root
2. su koffice
3. uninstall_package koffice
4. (a) Copy the new koffice-1.5.0.tar.bz2 to your current directory (/usr/src/koffice/) if you have already downloaded the source package. OR
(b) If you have not downloaded the source package, just type following and press Enter:
5. Check the md5sum:
it should be: 220b6bde28b5ebd5c6621bc87ca2c05f
6. bunzip2 koffice-1.5.0.tar.bz2
7. tar xf koffice-1.5.0.tar
8. cd koffice-1.5.0
9. ./configure --prefix=/usr --sysconfdir=/etc --disable-debug
10. make >& koffice-make.log
11. make install >& koffice-install.log
Its the same concept to upgrade any other package.
> With Tomahawk Desktop, you don't have to wait until somebody package it for you.
> 9. ./configure
> 10. make
> 11. make install
What a quite unique feature of Tomahawk Desktop!
well, as Tomahawk installs Koffice now as a user (Koffice) you can just remove all files from this user, and Koffice is removed. or package all files of this user, and you have a package. so it is a bit more clever than the normal 'configure/make/make install', and very unix-like. no central database that can be broken, or stuff like that...
tough i still prefer a decent package management like debian or gentoo have :D
and you package your .tar.gz to a .run, you have a Nvidia style package :)
If you're going to compile anyway, I prefer the Gentoo way:
emerge -av koffice
Looks a lot simpler than this Tomahawk thing that keeps getting spamvertised here.