Announcement

Collapse
No announcement yet.

KDE's KOffice Forks Internally As The Calligra Suite

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • KDE's KOffice Forks Internally As The Calligra Suite

    Phoronix: KDE's KOffice Forks Internally As The Calligra Suite

    The KDE community has announced the formation of the Calligra Suite, as a "continuation of the KOffice project" to reflect the larger KOffice package rather than just being an office and productivity suite. Calligra is meant to breath new life into the contained KDE programs after an unresolvable dispute by KOffice developers...

    http://www.phoronix.com/vr.php?view=ODg4NQ

  • #2
    typo:

    Aaron Siego -> Aaron Seigo

    Comment


    • #3
      Um... you said that Stage is replacing kpresenter, and Flow is replacing kpresenter. I think only Stage is replacing kpresenter, and Flow replaces Kivio

      Comment


      • #4
        They shouldn't even have to create a custom renderer. Write the whole implementation as an XSLT which generates SVG from ODF - then the display of the document is just a webkit kpart. Is there anything you can do in ODF that would be difficult to generate an SVG representation of for display? I know you can get from LaTeX to SVG pretty easily. Lilypond generates ps or pdf too and they recently modified it to generate SVG directly.

        Comment


        • #5
          Calligra isn't going to compete with much of anything if it maintains its dependance on KDE libraries. Unless it can isolate those dependencies to a kde integration plugin or library, we can't port koffice anyware and have it stick.

          Comment


          • #6
            Originally posted by Smorg View Post
            Write the whole implementation as an XSLT which generates SVG from ODF
            Yeah, that's going to have really great performance, especially on a mobile phone.

            Not to mention that a XSLT has to process the whole document, loading that 100 page document may take a while. Rendering the resulting .svg to a 100-page bitmap may be a bit taxing on your memory resources, too.

            I'm also curious how you're going to implement intra-document links and the ability to copy/paste once everything has been transformed to svg.

            Lastly, XSLT is a horrible language to write code in, writing a custom renderer is probably less work and way better for the sanity of everyone involved.

            Comment


            • #7
              monkey see, monkey try to do and fail.

              they saw libreoffice, and they are trying to copy. sadly koffice should just start from scratch. the current suite is a mess.

              Comment


              • #8
                Originally posted by dacresbu View Post
                Calligra isn't going to compete with much of anything if it maintains its dependance on KDE libraries. Unless it can isolate those dependencies to a kde integration plugin or library, we can't port koffice anyware and have it stick.
                What's the problem with installing kdelibs, if it all installs together and simple I think it would be no problem,
                after all I think openoffice and msword are both bigger than kdelibs + koffice.
                The main difference its that it feels dirty because libs are all across the system but it should be possible to put everything into a folder.

                Comment


                • #9
                  Originally posted by rolandixor View Post
                  monkey see, monkey try to do and fail.

                  they saw libreoffice, and they are trying to copy. sadly koffice should just start from scratch. the current suite is a mess.
                  Erm, no. If you read the article (and the mailing lists where the decisions were actually made) you'd know this was in response to a conflict of interests among certain people. Long story short, the developers wanted to move AWAY from being a simple MS Office/OpenOffice/LibreOffice clone and a certain dickish maintainer didn't want this. So they forked the project and took the opportunity to create a new brand to reflect not only a new direction, but the fact that some applications (such as Krita, a painting application) simply didn't fall under the "office productivity suite" label.

                  Comment


                  • #10
                    At least it's not called Kalligra. Thank the gods.

                    Comment


                    • #11
                      Originally posted by rolandixor View Post
                      monkey see, monkey try to do and fail.

                      they saw libreoffice, and they are trying to copy. sadly koffice should just start from scratch. the current suite is a mess.
                      all the office projects should be scratched and people should concentrate on how to make OOo/Libre integrate the best with their desktop and adapt this for the corner cases

                      FFS we don't need a million office applications

                      Comment


                      • #12
                        KOffice predates OpenOffice (maybe not Star Office). It quite refreshingly isn't trying to be a clone of MS Office. Unfortunately it really doesn't have the level of polish that it should and has been somewhat in the wilderness with the 2.0+ versions. Calligra is more or less the same code-base under a new name.

                        The other practical advantage is that having a seperate code base helps test OpenOffice adherance to the ODF specifications.

                        Comment


                        • #13
                          Originally posted by dacresbu View Post
                          Calligra isn't going to compete with much of anything if it maintains its dependance on KDE libraries. Unless it can isolate those dependencies to a kde integration plugin or library, we can't port koffice anyware and have it stick.
                          This doesn't make any sense.

                          KDE libraries provide lots of important functionality. Should they rewrite all of this just so they can claim they are not using KDE?

                          The dependence on KDE is exactly a library dependence. It links against kdelibs (which has been ported to most relevant architectures) and that's it. You don't need KDE to run any of it, just kdelibs.

                          Comment


                          • #14
                            This might actually be a good thing for KOffice.

                            If I understand correctly, this will further focus the development on small devices (palmtops, tablets, netbooks), which is a market niche. Competing with LibreOffice on the desktop has not been very successful due to a lack of developers, and LibreOffice provides both GTK and Qt frontends nowadays and has GNOME and KDE integration and lots of corporate backing.

                            But putting out a good cross-platform, standards-compliant office suite (it uses ODF as its native format) which can run without being resource-hungry (5433 terrabytes of RAM + Java runtime + 2 gigabytes of source code, yes LibreOffice, I'm looking at you!) -- this is a really good idea.

                            Nokia has put in a lot of work into MS Office compatibility recently, mostly because they wanted a reader for Maemo. With very little work, KOffice/Calligra could become a very important player in this market, without having to compete head-to-head with LibreOffice on the desktop.

                            And since both suites use ODF, they can interoperate.

                            Comment


                            • #15
                              Originally posted by pingufunkybeat View Post
                              You don't need KDE to run any of it, just kdelibs.
                              For sure? If I select koffice on my pure Gnome Ubuntu, it pulls in a heck of a lot (117 to be exact) of packages. Most likely not all of them will be strictly needed, but I bet at least the core ones will have to be there:

                              kdebase-*, kdegraphics-libs, maybe kdepim-*, ...?

                              If I just select kwrite, aptitude will still want to install 58 packages...

                              Comment

                              Working...
                              X