Key KOffice Developers Talk About KOffice 2 and Open Standards
KOfficeSource: a KOffice Consultancy Company
The password to join has been made visible. See the top menu under 'members' for the page link. To forestall joining by bots, the procedure has been left a little complicated but is not difficult.
Português
Bem-Vindo aos usuários do KOffice
wikidot handbook being translated to Portuguese
Português handbook begun
introduction
new KOffice and new QT means new features
This is for users of KOffice which is emerging as one of the primary choices as office software. Initially, it contains a wiki, a forum, some links and feeds from the KOffice news page and KOffice mailing list.
The forum is now open for posting by non-members. If that becomes a problem, the initial setting (only the Guest Book and Page Discussions were open for posting by non-members) may have to be reinstated.
Non-members may create new Wiki pages and edit pages they have created.
Google tuxmachines for KOffice - (100 per page)
Raiden's Realm has a synopsis of KOffice applications, an article on screen-shot captures, a summary of complementary graphics tools and another of complementary development applications.
The following KOffice applications are mentioned favourably in an IT Management article:
Kexi - KOffice database
KPresenter - KOffice presentation
Krita - KOffice image editor compared favourably with The Gimp
KSpread - KOffice spreadsheet
KWord - KOffice word processor
Cross platform KOffice to challenge OpenOffice.org Rodney Gedda on computerworld.com
a summary on lxer.com You need to log in to the site to read the full story
a discussion by KOffice developers
interview with Mark Shuttleworth | ogg version
Review of kWord by Carla Schroder December 6, 2007
A quotation from this page :
There are two ways of constructing a software design: one way is to make it so simple that there are obviously no deficiencies; the other is to make it so complicated that there are no obvious deficiencies. — C. A. R. Hoare
contributing to KOffice
support KOffice
ways to get involved
chapters
community
community building
site design
support sites on the links page
create your own pages members may create pages over which they have exclusive authoring rights
extras
international
advanced processes
scripting with Python
compiling and developing
* comments
Comments are enabled on this page. If you do not have permission to use this feature or prefer a forum discussion, there is also a 'discuss' button in the options at the foot of the page for automatic posting to the "page discussions" category in the forum.
If you cannot see the 'discuss' button, post in the forum by using the top menu Forum > Page discussions. view this insert
KOffice news
Official mailing list archives
Re: KPresenter in UserBase
1257246600|%e %b %Y, %H:%M %Z|agohover
Re: KPresenter in UserBase
1257227760|%e %b %Y, %H:%M %Z|agohover
KPresenter in UserBase
1257061920|%e %b %Y, %H:%M %Z|agohover
Re: RTL documents in Koffice
1253611800|%e %b %Y, %H:%M %Z|agohover
Re: RTL documents in Koffice
1253596440|%e %b %Y, %H:%M %Z|agohover
Formulae in Kword
1253400600|%e %b %Y, %H:%M %Z|agohover
Re: RTL documents in Koffice
1253362020|%e %b %Y, %H:%M %Z|agohover
Re: RTL documents in Koffice
1253356380|%e %b %Y, %H:%M %Z|agohover
Re: RTL documents in Koffice
1253354460|%e %b %Y, %H:%M %Z|agohover
Re: RTL documents in Koffice
1253352840|%e %b %Y, %H:%M %Z|agohover
RTL documents in Koffice
1253350380|%e %b %Y, %H:%M %Z|agohover
Office viewer for Maemo5 based on KOffice
1253167620|%e %b %Y, %H:%M %Z|agohover
2.1 b2
1253037240|%e %b %Y, %H:%M %Z|agohover
Re: problem and motivations
1253020440|%e %b %Y, %H:%M %Z|agohover
Re: problem and motivations
1253019720|%e %b %Y, %H:%M %Z|agohover
problem and motivations
1253018940|%e %b %Y, %H:%M %Z|agohover
Re: Fwd: Re: How to view .kpr files ?
1252979460|%e %b %Y, %H:%M %Z|agohover
Fwd: Re: How to view .kpr files ?
1252978740|%e %b %Y, %H:%M %Z|agohover
koffice.org/download added
1252734660|%e %b %Y, %H:%M %Z|agohover
Re: Can't run kword on openSUSE 11.1 x64
1252451280|%e %b %Y, %H:%M %Z|agohover
Can't run kword on openSUSE 11.1 x64
1252377600|%e %b %Y, %H:%M %Z|agohover
Questions about the KOffice version control and bug tracking systems
1250543640|%e %b %Y, %H:%M %Z|agohover
Re: Koffice download for windows
1249804080|%e %b %Y, %H:%M %Z|agohover
Fwd: Koffice download for windows
1249780020|%e %b %Y, %H:%M %Z|agohover
Many users of KOffice no doubt use the Kde desktop. The following is a recent article by Bruce Byfield: 12 Tips for KDE Users
OpenChange 0.9 - coming soon
1259229376|%e %b %Y, %H:%M %Z|agohover
Not really a KDE related post, but instead one about the OpenChange project.
OpenChange is a project to implement the Microsoft Exchange / Outlook protocols, and we're creeping up on the 0.9 release. For those not familiar with it, the aim is to be wire-level compatible, so that you can use a FOSS client (such as Evolution or an Akonadi client) with an unmodified Exchange server.
OpenChange depends on some underlying Samba4 libraries, so we normally work with the Samba project to get releases that basically match up - we don't want to rely on building bits of Samba4 from the git repository, and we don't want to depend on really on versions of Samba4. Not too far ahead, and not too far behind. Just right...
The next release of Openchange (0.9 "COCHRANE") will rely on Samba 4 alpha9. So the main thing to do is to make sure that we can work with the current state of Samba 4, to provide patches to Samba for stuff that needs to be fixed on the Samba side, and to have changes for OpenChange ready to go.
We expect to release within two weeks of Samba 4 alpha9, but OpenChange 0.9 will be released when it is considered done.
We anticipate a 0.10 release in early 2010, and probably a subsequent 0.11 release prior to 1.0.
I've gone through the trac tickets, and moved anything that can't reasonably be achieved for 0.9 to a 0.10 milestone. Large changes have to wait for 0.10 - it is getting very late to risk destablising libmapi.
So what we still have left:
- integrate exchange2ical work from Ryan Lepinski into trunk
- ensure that OpenChange works with FreeBSD/OpenBSD
- ensure that OpenChange works with OpenSolaris
- libmapi/Samba4 API updates
- mapiproxy/Samba4 API updates and association group API evolution
- a couple of tickets that may not be too hard to fix, related to pkg-config support
- a ticket related to Free / Busy time support that has a crash.
- a patch that checks some return values that we current don't handle.
- some documentation stuff.
Details are on http://trac.openchange.org.
Known problems:
- openchange development server will not be working "as it is". Resolving this requires revision of the OpenChange schema updates (to match Samba4 changes). This may not be resolved for 0.9.
If I've dropped a patch, or there is something you really need for 0.9, now is your chance to make yourself known. Probability of a patch being applied is inversely proportional to complexity, and also inversely proportional to how close I think the release is. That is, simple and soon is good.
KDE Licensing Policy Changes
1258668092|%e %b %Y, %H:%M %Z|agohover
Today I updated the KDE Licensing Policy with a couple of changes following requests from folks. Most notably Creative Commons is now allowed. This is only for standalone media files (such as an image for a splash screen) and not for anything which might want to be mixed with GPL material such as icons. "Attribution-Share Alike 3.0 Unported" is the version allowed. The other change is requiring BSD licencing for CMake modules, which brings the policy into line with existing practice.
How are you? Kubuntu in Dallas
1258657570|%e %b %Y, %H:%M %Z|agohover
The Ubuntu Developer Summit is happening this week in Dallas. The theme of the discussions is LTS and what it will take to have a release in six months which can be supported for three years hence. We've been having sessions on packaging, development, bugs policy, translations and more. You can find the schedule and how to take part in sessions on the summit website, there are icecast streams for all the rooms. The Kubuntu specs are on this wiki page still works in progress of course. It's going to be great to have a KDE 4 release suitable for LTS, just six months to do it!
Some of the Kubuntu Team take to the ice rink
Fixes, features
1258235139|%e %b %Y, %H:%M %Z|agohover
Many small fixes are a building block of the Kexi porting effort - the goal is joining the KOffice 2.2. Many of the fixes and refactoring is related to forms. Much more left and we're scheduling works on crazy features even up to Kexi 2.6 already.
The next is porting task, I hope, is the table view port to QScrollArea from QScrollView, what's rather demanding task to me at least since while the table view can be called widget itself, it is the biggest one (# of SLOC) of those I have touched directly so far in KDE (at least it bundles a dedicated model/view framework developed long before the first announcement of Qt4 Model View API).
Sometimes one needs to add some procrastination, and this time I added an indicator/emblem-like icon to forms so you can easily notice that what widgets are bound to data source (and to which).
Kexi Forms: Data source emblems for data-aware widgets; click to enlarge
Other small improvement that you can find in above screenshot is frame-around-labels in the design view. Before that, we had to live with borderless labels, like in Designer. As Kexi generally lowers barriers for new users, we display the frame more like in case of a text frame in a word processor.
In related news, I am also excited that Nuno has admitted that one of the forthcoming items on his list are Oxygen icons specific to Kexi.
Speaking of procrastination, we (me and Nuno and Hugo Pereira) just yesterday had a small session of three graphics-loving guys regarding some bits of Oxygen style. Two outcomes of that are:
1. Idea for cleaning up vertical lines for the case when docks+tabwidget+splitter+another frame is used in an application. This is the case for Kexi as well everywhere in KOffice and most complex apps featuring sidebars. I bet the idea is not new and the improvement is pretty much demanded. Two proposals (less and more extreme):
(compare these improvements with the current look presented earlier.
2. Exclusive QGroupButton styling for Oxygen; my early proposals, need fixes but the 3rd is somewhat acceptable. The mockups use Kexi's view switchers as a base.
On the technical side, I think the look can be either set default or can be supported via K* overload of QGroupButton or addition to KStyle or by setting a Qt4's dynamic property (so developer can decide to alter the look only for some group buttons). Whatever we recommend, it could find its way to the HIGs first.
There's also one note that we agree on, that since the Oxygen now employs fade in-out when you switch between tabs in QTabWidget, this effect should be measured and switched off when there are too many delays. The goal is not only to support slower machines or conserve power but also cases when there are large Konqueror's (or Kexi's, which is indeed my test case) tab areas much harder to fade in-out than small ones. So there could be some logic employed depending on the size of the tab widget.
mos def
1258228043|%e %b %Y, %H:%M %Z|agohover
Given the pile of awesome that was Camp KDE 2009 in Negril, Jamaica, how could I not attend this year as well? I'll be presenting and doing some Qt training sessions again, like last year, on whatever topic the audience wants. There'll be sun, there'll be hackery, there'll be merriment. You must not miss this, so make sure to sign up now and meet us in Sand Diego in January.
In which the author introduces himself
1258091260|%e %b %Y, %H:%M %Z|agohover
Hi there. In order to keep the tradition, an introduction in this first post. I'm Raphael Kubo da Costa, a 20-year-old Computer Science student at State University of Campinas, Brazil, and also part-time employee at ProFUSION Embedded Systems (a very nice place for any free software developer, I'd say).
My first contact with KDE as a developer was in 2006 when I sent two small patches for Konversation. Curiously and frustratingly enough, when I started university in 2007 I found myself with much less time to dedicate to my own free software interests than before -- even though I did to go to the International Free Software Forum that year and happened to be one of those "new and interested developers" to whom aseigo showed off the soon-to-be KDE4.0 desktop on the exhibition floor. 
Since the beginning of this year I've been contributing to KDE in a few different fronts: I do some occasional bug triaging and commits to kdelibs, but most of my KDE time is spent maintaining Ark, our old and beloved file archiver, with Harald and helping the KDE-FreeBSD team (I'm not a full-time FreeBSD user, although I'm writing this post directly from FreeBSD 8.0-RC3). So expect me to write more about these activities in the future.
Now let's try to make this post a little less "hello planet-ish" and talk about Ark, KDE's file archiver which lives in kdeutils. I believe it's one of the longest-living programs in KDE (the first commit shown by svn log is revision 12097, which was actually a CVS commit and dates back to the end of 1998). It has survived our four major releases and has had quite a few different maintainers (curiously enough again, most of them were Brazilian).
So what's the state of Ark today? As I write this post, Ark's bug count in Bugzilla is at 72, which I consider a small number to be honest. However, we have been mostly in bug fixing mode for at least a few months, and some bugs need pretty big changes in code to be properly fixed. Being a university student, working (even when it involves using Qt) and also having a life means I don't have that much time for big changes at the moment, and neither does Harald, who's also losing his hair to graduate from university.
I don't want to end this post in a negative mood, though. So my dear reader, you have been watching the KDE "scene" for some time, you would like to contribute and you don't know where to start. Well, Ark needs you! Despite its age, Ark has a small code base, and both Harald and I are (presumably) nice guys and we are more than willing to help you. And you, my dear reader who already contributes to KDE, how about doing something completely different? 
openSUSE 11.2 is out. And a couple of KDE release notes.
1258044060|%e %b %Y, %H:%M %Z|agohover
Oh, yes, just in case you haven't noticed, it's out. However, since I maintain this image of seriousness, purposefulness and so on (which I only occassionally spoil by something like doing strange things to my hair, eating way too much icecream or doing silly things at SUSE outdoor events), I would like here to reference the KDE release notes for openSUSE 11.2. We recalled at least the Pulse Audio thing a bit too late, so maybe right now the actual release notes do not mention it yet.
Default Web Browser - yes, we default to Firefox with KDE integration, see the notes for switching back. Nothing more to say here, if you still don't know about this, you apparently don't know about KDE and openSUSE (in which case you're kindly asked to fix that ).
KDE3 - boy, I'm getting really tired of this topic 
. It's really simple: Apparently there is nobody caring about KDE3 enough to do something about it. So, if you are in the minority that still doesn't find KDE4.3 good enough as a replacement, either just stick with an older release, or try to use the unsupported KDE:KDE3 repository, which right now looks like it still builds, but may not anymore tomorrow if anything changes, since, as I said, everybody feels like having more important things to do than spent time on it (really, we tried to find people who'd be interested in it, but apparently all people capable of doing so already work on KDE4 or are too busy complaining on mailing lists). So, just get over it. KDE3 is dead. It is no more. It has ceased to be. It has expired. It is an ex-KDE3. (Thinking of it, I will skip that is has gone on to meet its maker, just in case).
Strigi/Nepomuk - they are disabled by default. With Beagle not enabled by default being asked a lot for, and generally considering the situation, we decided this would be a better option (and upstream wasn't really against). Those who want them enabled can easily do so in systemsettings. Well, almost - unfortunately a problem slipped in that prevents starting Strigi in default installations. See comment #6 in the #548007 bugreport for an easy fix.
PulseAudio - since KDE not only does not have a hard dependency on PA but also there is basically no integration of PA, having PA with KDE doesn't buy anything to most users, so we decided to disable it by default in KDE installs. This is not the broken PA that was in 11.1, but still, why force it unnecessarily. Those that have a use for PA need to enable it in the YaST Sound module (note that this includes everything running on a system that has KDE as the default desktop).
Now, onto the goodies!
Linux Desktop Ready for the Users
1257938845|%e %b %Y, %H:%M %Z|agohover
I often say that my hypothetical user for Kubuntu is my non-technical girlfriend. Unfortunately I'm between girlfriends at the moment but the intent is still there. Someone who uses the computer for everyday tasks of web browsing, chatting, watching videos, listening to music, writing some documents, storing photos. But also someone who doesn't care about computers any more than I care about my car, it should do the job but I don't want to have to fiddle with it to get it to work. Unfortunately I rarely get the chance to try out Kubuntu on such users, my family have all been using computers far longer than I have and are just as stuck in their ways as I am in mine.
But yesterday I did get a chance to install Kubuntu on a dying WIndows machine. The worst part of the process was booting up Windows to see how much disk space there was, it took 20 minutes to boot up loading all the half broken vendor apps and anti-virus software. Then it took 20 minutes just to shut down, every 30 seconds interrupted by a "missing .dll" or similar dialogue.
So up boots Kubuntu from the CD in half the time than Windows boots from hard disk. All hardware working perfectly. The disk partition resizing is a breeze, installation works without problems.
We came across two small problems. Knetworkmanager doesn't give much feedback if you use the wrong wifi encryption or password method, and the Firefox installer claims it has nothing to do if you don't have an apt cache first. Both known issues which I expect will be fixed before long.
So far one very happy customer, off to browsing the web in 1 minute beats Windows by a factor of 20. But that is just the install. I'll find out in the coming days how someone who doesn't care about computers manages with the everyday tasks that we all expect to work easily.
Firefox KDE Integration
1257283706|%e %b %Y, %H:%M %Z|agohover
Now that the mention of the Firefox KDE integration I've done has reached also the dot, I guess it's time for a couple of things that don't quite fit into an article but I should probably say them somewhere anyway.
First of all, this is nothing against Konqueror. I still use Konqueror. In fact when a couple of months back there was a wave of "let's ditch Konqueror" voices on the planet and kde-core-devel, I was one of the people opposing that (and I still think it's not an option, as Konqueror is still the best KDE browser there is - Aurora is Qt-only, Rekonq is at version 0.<somesmallnumber>). For the next openSUSE release we will evaluate the possibilities again and Konqy may end up as the default again if it's considered to be up to the job. Speaking of which, Konqueror has never really been 100% default in openSUSE, as the desktop icon, which is what the common user uses, has always been Firefox, so we can also say the we just fixed the inconsistency (and it's really simple to switch it back). But the real reason was that many people are simply not satisfied with Konqueror, so we decided to try to not ignore the reality for a change. I myself use Konqueror, but if somebody else wants to browse the net on my home machine, they get Firefox. I don't like this, but what the hell, c'est la vie.
So, when we decided to make Firefox the default, we also faced the problem that we switched to something that from KDE user's point of view sucked in pretty much all aspects except for the browsing itself. The idea of Firefox desktop integration on Unix ranges from not bothering with it at all, over using generic not-really-desktop stuff like mailcap, to thinking Unix==GNOME. Normal Firefox in KDE offers to open PDF files with Evince, shows /usr/bin in a filedialog when you decide you'd like to open the PDF in some other application, has inconsistent (not just reversed) button order in dialogs and other yummy things. There have been attempts to solve this e.g. by creating a Qt version of Firefox, but those AFAIK have never led to something usable in practice, and with WebKit now part of Qt I somehow fail to see the motivation for anybody to try once more. And in this situation we had just a short time before openSUSE 11.2 feature freeze.
The trick, of course, was using magic. The Firefox with KDE integration is still the same Gtk Firefox, just with a bunch of hooks calling an external helper. I don't have the ability of some other KDE developers to have clones, and I'm not crazy enough to try to mix Gtk and Qt in one process (which, despite the possibility of a shared event loop, should be nowhere near trivial). So it's nowhere near the extent of the Qt port, and maybe that's why it has worked out (as we all should know, perfect is the enemy of good).
The helper and the patches at available in a Gitorious repository, they are made to match the openSUSE package so they may not possibly apply cleanly to upstream sources, but feel free to play with it. Actually, you are more than welcome to do anything you want with it (wanna be the maintainer of it? no problem). With the problem more or less solved, and with other things to do, I don't have any further big plans for it. I will try to push this upstream if possible (I have no idea what faces will Firefox developers make when they see it), but besides that, there are still many other areas that need some magic. And, after all, the ultimate plan is still that Konqy will one day rule the world .
not your average geek
1256838707|%e %b %Y, %H:%M %Z|agohover
On a related (to my other blog post today) note, while I'm giving credit where credit is due: my personal KDE hero at the moment is Anne Wilson, who has been helping KDEPIM users for years on our lists and at meetings and has been a voice of reason, courtesy, constructive feedback and positiveness that makes a huge difference in the atmosphere of our community. I much admire her work with the documentation team (userbase, anyone?) and the community working group and ever since I first met her in person (in Glasgow, I think) I have been impressed by the fearless and all embracing manner in which she has found her way amongst us weirdos and become a gentle, well respected leader and wrangler of geeks. I don't know when exactly it is, but happy 70th birthday, Anne, all the best from us PIMsters, we thank you and look forward to many more Akademy meetings with you.
