Test documents needed...

Hi folks

As you probably know, I worked on ODF support for KWord during this Summer of Code.

But now :


Please, send me as many documents as possible. There are probably some features lacking, but I must know what are the main problems remaining.

Send them to me at pinaraf__A_T__gmail.com

Korganizer with kicker clock applet integration - 2

Hello world

I didn't expect that much answers from my previous blog entry...
What's so special with this clock applet - korganizer integration ? I don't use KOrganizer (my brain is not compatible with such applications : I'm far too messy) so perhaps I'm missing something here...
Thanks to Tobias Koenig for his suggestion about the KDCOPServiceStarter. I didn't know this, and it's quite great. Now the code is far less ugly. So the new patch can be downloaded here. That's the only change I made, sorry I had no time to look at the duration of events.
For the upstream inclusion :
1- I'm not sure there will be a new KDE 3.5 release... I'd prefer a KDE 4.0 sooner if possible.
2- This patch introduces a new dependency in kdebase. If somebody want to look at the weird autotools and make this optional, then perhaps the patch could be accepted, but I'm not sure...
BTW, I'll look at KDE4 tomorrow and forward-port the patch if needed.

Quick and Dirty : clock applet patch for KOrganizer integration

Hi

A friend bugged me about the gnome clock applet that had evolution integration while the KDE clock applet doesn't have KOrganizer integration.
So I decided to hack something on it during the night...
The result can be seen here :

As you can see, days with an event have a blue circle for background... Ugly but enough with my graphic abilities. And when you click on a day in the calendar, korganizer opens itself on this day...
The patch is really simple and can be found here : http://www.pinaraf.info/clock_applet.patch
For the compilation, I tried to understand. Well, I hope I'm not too wrong in the explanations :
1- download kdebase-3.5.7 (may work with another kdebase... may not work... who knows...)
2- extract
3- go into the subfolder kicker/applets/clock and apply the patch (typ : patch -p1 < ~/clock_applet.patch for instance)
4- go back into the "root" of kdebase-3.5.7
5- launch ./configure
6- launch automake-1.9 (or if somebody still has hairs, he can look at this and explain how to do it the right way)
7- since you don't want to waste your CPU to compile the whole kdebase stuff compile with the following commands :
8- cd kicker/libkicker
9- make
10- cd ../applets/clock
11- make
12- make install as root.
Then you can relaunch kicker using the command dcop kicker Panel restart. Et voila...
You've got an ugly-looking integration between Korganizer and the clock applet, with a dependency on kdepim for a kdebase applet... Since kdepim is splitted with kdepimlibs, I hope it has already been done in KDE4... (I don't use korganizer so I didn't test this yet)

Any comment, feature request... can be written here. But don't expect every feature request to be accepted and worked on : I consider this as a waste of time...

Progression on my Summer of Code work...

Today (and monday late) I started implementing support for line through text styles.
That's quite a lot of work because that's not supported by Qt4 scribe :/
I'm really happy because it's basically working, and that's not something I expected to be that easy. Ok, still a lot of work to do, but the basis are working. And the next parts are only going to be writing boring code to implement the various attributes for line through text...
Something interesting with this : OpenOffice doesn't fully implement this. It does support only line through text types and letter through text. Nothing else. We support near of fully line through text styles, what's left is types, color and width. We don't support letter through text, but that'll be easy.
No screen shot currently because the result is still a little weird...

Fun with the testsuite...

Well I wasn't able to do a lot of work on KWord recently : my KDE4 copy broke totally, I had to build it again from scratch...
But now I can continue my fun work : playing with the ODF testsuite. This testsuite is extremely interesting : its files are quite small, testing one feature totally...
Really good.
But some test cases are broken. For instance, no suite should be able to pass the font size test case totally except openoffice because the file isn't valid regarding the spec (there is no "Default" style defined in the spec, and it's mentionned in the file but not defined).
A problem with manipulating ODF files such as these : you must unzip them, then you can open each XML file in KWrite.. That's quite boring. I just wrote a ~20 lines Q&D python program (Quick and Dirty) to help me with this. It's showing on the left the file list, and on the right it shows the file, in raw text. Fast and simple. Now, I can just drop an ODF file from konqueror to the icon on my desktop and voila.
Mandatory screenshot : http://www.pinaraf.info/ODF_viewer.png
The source code (using Python + PyQt4) : http://www.pinaraf.info/ODF_explorer.tar.bz2
If you consider this small piece of code usefull or a good idea or a "should be improved" thing... send my an email or post a comment. I don't plan to extend it really, it's doing its job for me, I don't need more... but if you want more, perhaps you'll get more :)

That's all folks...



P.S : I upgraded this small python thing : now it's automatically pretty-printing the ODF files, and there is some basic coloration of the XML file... Far far better :)

This is where the fun begins...

And here we go.
This is the beginning of my blog for the Summer of Code 2007. Don't expect too much from this. It's the first time I blog, and I don't really like blogging.

So, what am I doing for this SoC ? I'm just trying to have as many OpenDocuments working out of the box in KWord. That's all. Ideally, I'd like to have every single line from the over 700 pages spec implemented in KWord. Realistically, it means I'm doing my best to have more test cases working from the opendocument testsuite, and then I'll switch to some real documents.