Have you ever wondered what the KDE developers were thinking? Have you ever wondered what motivates or annoys KDE developers? It was these questions that prompted the development of, an online weblog for KDE developers.

This weblog is intended to be for KDE developers to journal their thoughts in a community atmosphere. This is not meant to really compete with things like or the This is meant to be an area exclusively for KDE developers to share their thoughts about KDE or anything else for that matter. It's an incubator for ideas and an area to let the community see what the KDE developers are thinking. This is not a reflection of KDE policy but a reflection of KDE developers own thoughts. This freedom allows developers to think outside the box and not have to worry about policy derailing a discussion in its infancy.

For interested users who want to watch what their favorite developers are up to, we are providing RSS feeds for both the main site and individual blogs. I hope both visitors from outside the KDE community and developers from within the KDE community find this site enjoyable and friendly.

Dot Categories: 


by JC (not verified)

I really like this idea.
I can't wait to read more things in the website.

Btw, where is the RSS link ? :)

by Ian Reinhart Geiser (not verified)


-ian reinhart geiser

by Navindra Umanee (not verified)

Great. If someone sends me a simple script that pulls this file and converts it to something like this, I'll be happy to put a sidebox on the dot. Too lazy/tired/busy to do it myself at the moment, but might eventually get to it if noone steps up...

by Ian Reinhart Geiser (not verified)

Ill see what i can do. any reason why you dont do rss?

by Navindra Umanee (not verified)

Haven't really had a need so far for it, so I haven't looked into it. historically provides us with HTML and the stuff is a hobbled together hack that parses the main page of the site...

by Navindra Umanee (not verified)

RIght now, pulling this file includes quite some garbage at the top not related to the RDF feed. For example, I see entire log entries in this file at the moment:

Well, I still have no time to hack on KDE, (well, Kopete to be more specific)


But that's after I'll port KMail and KNode to it, especially that I n
eed to work on html export in KWord a little more.<?xml version="1.0" encoding="

[proper RDF feed continues here]

by AC (not verified)

It's too bad that the feed is served with the text/html content type, when it's not html.

by AC (not verified)

This is a really cool idea. :-)

by ik (not verified)

whats the difference between this one and the already existing qt<->dcop bridge ?

by ian reinhart geiser (not verified)

read the link you will see its VERY different.
(no im not going to explain it because thats what the link is for)

-ian reinhart geiser

by ik (not verified)

ah indeed, i should have read it before commenting ...
it looks very interesting, another way (besides kommander) to create 'kde shell scripts' (and more). it seems to have some advantages over kommander too (but its less straightforward i guess).

by AC (not verified)

I'm not an expert, but I'll try to answer anyway.

I think the main difference is that it makes the link bidirectional... Not only can you send messages to qt widgets, but you can receive messages from them too.

So you make an XML file describing what your widgets are, then you make a shell script describing what they should do... and *poof* you have a mini KDE application.

I guess it's not such a big deal if your favourite language already has a way to call Qt, since then your program could just make the widgets itself, and then of course it could get messages from the widgets. I would guess that the differences are:

1. This new method would work with any scripting language that can read and write from pipes and files... which should be all of them. :-)

2. It doesn't depend on your users having the Qt-from-Perl or whatever module installed (for example).

I think it would be great for building KDE front-ends of command-line utilities, and for things like graphical installers for KDE programs.

Then again, a lot of my post is speculation. :-)

by Ian Reinhart Geiser (not verified)

You are completely correct, but there is one detail that is missing and is not quite bug free. Basicly that is the fact that you can map most common Qt signals from the UI to events that can be handled at the command line.

This is the true power. With KDE containers now in Qt 3.2 we will see things like KJanuswidget in there too. Imagine all those sysadmins who can now have GUI front ends to all of those one off shell scripts that hold their systems together. Imagine all of those wacked out perl scripts that now can have a UI so that the users in the main office can use them.

The goal of this is to allow system admins to make KDE do what "THEY WANT TO DO" without the pain of bindings, and learning C++. Just draw your UI file in Designer, write a perl/python/shell script that interfaces with the dcop api (that is the same on all languages) and go.... ( you must be a sysadmin or a recovering sysadmin, because you seem to get this concept quite well )

Sure its not native, but damn, its fast, and probibly fits the bill for all those one off projects.

This is cool ;)

-ian reinhart geiser

by Navindra Umanee (not verified)

When I go to the main page at, it really should not be empty like that. It should send me directly to which seems to be the most interesting content on the site.

Btw, is it just me or are the fonts on this site extremely tiny?

by Ian Reinhart Geiser (not verified)

im still working on this page, I am trying to make it more of an information page and system status messages. Im still working out a few kinks, but for general journals its pretty good.

Another issue, is the anon comments are moderated, and im not sure if thats going to fly, the plus side is it helps protect against trolls, but the minus side is im not sure how many developers are willing to spend time moderating comments.

-ian reinhart geiser

by Navindra Umanee (not verified)

Well the dot gets by without moderation, so I think you should relax it. Anti-anon moderation practically killed KDEnews in my opinion.

However, I do think you should reconsider making the frontpage more than just a status page and put all the exciting content right there (in some form). Unfortunately, I do understand the use for a frontpage and if you put the main content there then you don't have many options for your system/status stuff...

by Philippe Fremy (not verified)

I also support unmoderated anonymous comments, the way the dot allow it (the poster can leave a name and an adress if he wishes to). If somebody wanders around and wants to make a remark, having to subscribe is a tedious processus that will kill the envy to contribute quite effecientely in my experience.

Overcontrol has always proven to be bad, be it for code development, blog comments or simply way of life.

by ian reinhart geiser (not verified)

no, you miss the point, the goal here is not for user posts. this is ment for developers. anon users can post comments, and vote on polls but thats it.

overcontrol is a good thing here, since the blogs are a service to KDE developers and an interest to kde users. If they find a useful nugget then they can post it here.

Otherwise, the main focus is for the developers.

-ian reinhart geiser

by Philippe Fremy (not verified)

1. Users also have good idea, even in the development process. It is important that they can post comments. Sometimes, the best idea for a software comes from an external contribution.

2. KDE developers may wander here without being subscribed and should still be able to post comments.

by anon (not verified)

> is the anon comments are moderated, and im not sure if thats going to fly, the plus side is it helps protect against trolls

In my experience, very few trolls hang around in blog type sites.

by Rob Kaper (not verified)

Do you plan on supporting trackbacks, pings, XML:RPC, RDF tags, blogrolls?
Would be nice to see at least some of those features, as well as valid HTML. ;-)
(I don't think & is correctly changed into & within links and I'm personally no fan of using tables for layout)

Nice idea though, might be big if you can smoothen it a bit. :-)

by Jeff (not verified)

WOW, what an exciting blog! :-( The dot barely gets enough traffic to keep people coming back, and now you want to divide it further by adding yet another news site.... which I've noticed you have yet to post any news for. I don't understand why dot readers wouldn't be interested in kde-development, and anyway you don't have enough news to keep us reading anyway, so what's the point of a news site without any news?

by anon (not verified)

click on blogs in the top

by Anonymous (not verified)

> The dot barely gets enough traffic to keep people coming back

I'm looking forward to don't see you again here.

by AC (not verified)

Wow, you sure are critical...

Which is it? Either he doesn't "have enough news to keep us reading anyway" or he's dividing the dot readership...

I for one am capable of checking both sites. And, while interesting, I'm not sure that the dot is the right place for "what I worked on today"-style informal posts by the developers.

by Jeff (not verified)

Whoops... you're right about the /blog page. Yeah, more content!
I still maintain that merging the sites to have news updated more often than (I'll say on average) about 3 posts per week would be better, imo.
I guess I can just check another site every so often now.

by Datschge (not verified)

I think you fail to see what's the difference between a news and a blog site. I (and others) sure don't want to post my personal stuff on a news site but still might include it in my own blog.