Notice that koffice is also in git and progressing nicely; kword is much more stable there for instance.
Just be sure to compile the koffice-plugins too so you can things like spell checking.

Sorry, I used B in place of A in a couple places.

zander wrote:Notice that koffice is also in git and progressing nicely; kword is much more stable there for instance.
Just be sure to compile the koffice-plugins too so you can things like spell checking.

Koffice-Calligra, or Koffice-other?

KOffice (Group A)

airdrik wrote:

zander wrote:Notice that koffice is also in git and progressing nicely; kword is much more stable there for instance.
Just be sure to compile the koffice-plugins too so you can things like spell checking.

Koffice-Calligra, or Koffice-other?

I meant Group A, which continues to be called koffice for now; see https://projects.kde.org/projects/koffice

So, anything going on in the KOffice camp?

There are still commits in GIT, but it is unclear how major they are. I have not seen any announcements anywhere about either the progress or future timelines.

Calligra Suite will just be the KOffice 2.4 release. Another name, same suite.

computergeoffrey wrote:Calligra Suite will just be the KOffice 2.4 release. Another name, same suite.

Yes, this is well known

But the talks were that KOffice will remain active too, so I wonder have they really.

atrox wrote:But the talks were that KOffice will remain active too, so I wonder have they really.

It is certainly active, in that the git tree is getting commits. How much real-world progress is being made is unclear to me, however. There don't appear to be many people making commits, essentially all of them are from Thomas Zander and Dr. Robert Marmorstein, with Thomas Zander making pretty much all the significant commits in the last 4 months. There are also no tags or other clear indications of an impending release.

It would be nice to get an update straight from the developers. The calligra developers have been fairly public about their progress and plans, in blog posts, commit digests, and interaction with the general press, and are nearing a 2.4 release. The KOffice developers have not been vocal, with the last significant thing I saw being fairly vague general goals for the suite from Thomas, and that was almost a year ago.

koffice not only reminds me on "officium", but "coffee" too. that's why I miss kexi in the cmakelist of koffice, because as an austrian I associate "kexi" with "biscuit". a perfect combination. But the akonadi/virtuoso-backend could be the chocolate pieces within.
Anyone working on virtuoso-odbc-backend for kexi?

please redirect me if you want - kmypersonal goals are:

virtuoso -> akonadi (additional storage backend if possible)
virtuoso -> kexi (additional storage backend if possible; add Visual-SPARQL-Builder)
virtuoso -> kdissert (view/add semantic meta-data, edit relations through NEPOMUK/Soprano)
virtuoso -> kword/kcell/kile (shared tool to map query results into OpenDocument/TeX-Templates)
koffice <- kile/kbibtex/kmymoney/kdissert (they could have a good home in koffice)
kontact <- kplato (let kplato act within kontact-chorus)
koffice <-> kontact = kjots (establish a bridge for mapping query results into OpenDocument/TeX-Templates)
kad <- freeCAD (bring kde aided design back to life with OpenCascade)
virtuoso/rdf/ifc -> kad (virtuoso as building information modelling backend)
kraphite <- krita/karbon/kad (let them be good team as kraphite)

than finally it would be the perfect trinity for me:
kontact - kraphite - koffice

Still anyone reading?
Essentially splittng for good is not kool,
but kstructuring may be.

If KDE 5 changes structurally,
I hope the community feels
that the number 5 is strong and alive,
and finally K should stand for Kool!

And... where are the extraordinary straight koffice-icons gone?
What do you folks think?

dkummer wrote:koffice not only reminds me on "officium", but "coffee" too. that's why I miss kexi in the cmakelist of koffice, because as an austrian I associate "kexi" with "biscuit". a perfect combination. But the akonadi/virtuoso-backend could be the chocolate pieces within.
Anyone working on virtuoso-odbc-backend for kexi?

please redirect me if you want - kmypersonal goals are
[..]

Hi, these are very good ideas. Since you asked, you can find Kexi forums for help and discussion at kexi and Calligra forums at http://forum.kde.org/calligra.

I propose to start new threads, re-posting ideas to continue discusion. Since the days when this thread started Calligra released 2.4, 2.5 and 2.6 is almost there. And we're working on 2.7 now!

PS: Things like akonadi/kdepim integration are among the TODOs of Kexi hackers. When it's released depends on initiative of interested parties, That's you!. By the way, Akonadi is a data cache, the integration would be using it but would be also closely related to KDEPIM.

jstaniek wrote:

dkummer wrote:koffice not only reminds me on "officium", but "coffee" too. that's why I miss kexi in the cmakelist of koffice, because as an austrian I associate "kexi" with "biscuit". a perfect combination. But the akonadi/virtuoso-backend could be the chocolate pieces within.
Anyone working on virtuoso-odbc-backend for kexi?

please redirect me if you want - kmypersonal goals are
[..]

Hi, these are very good ideas. Since you asked, you can find Kexi forums for help and discussion at kexi and Calligra forums at http://forum.kde.org/calligra.

I propose to start new threads, re-posting ideas to continue discusion. Since the days when this thread started Calligra released 2.4, 2.5 and 2.6 is almost there. And we're working on 2.7 now!

PS: Things like akonadi/kdepim integration are among the TODOs of Kexi hackers. When it's released depends on initiative of interested parties, That's you!. By the way, Akonadi is a data cache, the integration would be using it but would be also closely related to KDEPIM.

Thank you! My self-esteem in C++ is very low yet, but I'll do my best and follow your links!

This was two years ago...

scummos wrote:This was two years ago...

If you look closer, amberschwartz is a spammer...