today was family day, a statutory holiday, where i live. the p-man has the whole week off from school and will be visiting his mom in vancouver in a couple days during his time off. this will be nice for all involved, particularly he and his mom. Zack arrives tomorrow, the day before he leaves, so it'll be lots of visits to the airport for me over the next week.
the p-man went to visit a friend today while i visited with his friend's parent (singular, so many single parents in canada; lots of single fathers, too; i seem to remember reading something about canada having one of (the?) highest rates of single fathers in the developed world?). that was nice as the sun was shining and the snow was melting away.
i did find some time to hack today, and spent that time refining the AbstractRunner API further so that it's a bit easier yet to write runners and more memory efficient at that. the API had sort of evolved a bit "naturally" over the last year and so this time spent combing through it has been well served.
items are sorted much better now, combining exactness and relevance. i haven't yet added in runner priority, but that will be next. along with some tweaking in the runners themselves, the sorting is already much more sensible.
a couple of the guys (tagx and hydrogen) have been working at porting Plasma::Widget and Plasma::Layout to WoC over the last couple of days and apparently are nearing success. with that behind us we can charge forward with expediency with new features and more bugfixes.
the 4.0.2 backports have been settled in and seem to be working well. thanks to ruphy for the backporting barrage and binner for helping ruphy get everything compiling and working in branch.
if you are running kde from the 4.0 branch, your feedback is very desired to make sure this huge amount of backportage didn't break something subtle. i have a 4.0 branch checked out and compiled, but i run trunk/ daily, which makes it harder for me to notice subtle breakage in 4.0.
tomorrow, another "falling in love all over again" entry.
About Me
Labels
- akademy (3)
- amarok (1)
- appeal (1)
- build system (1)
- community (7)
- crash (2)
- d-bus (1)
- dataengine (1)
- dolphin (2)
- events (1)
- family (1)
- free software (1)
- gnome (2)
- graphics (1)
- guademy (1)
- kde (52)
- kde e.v. (3)
- kde; kdegraphics (1)
- konqueror (1)
- krunner (4)
- libs (5)
- lug radio (1)
- media center (1)
- misc (1)
- openid (1)
- oxygen (2)
- performance (1)
- photos (1)
- plasma (26)
- podcast (1)
- pr (1)
- prose (1)
- release (1)
- social (1)
- solaris (1)
- techbase (6)
- travel (6)
- trolltech (3)
- web2.0 (1)
2 comments:
Are all the backports due to preesure from the Distros. It seems that all the large vendors are offering KDE 4.0 installs as default which must suit the KDE team (very promising). I would ber using KDE4 now but Ubuntu broke KDE4.1 and now KDE3 apps with system tray icons don't go in the system tray and have their own little window but for some reason KNetworkManager doesn't connect automatically and right clicking to get the options to connect doesn't work. Still Kubuntu is my fave distro and I won't hear no Kubuntu bashing on my watch :)
how hard would it be to make a relational database that lists every result that was ever selected, and links it to the keyword for which it was selected, with a count of the # of times it was selected for that keyword, then take the results returned from the runners, and sort them accordingly?
tables:
keyword: word_id, keyword
result: res_id, result
link: word_id, res_id, hits
alternatively, it could be:
result: res_id, result
hits: keyword, res_id
and count the # of entries returned for every res_id from the hits table to get the number of hits.
Post a Comment