I ate something today that really did not agree with me. Or maybe it was a combination of things. I find that unless I prepare everything myself, eating is such a gamble like that. It's not just that one never really knows the quality of the kitchen that produces the meal, it's also that when I'm the cook I tend to be a lot more conscious of what foods I combine. When I scrounge/scavenge/eat out I tend to be less discriminatory over the combinations and end up doing silly things like eating jalapeno rich nachos for lunch, and then having a bowl of (vegan) hot and sour soup a few ours later. I think that was the combination that did me in. Ugh. So it's probably my fault.
On to more interesting things .. we've received a good number of SoC proposals already for Plasma. More important than the number of proposals, however, is the quality of them. I was impressed with the increased quality of proposals last year, but if the Plasma proposals are anything to go by ... this year is going to rock even harder.
Coinciding (though not strictly related) with this, a new wave of Plasma hackers have started to arrived on our shores. The best part of that happening is that new comers always sharp edges to catch themselves on that we haven't addressed or even noticed sometimes. API documentation inevitably improves and we get a very good idea of what needs to be adjusted or added.
I've also been watching toma's blog with great interest the last few days. With the recent round of Akonadi hacking, I'm looking forward to hopefully be able to do a couple of things: move to a KDE4 mail client full time and implement integration between calendars that appear in Plasma and events accessible via Akonadi.
Which reminds me: I was recently contacted by a fellow who has been researching timeline widgets for a couple of years now as part of his work at the university he's at in Germany. He's about to publish the culmination of his work to date in April. I've seen some demos of his work, and it's already very impressive. I think it has implications outside of just Plasma (to state the bleeding obvious ;). What's quite exciting is that we've discussed working together to bring his code into relevant areas of KDE, which shouldn't be too hard as he uses Qt4 already. =) After his presentation in April, the plan is that he will release his code under an open source license and we can go from there. I'm sure I'll blabber on more about it then. (Note: I haven't mentioned his name or other possibly identifying information, because I didn't get his permission to do so before writing this ... )
I've also been back and forth with another fellow who's been doing research (again, with practical results) in creating a way to rather powerfully define, discover and compose services in rich client applications in rather elegant ways. An outstanding problem has been the "Now that we have the API exported via DCOP/D-Bus, where do we go from here?" question. There have been bits of answers, such as standardizing interfaces via freedesktop.org or in interface classes hosted in kdelibs. But that only goes so far and still leaves a lot of the consumer-side work up to the developer to do by hand. This work provides a bridge between the IPC (e.g. D-Bus) and the consumer; in a way, one might consider it to be bringing some of the web service concepts to the rich client. I've encouraged the author (who's permission to blab his name, etc. I didn't get before writing this either ;) to submit a presentation paper for Akademy, so hopefully that will work out.
It's really enjoyable to work with people doing practical research in areas of my own personal/professional interests. One of the things I came to regret about entering the "IT industry" in the era I did was the lack of collaboration and meeting of minds. I remember reading in my youth about the great collaborations (and rivalaries ;) in science, art and philosophy in history and thinking, "I want to experience that!"
But shortly after getting into the industry, I found that the opportunities for collaboration diminished in direct proportion to the proprietization of technology. I started out in a very open environment, and probably got a bit spoiled there. It wasn't until free software seeped into my life years later that I re-discovered that open environment. Score another one for freedom.
On a more practical level: it will be interesting to see how many of these research concepts actually pan out and in which ways ...
Sunday, March 23, 2008
Subscribe to:
Post Comments (Atom)

10 comments:
hi,
i'm wondering for weeks now what the hell the timeline widget/plasmoid is going to be?! can you explain it?
thanks
I assume this is the project:
http://www-mmt.inf.tu-dresden.de/Forschung/Projekte/INPERIC/Results/TimeZoom/index_en.xhtml
This is a public page, no sense in trying to hide it. And "timeline widget", "germany" is more than enough identifiable information for google.
Looks pretty cool in any case. Similar to Sheldon's work on Slick, with some more ideas and enhancements.
I understand what timeline's are, just not how they would B practical to Plasma?
I would have thought a web based mail and calendar solution would have been more your sort of thing Aaron seeing as you travel so much.
Hm, I found this http://simile.mit.edu/timeline/
Now imagine this aggregating all (more or less) useful time related information as a Plasma widget. Time related information could be usual calendar entries, browser history list, file and program access times etc. The ingenuity would be an intuitive representation of all such events combined, allowing for new approaches on how to access and manage any data. As that's hard to define, achieve and explain there are researches about it and Aaron prefers to remain calm about details for now, I guess. ;)
@leo_s:
well, not trying to hide it, just not trying to push the guy's name out there in relation to this until i know for sure he's all cool with that.
@dave taylor: "a web based mail and calendar solution would have been more your sort of thing Aaron seeing as you travel so much."
actually, because i travel so much web based solutions are utterly useless.
think about it: when at home or in the office i have constant internet access. when i'm traveling, i often don't.
with a web based solution, internet is required.
with a locally syncable service, which doesn't require web anything (though it could use it), internet is not required except for syncing.
what i want is a portable device so i can interact with or without internet access, and that's exactly what i have in the form of my laptop.
anyways, web based solutions don't provide what i want/need from desktop timelines anyways.
"anyways, web based solutions don't provide what i want/need from desktop timelines anyways"
A damn puzzle wrapped in an enigma wrapped in a plasma container. So am I to guess that said timeline could retrieve emails and calendar appointments (and I imagine files through the magic of Strigi). Given that with the snippets of information I have I still can't figure out the purpose of this timeline then would I be bright enough to put this tool to use?
it not exactly the topic of this post, but whats about the mediacenter thingy you spooke for awhile? mythtv is ported to qt4 the last weeks, so it should be easy to use with kde things like plasma. Have you any news in this area?
Hi Aaron, a quick question: is there a way to send a signal to plasma save it's geometry and plasmoids? Something like the old "dcop kicker Panel restart".
I ask because plasma crashes on logout (every time) in my kubuntu 4.0.3 and I loose all plasmoids I added.
Sometimes it crashes even before logout, but that's another story ;)
@Iuri: "is there a way to send a signal to plasma save it's geometry and plasmoids"
dcopquit plasma; sleep 1; plasma;
that does the same thing the old kicker restart dcop interface did.
btw, a d-bus interface for plasma will appear in 4.2; we're waiting for 4.2 so we can do something coherent and solid, rather than a random collection of things.
as for your instabilities, the 4.0.x kubuntu packages are rather poor right now as far as stability goes =/ so i feel you pain. hopefully the 4.1 packages will be better in that regard.
Here is the link to the Qt widget:
http://advancingusability.wordpress.com/2008/03/31/facetzoom-first-open-source-release/
Post a Comment