The next KDE Usability meeting will be Wednesday March 18 2009 at 20:00UTC. This meeting’s theme will be usability bugs. If you have a usability-related bug you would like to discuss, add it to the meeting agenda. We will also review action items from the previous meeting and provide an update on those activities.
A group of students from the University of Oulu in Finland will be conducting usability testing on Dolphin this month. They contacted the Peter Penz, the Dolphin maintainer, and the KDE Usability Project several weeks ago, and we have been working with them on creating usability goals for their testing project. I am very excited to see their results.
In the pipes for April will be usability testing for Amarok through the Columbia (Maryland) Area Linux Users Group. Then planning and training meeting is scheduled for April 8 2009, with tentative testing a week after.
I am also continuing my research regarding interruption, disruption, and system notifications. The point in the primary ...read more...
Today the application for KDE to participate in GSoC 2009 was submitted. They check out our ideas page when they're evaluating applications, so be sure to get your ideas up there! We'll hear back by March 18th. Some other upcoming dates:
March 18-23: Students discuss applications with mentoring organizations (you can and should do this earlier, of course)
March 23: Student application period opens
April 3: Student application period closes
Of course, this hinges on us being accepted...but past years have shown that we have a good shot.
I'm in Porto Galhinas near Recife in Brazil right now, where I'll be keynoting at Bossa Conference later today. I've been flying in last Thursday from Amsterdam via Lisbon, where I already met some Trolls (Andreas (QGraphicsView), Marius (QItemViews) and Simon (QWebkit)). After a good flight (I got four free seats in a row, which translated to "lie down and sleep as much as you can" to me), we arrived in warm and sunny Brazil. It's about 30 degrees here, and it's spot on summer (spot on Winter would On Friday, we visited the INdT office close to our appartment, and on Saturday the iNdT guys took us to Bora Bora, a piece of beach 2 hours south of Recife that welcomes you to paradise. Can't really argue with that. :-) On Sunday, the "conference improper" began with a welcome and drinks in the evening so everybody was able to have a fresh start on Monday. Sandro opened the conference ...read more...
Francesco did a great work when he designed KSudoku. It won the second place in a contest of Linux Format and had support for different variants of sudoku-like games from the beginning on. Even 3D puzzles are possible. It was the generic graph coloring solver which made this success possible.
Unfortunately this solver is limited to graph coloring and not very easy to maintain. This is the reason why I'm writing a new generic engine for logic problems codenamed Logine. In theory it is able to solve any logical problem that results in one (or more) static solution(s). This flexibility is reached by an extensible high performance C++ core and QtScript-based descriptions of the rules.
/* Small script demonstrating how to setup rules */
// Create a board var board = new logine.Board(9, 9); ruleset.addItem(board);
// Make this board accessible for the application. ruleset.content.board = board;
It’s time to present the little hack that I’ve been working on for a while now: A Mac OS X backend (source code) for Solid, KDE’s hardware introspection library. To make a good screen shot, and to show how easy it is to use Solid, here’s also a small hardware browser:
The backend is still in progress, and not all Solid hardware interfaces are implemented yet. Still, the generic interface can be used to introspect any device and read out its properties. You can even introspect the famous Dont_Steal_Mac_OS_X device
One of the nice things about Solid is that it can be used from non-KDE applications as well - it just requires Qt (*)
Next to playing with Solid, the release of Qt 4.5 was a good excuse to play with 64-bit KDE on 10.5 (Leopard).
It is very amazing how many ideas for Nepomuk GSoC projects were posted as comments to my last blog entry. Thank you, really! I read all of them carefully and transformed some of them into actual proposals. I did not use all of the ideas. Some of them were way too complex to be handled in one SoC project. But please do not think that I do not appreciate them. I will soon create a Nepomuk TODO/Ideas page on which you will find your ideas again.
But for now I think having 7 solid GSoC project proposals for Nepomuk-KDE is a very good thing. Now all we need is 7 students that all get accepted. ;) (And of course a bit of mentoring help.)
I’m here to write my 1st post with my new laptop: Dell Vostro 1310. It’s fantastic, I’m really loving it… Anyway, the important part of the post is that Dell sold me it WITHOUT operative system! No Windows(tm) in my system! No stickers and no.. yes, it has the window key, but noone is perfect… I just spoke with Dell commercial reseller and asked to remove OS from my purchase list. And that’s all! Things are moving, fantastic..
What is a distribution and how does it differ from the distribution next door? Do they provide a different-enough experience to the user who is in search of a capable desktop? Note: The author is Norwegian, ...
Want a fancy input method user interface? Want to put it inside your panel ?
I'm currently writing a plasma applet for input method, which enables different input methods (scim etc..) to share same unified user interface under KDE. Its main features are there and with a fully working scim backend. Have a look at some pics:
I remembered reading the discussion on kde-buildsystem about CMake 2.6’s CMAKE_PREFIX_PATH environment variable. I just forgot to add it to kdesvn-build.
Today it finally caught up with me: A build failure I was having ended up being due to not having CMAKE_PREFIX_PATH defined. Although adding it to the environment manually certainly works, it’s something that should have been in kdesvn-build. Well, it is now, at least in the /trunk version of kdesvn-build. It will also be in the next release of kdesvn-build.
My recommended workaround until then is simply to manually export CMAKE_PREFIX_PATH=/path/to/kde/install/prefix before running kdesvn-build (easiest would be to add to your .bashrc). Otherwise if you have a system KDE 4 (or the dependencies, like akonadi, strigi, etc.) then there is a good chance CMake will prefer the system installation to your kdesvn-build install and you’ll have build problems for modules expecting the trunk version of various dependencies.
I met up with Jonathan in Amsterdam on Thursday, at gate D43. We were both booked on the afternoon flight to Abuja and Kano, so we talked shop, drank coffee and considered what we had got ourselves in to.
In Abuja we realised that 38 degrees is quite warm indeed, compared to the 6 and rain in Amsterdam; the air conditioning kept it down to a nice 30 inside.
In Kano we realised that we had got ourselves into the country (after getting past the customs officer who wondered why we knew the names of three cities: Abuja, Kano, Sokoto) and when a dark blue "part of the solution" T-shirt dived in front of a cab driver who was trying to pick us up, we realised that we had arrived indeed.
Welcome to the first Nigerian Free and Open Source Software conference. 400 people packed in to the Sa'adu Zungur auditorium for the opening keynotes; keynotes followed by talks by .. me, for the rest of the afternoon. Unfortunately Cliff (from ...read more...
A couple of weeks ago, I started an attempt to give regular updates on what’s going on with Telepathy development in KDE. Unfortunately, I’ve fallen behind already (thanks to a insanely busy fortnight), but hopefully I can catch up, so here’s a list of what’s going on at the moment:
Porting of existing Telepathy stuff in KDE to use the new library, telepathy-qt4.
Number one is annoying but necessary. Although it doesn’t get us any closer to having full-blown Telepathy awesomeness in KDE, it needs to be done. The old telepathy-qt library (and tapioca-qt, which it was used in conjunction with) is unmaintained and seriously showing its age. It also has a horrible flaw - it is a synchronous API. Although synchronous API’s are nice to work with, they end ...read more...
This year I won't be able to attend the Libre Graphics Meeting, but I still wanted to bring the LGM fundraiser to your attention. The LGM is the gather for everyone who is interested in graphics, art and free software. There are developers, designers, artists, there is fonts, 3d, 2d, color and movies. It's a unique conference, this year held in Montreal.
"This installation can not be reverted, because KDE has about 200 packages, but you will still be able to use the GNOME desktop! "Moreover, there is a problem with Konqueror in this version... it doesn't start.
I have just read that, the march 3rd Qt 4.5 has been released with Qt Extended 4.4.3, but I have read a news that I supposed it was going to arrive... but I hoped for long time to be wrong. The version 4.4.3 of Qt Extended will be the last Qt Extended version. Thought some parts of Qt Extended will be moved to the main Qt code. This, I think is better than nothing but is still not the best thing. In one side, I can understand that Nokia wants to focus on only one product, but a complete product, in the other side, a lot of Qt-Releated software have been / will be dropped soon.
It’s that time again, I just finished a rather large project and now I need to get some work.
Anybody interested in hiring a Software Architect / C-C++ Developer, I can work per-objective, part-time or full-time. I have direct development experience in both GNU/Linux and FreeBSD, Windows using MinGW and/or the Qt Framework; I also have experience developing device drivers and random kernel hacks.
I’m also available for development workshops, if your company or institution needs an introduction to POSIX development, ANSI C++, Qt 4, etc, I can help.
If you have any questions, please contact me via email firstname.lastname@example.org or in IRC gamaral @ irc.freenode.net or gamaral|away @ irc.freenode.net.
Sometimes you have to decide between being “correct”, and being user-friendly.
Also, sometimes you have to do one painful change with many regressions, to reach an ultimately better state.
I hope I had to do the last such step before the stable KDevelop release(Though you never know). I have changed the internal representation of the C++ DUChain, so typedefs spawn custom types, instead of being just pointers to the targets. This is not exactly what the C++ standard says, but this means that KDevelop will no more replace std::string with “std::basic_string<blah bla>” if you implement a function or do other simple refactoring stuff.
There is some problems with generally doing this though, because for example in a template container like “std::list”, you want the types in the completion-list not to show “std::list::reference_type”, which also is a typedef, but instead the type you gave to the container. So how should this be done to be most userfriendly, while still staying correct enough?
I’ve implemented this simple logic for the completion-list: If the typedefs target type recursively contains less template ...read more...
KDE 4.0 RC1 has been released . "The KDE Community is happy to announce the immediate availability of the first release candidate for KDE 4.0. This release candidate marks that the majority of the components of ...
"Indeed, these are fantastic news for all Linux Mint users, especially for the KDE fans, as this first release candidate of Linux Mint 6 KDE Edition is based on Kubuntu 8.10 and it is powered by Linux kernel ...
Hi, I will be giving a talk about KDE next sunday at 11:00 am in the UPC university, on the Campus nord and I am posting this blog entry because if you are in Barcelona and interested in KDE you might want to come.
Here you can find all the information about how to go, schedules and (yes, there are other talks you might want to go too ): http://www.fiberparty.org/
Comments on the last blog regarding Nepomuk and the GSoC were rare. Since I am not sure if that is due to a misleading blog title or due to an actual idea shortage, I am trying again. Please post your ideas as comments to this blog entry. See the KDE GSoC ideas page to check for projects I already proposed. Go nuts!
I’m writing again from the KDE booth at CeBIT (hall 6, stand F50). Although our booth’s location is suboptimal, many users and business representatives are visiting us to checkout what’s new in KDE. Eckhart set up a Windows XP virtual machine with KDE 4.2.1 running on it, and Jos Poortvliet, Alexander Neundorf, and Rolf Eike Beer have joined us to bring the message of free and open source software to the visitors. (Jos also demoed the new Air theme; I’m really looking forward to this in 4.3.)
Qt supports most types for most compilers…… but long double. I do not know why. When asking on #qt (IRC), people say that nobody seems to care. Well… I do. long double have some use in scientific software at least. If you ever need to use long double in QTest, you will need to add this somewhere in some of your headers used by unit tests.
This is tested with Qt 4.4.2 and 4.5, on linux(gcc 4.3.3) and windows (mingw/gcc 3.4.5).
Once you have this code, you can do things like QCOMPARE() between long double and so on.
The NLUUG conference has Jos van den Oever in it, on Strigi, search, semantics -- after all, storage is fine but you do have to be able to find your stuff in the filesystem for it to be any use.
I'll be at the one in the Netherlands -- my regret being there's not enough days in the year to attend all the useful and interesting tech conferences, because the conference in Taiwan sounds very useful from a licensing, compliance and shiny gadgets point of view.