Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

KDE Readies KOffice 2.0 As OpenOffice Competitor

Posted by kdawson on Tue Oct 09, 2007 06:52 PM
from the another-country-heard-from dept.
Da Massive writes in with a link to a story on KOffice 2.0, the next generation of the KDE office suite due sometime next year. In an interview with KDE spokesman Sebastian Kugler, Computerworld reports that KOffice 2.0 will be leaner, faster, and enjoy a cleaner code base than OpenOffice. It will also feature more applications, including an Access-like database creator, a flowcharter, and an image manipulation tool. KOffice is not yet fully compatible with ODF but the claim is that 2.0 will be.
+ -
story

Related Stories

[+] Review of KOffice 2.0 Alpha 8 – On Windows 162 comments
4WebChimps writes "As featured previously on Slashdot, the KOffice project is working towards a cross-platform, open source office suite for Linux, Windows and Mac OS X. The most recent release, KOffice 2.0 Alpha 8, achieved that goal by being the first release for all three operating systems simultaneously. Want to try KOffice on Windows? TechWorld has a review (with screenshots) of KOffice on Windows, including the installation process which is as simple as clicking a few buttons (the online installer does the rest). Hopefully it won't be long before KOffice sits alongside OpenOffice.org as a usable cross-platform open source productivity suite."
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • KOffice 2.0 is FAST! (Score:5, Interesting)

    by Anonymous Coward on Tuesday October 09 2007, @07:03PM (#20919501)
    The main benefit KOffice 2.0 brings is that it's sleek and fast. Unlike OpenOffice.org, KOffice has a very sensible architecture. Now, part of that is because KOffice is a far newer application. It builds directly on top of Qt, rather than implementing its own UI layer (like OpenOffice.org does). It also has a far more sensible component model, that suffers from only a small fraction of the bloat of the OO.o model.

    While OpenOffice.org may have a larger feature set at this point, it just won't be able to compete with KOffice when it comes to being responsive and memory-efficient. Having built the KOffice source code from SVN just last week, I can tell you that you'll notice the difference immediately. OpenOffice.org just feels really damn sluggish, while KOffice is quick.
    • by Taxman415a (863020) on Tuesday October 09 2007, @07:50PM (#20919983) Homepage Journal
      You're not kidding. This article made me think to go install v 1.6. On a 1.8 Ghz processor running Gnome, Kword for ex opens extremely quickly and opens files quickly as well. This gives me hope that the rest of the codebase is that lean and clean and that it can eventually outdo oo.org. Hopefully it can start to hit critical mass to achieve greater developer mindshare. It's already got oo.org beat in code quality it seems, so hopefully soon in features.

      I can certainly say the formula editor is miles ahead of oo.org's in terms of ease of use. I get a font error right away though in starting the formula editor, so I guess I'm off to file a bug report.
    • Re: (Score:3, Interesting)

      I installed it when I learned of Krita because I wanted to try it out. I had some issues with opening a file (forget what kind now) and tried KOffice and was very surprised to learn it not only opened it, but did it fast.

      It has been my office app of choice since then.
    • by BRSloth (578824) * <julio@@@juliobiason...net> on Tuesday October 09 2007, @08:10PM (#20920153) Homepage Journal
      As long as you run KDE, I guess. Otherwise, it will take a much longer startup just to put every single daemon KDE uses and load all other libraries.

      In the end, I guess it is fast for KDE users; people using other desktop environments will see no difference.

      [Just guessing here, from my experience with older KOffice parts running inside GNOME. Yes, they run and will still run.]
    • by theguyfromsaturn (802938) on Tuesday October 09 2007, @08:31PM (#20920331)
      And KOffice can open PDFs for editing. Awesome. Sure, the layout rendering is not always exact, but it does a tremendous job of converting the PDF to paragraphs, with the occasional embedded images. Scribus is also nice to import PostScript (why not PDFs?...) and respect the layout, but the text is usually broken down into individual characters. KWord does a great job with it. All in all, they each do their own job. It has allowed me to save some documents whose original editable copies got lost somehow... and for which I only had the PDF left. It's not as good as OOo at opening MS Office documents though, and the equations from ODF files aren't imported yet, but it's awesoooome.
      • Re: (Score:3, Informative)

        by Anonymous Coward
        $pdf2ps document.pdf

        (Part of ghostscript.)
        • by bdubSOv1iKIJ403M (712039) <bizwrf7sNO@SPAMverizon.net> on Wednesday October 10 2007, @02:10AM (#20923323) Journal
          Converting a PDF document into an editable form is like taking a screenshot of slashdot and trying to reconstruct what the HTML and CSS was.

          Postscript, the precurser to PDF, is basically a layout system; draw a string here, draw a string there, etc. It is very good at preserving layout. However, some information is lost. Consider an embedded table, for instance. In the original document, a table might be defined with

          -table
              -row
                  -Firstname
                  -Lastname
                -row
                    Jack
                    Bauer
                -row
                    Anonymous
                    Coward
          -endtable

          Once converted to pdf, it might be represented by

          Drawline(200,200,400,200)
          Drawline(200,300,400,300)
          Drawline(200,400,400,400)
          Drawline(200,500,400,500)

          Drawline(200,200,200,400)
          Drawline(300,200,300,400)
          Drawline(400,200,400,400)

          PaintString("Firstname", 200,400)
          PaintString("Lastname", 300,400)
          PaintString("Jack", 200, 300)
          PaintString("Bauer", 300, 300)
          PaintString("Anonymous", 200, 200)
          PaintString("Coward", 300, 200)

  • by jpfed (1095443) <.jerry.federspiel. .at. .gmail.com.> on Tuesday October 09 2007, @07:03PM (#20919507)

    Computerworld reports that KOffice 2.0 will be leaner, faster, and enjoy a cleaner code base than OpenOffice.
    I'm glad they're setting the bar high for themselves.
  • If it doesn't work in Windows, it will only see a fraction of the OO.o market.
    The point of the open source movement was to ensure people have a choice. make software better and open and hopefully that will make it common. If Koffice can do better than Openoffice then they'll have the attention of at least the /.ers here :)
    • by QuantumG (50515) <qg@biodome.org> on Tuesday October 09 2007, @07:09PM (#20919591) Homepage Journal

      The point of the open source movement was to ensure people have a choice.
      False.

      The point of the "open source" movement is to improve the way software is developed by opening it up and distributing it.

      The point of the "free software" movement is to ensure that software is freely redistributable, and modifiable by the users of the software.

      As for this "choice" thing you're talking about. That's the function of the market isn't it? Wouldn't just proprietary software give people "choice"?

      • As for this "choice" thing you're talking about. That's the function of the market isn't it? Wouldn't just proprietary software give people "choice"?

        If open source didn't give people more choices, would there really be any point to it?
  • by siddesu (698447) on Tuesday October 09 2007, @07:06PM (#20919563)
    i tried 1.6 some time ago -- mostly because i needed something access-like on Linux. the database app on the surface looks a lot better than the horror the ooo thingy, except that it didn't work with pre-existing sql databases. one has to create a database from scratch, and there wasn't an easy (UI) way to even hookup an existing database after one creates a custom one. since my needs were really simple, i gave up, and instead used knoda (http://www.knoda.org/) which is similar, and works nicely for the kind of thing I needed.

    the rest of the office implemenation seemed to almost work. of course, it wasn't completely compatible with OO, but i liked the interface better and would have used it if it had a useful PDF output. However the PDF i got out of it was really jagged (the letters jumping up and down around the line), and the opinion on the mailing list was at the time 'it isn't our problem', so I switched back to OO in the end.

    I hope 2.0 delivers. I'll give it a try anyway :)
    • by vandan (151516) on Tuesday October 09 2007, @07:57PM (#20920039) Homepage
      I've been working on my own Access-killer for a couple of years now. It's a suite of open-source, cross-platform Perl libraries, using Gtk2 for the GUI. The old website ( complete ) is at: http://entropy.homelinux.org/axis/ [homelinux.org]. I'm right now working on a revamped website ( incomplete, but with up-to-date download links and new screenshots ) is at: http://entropy.homelinux.org/axis_new/ [homelinux.org].

      There are 3 main components: a form object, a datasheet object, and a reporting module ( which exports to PDF via PDF::API2 ). I'm also working on a GUI object builder that exports XML for all 3 objects. Click on the 'future' link to see some screenshots of it in action. Note that I'm also looking for developers to help out, and maybe create a commercial project out of it ( I'm as-yet undecided whether to do this or not ).

      I've had a number of large, complex production systems built on these libraries in use for about 2 years now. Please try it out, comment, report bugs, help out ... :)
      • by Steauengeglase (512315) on Tuesday October 09 2007, @10:03PM (#20921395)
        "I've been working on my own Access-killer for a couple of years now."

        I think you are a little late to the party. Didn't Access commit suicide like 5 years ago?
            • Re: (Score:3, Informative)

              Perl's a natural fit for people who already know BASIC -- lots of $ all over, doesn't enforce any particular programming style, not particularly object oriented, etc.

          • Re: (Score:3, Insightful)

            On a personal note, I'm disappointed that it is written in Perl and the author thinks that Python has some "very strange ideas" such as "everything is an object" (OO languages aren't strange anymore). Makes me scared of what the code looks like underneath, but honestly, if it works and works WELL than I don't really care unless I have to dig in and change something. (o:

            WTF dude? This is the 2nd post that's complained about my attitude to OO languages, whereas I said nothing of the sort. I said that Pyth

  • I'm a Gnome user (after road-testing KDE for a good six months), but I've been infected with the hype about KDE 4, and in particular, Koffice. If it's really as good as they say, there's a good chance I'll switch over. My job uses Macs, and I've found NeoOffice too unstable to use (four crashes in two hours). Supposedly, there will be a Mac OS X-native version of Koffice, which would fit the bill to replace friggin' MS Office.

    My fallback -- and I'd just like to take this opportunity to veer off-topic, here -- is to put Ubuntu on a used CPU and run LTSP, with the Macs as thick clients. One way or another, I can't stand to see my office sink any more money into proprietary software.
  • There's still no "print selection" option in the printer gui interface. This leads me to believe that there will be more of the same gotchas littered all over koffice. Noble effort though. Keep up the good work.

    And while you are at it, please work on the print selection thingy sometime eh?
        • by rduke15 (721841) <rduke15@NospaM.gmail.com> on Tuesday October 09 2007, @09:19PM (#20920895)
          I actually knew someone who definitely needed "print selection". He had never heard of the concept of files, much less folders. He had ONE Word document on his Mac desktop, and only ever typed into that. Then he would select the part he needed and print that. I'm not kidding! Luckily, I was in a hurry and was able to refrain from getting into helping him. Anyway, he didn't want or need help. I have no idea how it ended, and whether eventually someone showed him the light. But maybe he wouldn't have been interested. It worked for him, with all his writings in a single huge Word file...
  • by Zombie Ryushu (803103) on Tuesday October 09 2007, @07:13PM (#20919635)
    Why is it that Kontact does not have KOffice integration and Kerberos support. Kontact+eGroupware would be an Exchange Killer IF Kontact and eGroupware supported Kerberos so that I don't have to setup kwallet with Domain login and passwords for remote Calendars/Tasks/Address Book with XML-RPC.

    Why no love of Kerberos!
  • Native Mac Version (Score:4, Informative)

    by javacowboy (222023) on Tuesday October 09 2007, @07:39PM (#20919883) Homepage
    KOffice 2.0 will run natively on OS X:

    http://apple.slashdot.org/article.pl?sid=04/01/02/1930232 [slashdot.org]

    This will benefit Mac users tremendously, as NeoOffice is too bloated (although making good progress at getting more efficient) and the native version of OpenOffice is probably several months away at best.

    There is no lean, simple free and/or open source spreadsheet app for Mac yet. When KOffice 2.0 comes out, cheap Mac users (like me) will have more choice. When MS Office 2007 comes out for Mac in January 2008 (sorry, had to poke fun at Microsoft :D ), and iWork 2008 out starting last month, Mac users willing to pay for a good office suite will have even more choice.

    This will also benefit the KDE team, as their installed based will expand by one (and possibly two) OS's, giving them more bug reports and feature requests.

    Everybody wins!
  • In 2009, I will ship my office suite, Stork Office. It will be fully open source, be even leaner than koffice, and not have the stupid Access-like tools. Then, if KDE isn't finished their 4.0 desktop, and fix the register view in KDevelop, I may just write my own GUI and IDE to go with it, for release in 2009. Oh, and I'll have Duke Nukem Forever as a game that ships with my system!
  • by C3ntaur (642283) <centaur@NOspAM.netmagic.net> on Tuesday October 09 2007, @10:01PM (#20921365) Journal
    I don't care what bells and whistles are added, what shiny new GUI paint is applied, how much faster the app runs, etc, etc, etc. Office 2007 is on the street, and we are going to be hit with a barrage of OOXML files that can't be opened by anybody who's not running Microsoft. Any contender in this space needs to address this problem, and right now.
          • Re: (Score:3, Informative)

            These projects are all odf converters, mostly MS Office plugins. They do not make it possible to open OOXML in anything other than MS Office.
    • by zsouthboy (1136757) on Tuesday October 09 2007, @06:58PM (#20919437)
      RTFA:
      KDE 4's framework is cross-platform.
      They plan to release this on Windows as well.
      • This is good news. I've been looking for a word processor with a good set of features without the bloat. I've been trying KOffice for a little while now, not quite used to it yet, but it is looking to take over, at least for myself. Reading on the features that will be available soon, I'm really looking forward to this release.
    • by japhmi (225606) on Tuesday October 09 2007, @06:59PM (#20919449)
      From the fine article, first paragraph.

      While the industry is distracted by the ongoing tussle between Microsoft and OpenOffice.org over document formats, the KDE project is quietly preparing the next generation of its own office suite, KOffice, for Linux, Windows, and Mac OS X
      • by Kjella (173770) on Tuesday October 09 2007, @08:37PM (#20920387) Homepage
        And just to expand on that, there are really several different things going on:
        1) Qt 4, the underlying system library is now dual licensed GPL/commercial on the Windows platform by Trolltech, before only commercial on Windows.
        2) As a result, the kdelibs (the core KDE libraries) for KDE4 has been made cross-platform. Like KDE4, they're still unreleased (at beta 2 still I think) but I did manage to get a KApplication compiled and running on Windows.
        3) Since the KDE libraries are going cross-platform, so is all KDE applications that doesn't have additional *nix-specific dependencies. Note that KDE is trying to be a complete application framework not just an UI library, so this should be true for most.
        4) Since the move from KDE3 to KDE4 is major, most applications like KOffice are also doing major rewrites not only because of the framework changes but also "if you want to change and break something, now's the time".

        End result? Well it's always though to say with unreleased software but the general idea is that it'll be a three-pronged attack:
        1. It's now cross-platform, so new markets
        2. All applications should see a 20-30% speed improvement because of library improvements
        3. Major new version with new features

        Only downside is that it's taking quite long - Qt 4.0 was released in June 2005, though in personal experience it was a poor release but none the less it's taken a few years and KDE4 is still in development. The release of KDE4 is scheduled for December 11th, and I'm very much looking forward to it. It should bring the Gnome vs KDE flamefest to new heights :D.
      • KOffice also opens MS docs and spreadsheets, and can save in .doc or .xls format. I don't know how well that is supported in terms of very elaborate stuff, but the docs and spreadsheets readily accessible to me here worked fine.
      • Re: (Score:3, Insightful)

        You're not kidding:

        sudo apt-get install koffice
        Password:
        Reading package lists... Done
        Building dependency tree
        Reading state information... Done
        The following extra packages will be installed:
        karbon kchart kdelibs-data kdelibs4c2a kexi kformula kivio kivio-data
        koffice-data koffice-libs koshell kplato kpresenter kpresenter-data krita
        krita-data kspread kthesaurus kugar kword kword-data libarts1c2a
        libavahi-qt3-1 libopenexr2c2a libpoppler1 libpoppler1-gli
        • by Bogtha (906264) on Tuesday October 09 2007, @09:30PM (#20920995)

          A lot of those packages are simply the individual applications and their supporting data. Once you ignore those, the required supporting packages are simply:

          • kdelibs-data, kdelibs4c2a, libarts1c2a - the KDE libraries and sound daemon.
          • libavahi-qt3-1 - support library for Rendevous/Bonjour/whatever it's called these days that makes network service autodiscovery work.
          • libopenexr2c2a - support library for the EXR image format.
          • libpoppler1, libpoppler1-glib, libpoppler1-qt - support library for PDFs.
          • libruby1.8 - support library for scripting.
          • libwv2-1c2 - support library for Word document format.

          The rest of the packages are optional. Furthermore, if you only want a couple of the applications, e.g. KWord, you can install them individually. And of course, on a KDE desktop, you'll already have much of this installed anyway. Considering the size of things like OpenOffice and Microsoft Office, I'd say that's not too bad.

            • by Bogtha (906264) on Tuesday October 09 2007, @09:59PM (#20921341)

              What do you need a sound daemon for an office package for?

              That should be optional. Same with the network discovery crap.

              Blame your distribution. They are optional. Whoever packaged it for your distribution decided that they should be required. I have KOffice installed, and I haven't got all of those packages installed.

        • Re: (Score:3, Interesting)

          That list of deps (installing Koffice on a Gnome based system) is about the same size as installing only Gnumeric (which is largely Gnome based) on a simple KDE based system.

          Hard drive space is cheap.
      • Re: (Score:3, Insightful)

        The difference lies in the Qt4 licensing versus Qt3.
        Qt3 was available with a GPL license only for X11, so the previous effort to port KDE to windows had to reimplement a GPL version of Qt for win32 from scratch, which is quite a big undertaking.

        Qt4 is available under the GPL for every platform, so that big roadblock is cleared. And the KDE project is officially supporting and ecouraging the win32 port this time.
        Also, some other things like KDE switching to a much nicer and cross platform build system than a
        • Re: (Score:3, Interesting)

          15 seconds? My 4 year old laptop running gusty can get a cold start on OOo in about 5 seconds. Subsequent startups take about 2-3 seconds. Of course this is still an eternity compared to the near-instant starts of MS Office though.
      • Re: (Score:3, Informative)

        I use access all the time when people send me CSV files that have more than 65,000 rows in them, and therefore won't open in most spreadsheets. It's nice for one-time-use databases or just doing simple queries on csv files that clients have sent you. I wouldn't use it for any kind of permanent database, but that's usually how access applications get started, Somebody needs a quick and dirty database to use for a week to analyze some data, and 3 years later, it's still running, because somebody thought it
      • Access (Score:3, Informative)

        I can't think of a single good reason to use Access (or Access-like databases). Can somebody tell me what sort of applications would actually call for a wretchedly limited application like that?

        I cannot quite understand how you cannot see what Access is used for. When you need a databse application with a GUI, what do you build the GUI with? HTML? That's fine for many tings, as the web demonstrates. But for a real desktop GUI application, what do you suggest instead of Access? Perl/Tk? C++? Visual Basic?

        Des

        • Re: (Score:3, Informative)

          Try my project as as Access replacement:

          http://entropy.homelinux.org/ [homelinux.org]. I'm also working on a new website ( with updated screenshots and also snapshots of the libraries ), at: http://entropy.homelinux.org/axis_new [homelinux.org].

          It's written in Perl, and uses Gtk2 for the GUI. It's open-source and cross-platform, and soon will get a GUI object builder ( click the 'future' link for some screenshots ).
      • Re: (Score:3, Interesting)

        Anyways, I have a question. I can't think of a single good reason to use Access (or Access-like databases). Can somebody tell me what sort of applications would actually call for a wretchedly limited application like that?

        Access *is* truly wretched as far as an actual DB backend. The early versions of MySQL were far more powerful and fast, for example. But the real killer feature of Access is the ability to create tables and interfaces to them graphically. It's actually very good at that, and I haven't seen a decent replacement for Linux. A non-technical person can sit down with Access and make, say, a database of their recipes, or book collection, or company purchase orders... and make a decent GUI to do CRUD on it.

        For

    • by Pr0xY (526811) on Tuesday October 09 2007, @08:17PM (#20920203) Homepage
      While I can't speak volumes about Gnome and GTK. I can say that you views of KDE and QT do not appear to be based on facts, but more assumptions and preconceived notions.

      KDE is NOT simply QT plus bloat, the goals of the KDE library are to provide a consistent API to applications to work well with the KDE desktop. In the grand scheme of things it is actually very light as far as things it adds to QTs very complete API. For example, it will provide a KPushButton which inherits from the QPushButton class to add a few small integration features. Also KDE offers many common widget combinations as a reusable widget in itself, this is good library design as a whole. Making libraries of reusable code is a GOOD THING.

      Don't mis-interpret this as KDE zealotry, I imagine that Gnome provides some sort of API to help applications integrate well with the desktop as well.

      And what is your general issue with using c++ and moc? I hate to break it to you, but moc IS "real c++". There is nothing wrong with having utilities to generate code, there is huge gain to doing it with moc instead of templates...runtime bindings. moc just hides these details for you, and to be honest, you usually don't even have to worry about it at all if you use the QT build system.

      As for what is wrong with GTK + C? Well nothing is wrong with it but it's not the only choice. One thing to keep in mind though is that graphical displays usually consist of conceptual objects "windows", "buttons", "listboxes", "textboxes", etc. These are all "things" which to be honest, creating code to describe "things" is what object oriented programming excels at.

      You will never see a port to GTK of KOffice because it would not be a port, but a litteral re-write as the whole code base is built around the KDE/QT libraries.

      And why not start with AbiWord? Heh, this statement is a shinning example of a preference not based on the merits of what you want, but instead on an arbitrary dislike for the competition. You are of course entitled to your opinion, nothing is perfect. But you provide no real reason why something built on KDE libraries is inherently bad. Secondly, Abiword is a single word processor application with no integration into an "office solution". KOffice is looking to provide the whole shebang.

      I imagine you are going to reply with "KDE is bloated", "KDE is slow". But these generalizations aren't really based on real facts. KDE is actually quite lean (and KDE 4.0 is going to be leaner because QT 4.0 is a vast improvement of 3.0). Its memory usage is nothing crazy, the reason for this is that there is a LOT of code reuse. Using the KDE libraries is effectively "free" as far as memory usage goes because modern operating systems do code sharing of dynamic libraries and the whole damn desktop uses these libraries! There are benchmarks that show that Gnome and KDE are actually quite comparable: http://ktown.kde.org/~seli/memory/desktop_benchmark.html [kde.org]

      I'll even not go so far as to say KDE is better than Gnome in memory usage because I know that there are many factors and a single set of benchmarks by one person doesn't really prove much...but it does show that they are at least in the same ballpark.

      All in all, I find your argument against using a modern library not founded in facts :(

      proxy
        • by Pr0xY (526811) on Wednesday October 10 2007, @12:08AM (#20922613) Homepage
          surely, in fact, the linux kernel uses object oriented programming in things like the VFS layer. The thing is, doing OOP in C is no more efficient than C++, it really is just a matter of syntax. And if you have a language which gives you OOP and is generally efficient..then why not use it.

          It's just another tool in the toolbox, i like using many languages and it's just a matter of choosing the right tool for the job.

      • Re: (Score:3, Informative)

        What about a Vector graphic editing tool?

        That would be Karbon14 [koffice.org]. (KDE seems to have gone through a few iterations of vector graphic tools, or maybe the same tool under different names. I know KIllustrator was renamed because of pressure from Adobe, to Kontour. And there was a Krayon in there too. I don't know how many of these may actually have been different codebases.)