KDE Commit-Digest for 19th August 2007

In this week's KDE Commit-Digest: The Summer of Code for 2007 nears its end. Implementation of more features in the Step physics simulation package. More graphical game themes in KMahjongg, KWin4 KShisen, KGoldRunner and KJumpingCube. The start of a new game, KDiplomacy. More development in the Blitz graphics library. Lyrics Plasma applet and other interface work for Amarok 2. The start of the implementation of panels, and a clipboard engine in Plasma. More features in the ODBC Data Sources KControl module. Animation support in the Raptor menu. KCacheGrind is ported to QGraphicsView. MusicXML import function in KOffice. Ability and an application for viewing statistics in KPixmapCaches. KGraphEditor imported, an application to edit "dot" graphs. A new architecture for KMobileTools. KTrace renamed to Inspektor.

Dot Categories: 

Comments

by Sarath Menon (not verified)

So does this mean that liquid will be resurrected? I tried to get it in shape a long time ago, but it was too tough and I ended giving up :)

by jospoortvliet (not verified)

Nope, he's not interested in styles anymore. Some other stuff he did might live again, though ;-)

And of course there is new stuff he is working on. pretty cool, imho.

by a reader (not verified)

Mosfet's back, and we're really happy about it. Whatever he chooses to do, it will be a touch of class to the desktop for sure! I(we) owe to him ;-)

by anon (not verified)

As a newcomer to KDE - who is Mosfet, and what kind of thing has he/ does he do in KDE? Everyone seems excited, so I guess he's really talented at something :)

by jospoortvliet (not verified)

He is a developer from quite some time ago, who kind'a vanished. He wrote some pretty popular stuff in his days, like the Liquid style (mac aqua like) and Pixieplus (image editor) and some other nice things in the KDE libs.

by Morty (not verified)

He did lots of style and window decoration work, he was main developer for it in KDE2 if I'm not mistaken. He created the KDE classic styles(regular and highcolor) and the B2/B3 styles I think. And the KDE2 and Laptop window decorations.

But more importantly IMHO, his news site(Nobody had invented blogs yet:-) was the only place giving regular news about KDE in the pre KDE 2 days. Back then it was no dot, no PR people, developers blogs etc. That site did a tremendous job keeping public interest in KDE during the long development cycle leading up to KDE2.

by Aaron J. Seigo (not verified)

he also worked on such things as kicker. like many of the core hackers back in the kde2 days, his code was to be found all over the place. as the project has grown, more people have become "specialists" concentrating on a specific set of apps or features. interesting how that all evolved, imho.

by madpuppy (not verified)

We all knew Mosfet would be back someday (or never really left :P)

He did some real cool stuff back in the day, looking forward to the interesting stuff He will bring to the table once he gets up to speed...

by oliv (not verified)

In fact (Anecdote), half of the post about Mosfet were people arguing about his gender... I hope he change haircut since ;-)

by taurnil (not verified)

And that is something I never could figure out. Why anyone would care enough to make that such a big deal what gender erm, he/she is/was.

by fast penguin (not verified)

Yep. Besides, such a talented hacker can only be a girl. ;)

by reihal (not verified)

Don't start that crap again!

by a.c. (not verified)

Mosfet was a HIGH maintenance type developer who was very talented. THere is a good saying that applies nicely to him.Everybody brings joy in your life; Some in coming and others in going. Mosfet was a LOT of both.But assuming that he has calmed down and grown up, I am betting that he will be WELL received.

by semsem (not verified)

An alpha with an alpha personality.

by Max (not verified)

Besides Lubos he is the only (unfortunately!) KDE developer I know of who knows how to write efficient code. If you somewhere see MMX special effect code it's probably Mosfet's code...

by LiquidFire (not verified)

Great work on Marble!

By the way, the "Plasma" link has no href so it just links to this page.

by AC (not verified)

Also, the kpilot keyring link points to the thumbnail and not to the full-size image : http://commit-digest.org/issues/2007-08-19/files/kpilot_keyring.png .

by Danny Allen (not verified)

Fixed both issues.

Thanks,
Danny

by nick (not verified)

wow. you should definitely add them to kdelibs for KDE 4.1

by elveo (not verified)

clear case for a styleguide (discussion). that looks 'gangsta awesome'!

by KDEer (not verified)

KDE 4 is going to take the free desktop by a storm!

by Patcito (not verified)

it would be great if Pixie and Gwenview could share some code cause I think Gwenview picture rendering is really slow compared to say digikam but maybe that's just my setup.

by Max (not verified)

No, Gwenview is everywhere slow.
Btw. Kuickshow (with e.g. 64MB image cache) is extremely fast.

by Sarath Menon (not verified)

you should try the latest version of the kipi plugins - there is a fast X-overlay based viewer that speeds up things greatly. If you are using an older version of the packages, you can still compile it from source. Search on kde-apps for it, its not that hard to find and has an obvious name (which i dont remember).

All said, nothing beats pixie - its like comparing word perfect to office 2007 :)

by LordBernhard (not verified)

wow.. pixie is just sooo cool.. even in such an early state.. i hope he's going to improve it and release it... at least with kde 4.1

btw: great work on marble!

by Anonymous (not verified)

Anyone knows where to see the progress of Pixie? Has he commited those changes to svn? It would be great to see those ideas in action :-)

by jospoortvliet (not verified)

It's all private still, afaik.

by djouallah mimoune (not verified)

Initial implementation of panels commit by mbroadst, waiting for the next commit " kicker moved to black hole"

cheers

by Xanadu (not verified)

Hey!

I hate to be a stick-in-the-mud, but, I guess Klickety is gone for good then? That's been one of my favorite quick time killers for MANY moons now. 'Tis a shame it's gone the way of the dodo.

Thanx,
M.

by anon (not verified)

Nothing's ever "gone for good" if someone is willing to resurrect and maintain it :)

by Xanadu (not verified)

heh! Good point!

I wish I could pick it up. I know next to nothing about C++, and the little I do know is only super-basic text-book type stuff. If I had at least a small clue what needed to happen to get a KDE app from QT3 --> QT4, I'd pick it up and play with it. And that would take learning QT in addition to C++.

/me Sighs

I guess I gotta start somewhere, though...

(this is by no means saying I'm picking this up since I'm sure people would want it *working* and not broke like I'd probably leave it... :\ )

--
M.

by Martin (not verified)

> If I had at least a small clue what needed to happen to get a KDE app from
> QT3 --> QT4, I'd pick it up and play with it

Here is for Qt:

http://doc.trolltech.com/4.2/porting4.html

There is a porting tool that does some of the trivial rewrites:
$ qt3to4 myfile.cpp

http://techbase.kde.org/Development/Tutorials/KDE4_Porting_Guide

Small clue provided! ;-)

by Martin (not verified)

Will KMobileTools use KitchenSync / OpenSync now? Will that be one of the "engines" or what will the relation be?

by Carsten Niehaus (not verified)

Tobias merged the OpenSync code into KDE4's kdepim _today_. See

http://websvn.kde.org/trunk/KDE/kdepim/kitchensync/

for details.

by anonymous coward (not verified)

I have really high hopes for opensync, but it seems its progressing very slowly. Looking at mailing lists and svn, it seems there's currently not too much happening.

Will kde4 use opensync .20, .30 or the (hopefully) upcoming .40?

by Matthias Lechner (not verified)

Hi,

first sorry for the late answer, unfortunatelly (well, for you ;-)) I was on vacation. Currently - due to lack of time - there are no concrete plans for an OpenSync engine in KMobileTools, but this will definitely get a high priority on our todo-list.

If you (or anyone else) is willing to implement such an engine, you're welcome. It shouldn't be a too hard job.

Best regards
Matthias