By Unknown Lamer from Slashdot's it's-the-little-things department
Via Planet KDE, some good news for people who hate the KDE 4 notifications applet (coming in KDE 4.10): "So, it seems it's that time of the year again... the plasmoid used in KDE Plasma Desktop to display notifications and the progress of transfer jobs started to really show its age, due to some bad limitations in the old QGraphicsview code to handle complex layouts, so it appeared quite buggy and not so smooth to use. ... The fact that there is some research/development being made to build a new backend for notifications that will support many new features, more 'modern' to be actually useful with the applications that are so heavily 'communication' oriented (both desktop clients and web stuff), that became essential part of out workflow. ... The story begins more than a year ago: we needed a way to display notifications on Plasma Active, and obviously the desktop applet used back then wasn't enough. ... Since we would have to rewrite it in QML anyways, we started it."
The article has two videos: one of the new UI in Plasma Active on a tablet, and another of it on the desktop. They share basically the same code base, differing only by a couple hundred lines of QML. In addition to this, another KDE developer has been musing on a replacement for the freedesktop.org notification protocol
designed to fix the deficiencies that have made themselves apparent over the last few years (parts one
).Read Replies (0)
By timothy from Slashdot's hope-it-all-goes-to-plan department
writes "Virgin Galactic's SpaceShip Two is in the final stages of preparation for powered flight. The suborbital spacecraft, built by Scaled Composites, has successfully completed airspeed, angle-of-attack, center-of-gravity, and structural tests during unpowered glide flights. It is now on track for powered glide flights by the end of this year. Meanwhile, in the hangar next door, XCOR Aerospace continues to work on the Lynx spacecraft, expected to begin powered flight tests early next year. Some exclusive photos provide a sneak peak at things to come."
Also to watch for in the world of private space launches, next month (possibly as early as the 8th), SpaceX has another launch scheduled to reach the ISS
.Read Replies (0)
By timothy from Slashdot's when-instructions-are-redundant department
Reader Presto Vivace
blesses us with news that the state of New Jersey "has banned motorists from making big smiles
[for their license pictures] because such expressions don't work with facial recognition software." Now that passports are by decree grim and glasses-free, I'm expecting the next phase to involve the banning of facial hair, lips, and any hair that blocks the ears
.Read Replies (0)
By timothy from Slashdot's seeks-same department
New submitter tavi.g writes "Working for a ISP, along with my main job (networking) I get to create some useful code (Bash and Python) that's running on various internal machines. Among them: glue scripts, Cisco interaction / automatization tools, backup tools, alerting tools, IP-to-Serial OOB stuff, even a couple of web applications (LAMPython and CherryPy). Code has piled up — maybe over 20,000 lines — and I need a way to reliably work on it and deploy it. So far I used headers at the beginning of the scripts, but now I'm migrating the code over to Bazaar with TracBzr, because it seems best for my situation. My question for the Slashdot community is: in the case of single developer (for now), multiple machines, and a small-ish user base, what would be your suggestions for code versioning and deployment, considering that there are no real test environments and most code just goes into production ? This is relevant because lacking a test environment, I got used to immediate feedback from the scripts, since they were in production, and now a versioning system would mean going through proper deployment/rollback in order to get real feedback."Read Replies (0)