APPEAL Meeting: Springtime in Berlin

A group of KDE contributors converged on Berlin, Germany for five days at the end of March to collaborate on a variety of KDE related projects. The scope was broad and included artwork, human interface guidelines, Tenor (a contextual linkage engine), alternatives to traditional file managers and groupware applications. Graciously sponsored by Novell with additional support from basysKom, credativ and Relevantive, this group of individuals came from as far away as Canada and from as near by as 15 minutes across town.

During the intense day-long meetings attendees broke out into small focus groups, occasionally coming together for presentations and brainstorming sessions. The creation of eye catching, usable interfaces was a common thread in these sessions, which often extended well into the evening hours.

In attendance were artists Frank Karlitschek, Torsten Rahn, David Vignoni, and Ken Wimer who are working on a wide array of artwork for KDE. Joining them were usability experts Jan Mühlig and Ellen Reitmayr who explored how to refine the most commonly used interfaces in KDE, such as Konqueror and the KDE PIM applications. A collection of KDE hackers, including Stephan Binner, Eva Brucherseifer, Daniel Molkentin, Hans Oischinger, Kurt Pfeifle, Cornelius Schumacher, Aaron Seigo and Scott Wheeler helped bring technical expertise to the meeting.

This first APPEAL meeting provided a hot-house for focused, interdisciplinary KDE development. Looking forward, the group aims to grow organically in scope as others with a similar drive for realizing visual beauty, interface clarity and technical creativity in KDE come together. Additional APPEAL meetings are already being planned.

A web site, descriptions of the current APPEAL projects and outreach to the broader KDE, Open Source and business communities is underway. Until then, enjoy some pictures taken during the event.

Dot Categories: 

Comments

by kubu (not verified)

Berlin rocks. I was at WOS 3 and quite amazed about Berlin.

by Aaron J. Seigo (not verified)

i agree. i really didn't get to see much of Berlin as we were pretty busy. i arrived in Berlin just in time to boot over to the hotel, check in, have a shower, change clothes then take the train to the meeting location. i was 5 minutes early for that meeting, after traveling for ~14 hours. and that was pretty much how it went the entire time. i did manage to get out on Saturday evening and met a number of really nice people, but next time i'm in Berlin i would like to get out during the day and visit some of the museums and art galleries.

Berlin also struck me as quite unique compared to the other cities and towns i visited last time i was in Germany...

first we take Manhattan? =)

by David (not verified)

Enjoyed your interview on http://thelinuxbox.org/ Very nice to hear about all that is coming up and being developed for KDE.

All of the hard work is appreciated.

by dc (not verified)

Sounds fantastic. It's really great that these companies are sponsoring KDE and taking usability so seriously.

There is just one problem. Please explain why you capitalize APPEAL? Is that supposed to mean something, or are you just shouting?

by Aaron J. Seigo (not verified)

> Please explain why you capitalize APPEAL?

i didn't want to capitalize it, but a couple of the others thought it would be a good idea. maybe they'll change their mind ;)

by dc (not verified)

Or at least come up with a proper meaning for the APPEAL acronym. Then you can have an excuse to capitalize it. ;)

by Corbin (not verified)

'APPEAL: Please, Enrich, Alleviate, Love' ?

Hows that?

by anon (not verified)

Bad.

by Corbin (not verified)

Hm... I forgot a 'P'!

by Jasper (not verified)

That would be 'pretty please' ;-)

by Morty (not verified)

>i didn't want to capitalize it
Not a big surprise for anyone who have seen your writing:-)

by ac (not verified)

That was mean. =D

by ac (not verified)

...and true to the letter! ;-P

by Aaron J. Seigo (not verified)

i'll be the first to say that Morty was spot on =P

by Anonymous (not verified)

> It's really great that these companies are sponsoring KDE

Yeah, this and SUSE 9.3 will talk all "Novell is all about GNOME" trolls a lesson.

by anon (not verified)

What about SUSE 9.3? Good news for KDE?

by Evan "JabberWok... (not verified)

Several Gnome people were saying that SUSE 9.3 would get rid of KDE (or at least make it an optional install) and make Gnome the standard desktop. This was somewhat based on Ximian's presence within Novell.

9.3 is still KDE based, and several KDE developers still work at SUSE/Novell.

by anon (not verified)

I don't think there was any doubt about 9.3 being KDE-based. What they said was that GNOME support would be improved. Novell is increasing GNOME commitment with bounties, etc. I'd like to see them do the same for KDE.

Maybe they already are, but it's hard to tell. All the Novell noise comes from Ximian people, not the SUSE group and predominantly about GNOME. That too, is bad for KDE in a way.

by Anonymous (not verified)

> What they said was that GNOME support would be improved.

They did by bumping the GNOME version by 0.3.9 and now ship a current GNOME version.

> Novell is increasing GNOME commitment with bounties

Don't think so. AFAIK their Ximian department once assigned an amount for bounties (was it 20000$?) and then listed tasks for some x000$ only. Later for some other x000$. I think there is still money left for bounties from that initial amount. Maybe they are running out of ideas or the bounties were to controversial?

The SUSE way btw seems to be to hire developers or offer internships.

> I'd like to see them do the same for KDE.

It's very controversial if bounties can have an overall positive impact on a project.

> All the Novell noise comes from Ximian people

Like praising Beagle shipping in SUSE 9.3 which is said to be found too buggy shortly before release so that it had to be disabled by default? :-) And the Ximian people have to make some noise: if the NLD doesn't sell better they soon have a big problem.

by hannes gütel (not verified)

The problem with Ximian is not
Gnome vs. KDE
the problem is fair play. FUD from Ximian shows the lack of personality.

I think SUSE shall tell Novell to ask them to shut up and get Ximian under their control.

by Evan "JabberWok... (not verified)

When you talk about "people" (as in "KDE people" or "Gnome people" or even "Computer people"), you include a wide group.

When I used the term "Gnome people", I was referring to some people I know in real life, a couple people on random IRC channels and a couple on LiveJournal. I wasn't referring to anybody actually involved with Gnome development or Ximian. I've also seen plenty of people saying that SUSE is dead because Novell will kill it, either through inept handling or through over-commercializing it[1].

Of course, there are "KDE people" who will tell you equally outrageous claims about KDE, I'm sure.

[1] On an interesting side note, I've seen several people cite the "death of SUSE" as a reason to have or plan to move to Kubuntu. No idea if it means anything at all, but it certainly seems that Kubuntu is the new darling distro.

by Corbin (not verified)

I was hoping that some of the ideas thought up would be mentioned, or a link to a page with some :-(. Looks like I'll have to wait for KDE 3.5/4.0. Great work with KDE 3.4, I love all the new features and the speed increase, though KDE 3.4 on my laptop seems a bit less stable than 3.3, though I only saw the stability issues after upgrading from fc2 to fc3 (while still using the same binaries from the previous version), so I'm suspicioning that it may not be a KDE issues (no stability problems w/ Gentoo on my desktop). I'm really excited for KDE & QT 4.0, and hopefully before KDE 4.0 is released I will have contributed some code :-).

by Aaron J. Seigo (not verified)

> I was hoping that some of the ideas thought up would be mentioned, or a link
> to a page with some

you wont' have to wait for 3.5/4.0... the last paragraph says, "A web site, descriptions of the current APPEAL projects and outreach to the broader KDE, Open Source and business communities is underway." it's coming ... it just takes a bit. i've been back for about a week now and have been working feverishly will many others to summarize and organize what we've done, what we're doing and where we're going ...

i did an interview with The Linux Box Show that will be released in the next day or two that also goes into some more specifics.

so ... patience .. it's coming. it's just a LOT of work and we want to do it right =)

by Ian Monroe (not verified)

The Linux Box is up:
http://thelinuxbox.org/index.php?subaction=showfull&id=1112764056&archiv...

Good to see some support from Novell.

by Anonymous (not verified)

A Brief history of the K Desktop Environment @ 4:58
An Interview With Aaron Seigo about The Appeal Project @ 10:24

by ...... (not verified)

Sometimes in the start KDE (I use kdm) the font size change from 12 to 9 ...
is a bug? my X configuration? (Archlinux, kde 3.4)

by Aaron J. Seigo (not verified)

hard to say without more information, but this forum is probably only marginally better than standing in your bedroom closet and asking the question as far as results will go.

i'd recommend contacting the Arch linux team or asking on the KDE users email list or even coming by #kde on irc.freenode.net and asking there =)

by noone (not verified)

I could also recommend the gentoo channel on freenode and the gentoo forums. They're always helpful even if you use a different distribution.

One potential problem could be some old config file in ~/.kde - if the problem is tied to one user that's likely the case. If KDE has one problem it's that sometimes whacky settings are in whacky files for whacky reasons (especially the file associations and the konquerorrc are problematic in this regard =)

by cm (not verified)

I've experienced the same on a SuSE 8.2 system. Logging out and back in always made the font size return to normal (without me changing any config). I never found the reason for this strange behaviour, so I went with the workaround ...

I think it has gone away at some point because it hasn't happen in quite a while.

by odborg (not verified)

I may have a solution for this. If the size change isn't reflected in your configuration (i.e. that kcontrol actually doesn't show a difference in font size), this may be because X is unable to properly detect your screen.

Try running the following command and compare the results from the two behaviours:
xdpyinfo |grep -e resol -e dimen

If they differ X some times does not properly detect your screen. There is settings for doing this manually in xorg.conf/xf86config but i dont remeber the exact settings, i think it was NoDCC or NoEdid or something - try google or the xorg manual.

Alternatively recycling power on myscreen and reseting X often helped for me when i had this problem (new gfcard and screen so thats why i can't be more specific)

by kundor (not verified)

I have the exact same issue. I'm pretty sure it's because the X server is choosing different dpi on my screen sometimes, so it's not a KDE issue. I've never bothered to look into it because I like the smaller size, when it shows up, but also the larger size when it shows up. I'm easy to please, I guess.

by cm (not verified)

> I'm pretty sure it's because the X server is choosing different dpi on my screen sometimes, so it's not a KDE issue.

I also think it's because of the dpi used. I recently played around with the dpi setting, and I saw that this can lead to really grotesque layout of the whole dekstop if the fonts are too large, or to unreadable fonts if they're too small for the resolution. Changing between 75 dpi and 100 dpi has a huge impact.

Any idea *why* this can happen sporadically, without changing anything in the config? It only ever happened to me on one of my Linux systems...

If it's some auto-detection thing that *sometimes* goes wrong then maybe it would help to set the used dpi with the -dpi option of the X server so the auto-detection is not needed at all? I don't think all distros specify this option in the display manager config.

by odborg (not verified)

when i upgraded from a creative geforce2 to a albatron geforce fx 5900xt on my main desktop this problem went away. I now use the creative in another pc with another screen, and haven't seen the problem there. I suspect that the creative and the screen i then used on my main desktop (sony 420gs) had problems working together wrt dcc.

by kundor (not verified)

Ironic -- I got the problem on a geforce FX 5900.

Perhaps it's something to do with the nvidia drivers.

by Andre (not verified)

"If you look at media players, more and more they're moving away from reflecting the file system and more towards using the meta data contained in the media files to build playlists and show you your actual music files. There's a growing disconnect in media players between what's on the file system and what you're looking at."

Yes, a real problem and no advantage.

Look what happened on Windows! When you install picture viewers and image editing programs each of them creates its own home directory with its own database of images. Same for music players. Same for music exchange. Under windows it is a non-standardized mess. Windows MediaPlayer and say RealAudioPlayer are by no means similar in organising the content.

KDE applications will also mess up that. So what is really needed is one single comprehensive standard for default directories and metadata for music files and so on.

by Joe Lorem (not verified)

The big problem with image viewers on Windows is that they don't deal with file moves very well. When you're coming up with the KDE Way to track metadata and meta-collection, please consider using inodes, so it can cope with all of this.

by Carl (not verified)

Are there any plans to embrace autopackage with KDE4? What I mean is, is there a way to embed autopackage support into KDE? Perhaps through KControl. Perhaps a konqueror plugin to recognize .desktop file embeded in the web page (this idea is from autopackage.org). Add drag and drop support for that desktop file to permanently install the package or to uninstall it? I know autopackage isn't ready, but if KDE embraces it as it is, even with its current state of development, more developers will use it. The only problems we're seeing right now is issues with gcc 3.2 - 3.4 and QT/kdelibs . Hopefully this will be fixed with QT4. I realize this will probably reuquire a custom front-end to package, but like I said, if you build it they will come. And besides, autopackage promises backward compatibility so it wouldn't be that big of deal to go ahead and support it with its current state. This would also be great for updating KDE without having to use distro RPMs. We could just have a system updater.

> The only problems we're seeing right now is issues with gcc 3.2 - 3.4 and QT/kdelibs . Hopefully this will be fixed with QT4.

That's no issue between gcc and Qt/kdelibs but an issue between different C++ ABI versions in gcc. This means that Qt4 will definitely not fix the problem of autopackage and C++.

The fix will be a stable C++ ABI and all distros shipping at least this gcc version. I don't know if gcc 4.0 will offer it, but even if it does it will take a long time (years) until all distros switched to gcc4.