Skip navigation.
KDE Developer's Journals

For fun

zack rusin's picture

I'm over at Ian's place at the moment. West Chester, PA, suburbia at its best Smiling
Everytime I come over he makes me do something weird. This time he made me write a bumpmapping algorithm for him. It's mostly used in 3D computer games, since it makes really nice textures. Why did he need it? I'm sure he'll tell you sometime soon in his blog. I'll move the bumpmapping algorithm to kdefx KImageEffect after 3.2. Also if you know any graphics algorithm that you would like to use with QImage's let me know. Either send me the name of the algorithm and the app which implements it, or preferably math behind it.
One of my friends pointed me to the following comment by Jamie Zawinski. He says that it's not possible to mix GNOME and KDE widgets. The whole "not possible" thingy never worked too well in Open Source. Hopefully soon I'll release something that proves Jamie wrong. Hold your finger crossed as I'm busy with some other things at the moment.

Like Komposer. Komposer is the new email composer framework that we'll start using after KDE 3.2 will be out. Besides the HTML composing, which for some reason people want so badly, you'll be able to use KTextEditor editors there, write plugins for it, or just enjoy every KDE application using the same composer.
I'm putting some finishing touches on KConfigEditor and KCFGCreator which I want to release in about two weeks. KCFGCreator has to be integrated with KDevelop. Personally I of course use Emacs but that never stopped me before.
I also play with my web services app, which I use as a testing app for many, many things. It's my toy project so I'm rewritting parts of it on a daily basis. I need to release all my pending stuff before even considering showing the code for that one.
There's also KSpell 2 and I'm trying to figure out what to do with it. I'm not looking too favorably at Enchant right now. The idea is there but I don't like the implementation. Also I'm not in favor of having a glib dependency there. People completely miss the point when they say "it's a small library, every distro installs it!". The point is that I do not want to be doing data structures conversion. Period. Especially considering that the core of a spell checker is like 500 lines of code. I don't see a good reason why we would use Enchant for those 500 lines of code. Now sharing plugins would be a good idea. Especially Ispell, but besides it's just silly.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
stoffman's picture

Komposer VS KWord

I'm yet to gain more understanding in how KDE is constructed. What I would like to know why using Komposer and not Kword? (or KoText for that matter).

zack rusin's picture

Why use KMail and not Konquer

Why use KMail and not Konqueror? "These are completely different applications" you say - exactly. Komposer is an email composing framework, where editors are available as plugins. KoText based editor plugin can certainly be written.

brad hards's picture

Web Services

I'm surprised Tim didn't comment on it - but there is some support code in kdenonbeta/kdeutil/kde/ws/ for web services.

geiseri's picture

Or the fact...

That he only support soap, and believe it or not, NO ONE USES SOAP. SOAP is an over complicated answer to a very simple problem. XMLRPC is what the people who just want to have something that works use.

www.feshmeat.net uses xmlrpc, almost every blog interface uses xmlrpc.(movable type, live journal, avogato) Almost every RSS query interface uses xmlrpc (syntic8 ).

Basicly just because MS dosent force it dosent make it wrong...

Soap may have a place, just like CORBA... but then again ill take dcop/KParts over corba anyday, as I will take XMLRPC over soap any day.

Just my 2c as someone who has had to program in this junk.

tjansen's picture

No one

I wouldn't call Amazon, or Google, or Microsoft, or Sun, or SAP, or TrollTech 'no one' Smiling

It's true that with free tools SOAP is often more complicated. But that's because of the bad SOAP (and XML) implementations. I don't think that any XmlRPC solution is as easy as the good commercial SOAP implementations.

cloose's picture

Not to forget!

Don't forget Aareon in your list. Smiling

http://soapqs.mareon.com/ (german)

zack rusin's picture

As someone who looks at every

As someone who looks at every commit to KDE cvs I think we can safely assume I know what... Smiling

geiseri's picture

How does that saying go?

If your going to say something cannot be done, please be sure to stay out of the way of someone who is doing it Eye-wink

tjansen's picture

Mixing GTK and Qt widgets

Why do you want to prove him wrong? To show that the the it is possible to design GUI APIs that are less pleasant to use than Win32?

zack rusin's picture

I wanted to start an discussi

I wanted to start an discussion on kdedevelopers.org because I have way too much spare time Eye-wink Don't worry about it, we can discuss it when it's ready, not right now.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.