With a lot of requests to see tiling in action, I've uploaded my first ever video. Unfortunately I couldn't get my microphone to work. There are also a few glitches, forgive me for that.
Monday, August 24, 2009
Tiling screencast
Friday, August 21, 2009
Dynamic layouts are here
kwin-tiling now features dynamic layout switching per desktop. Use Meta+PgUp for Columns and Meta+PgDn for Spiral. Watch the windows change their place on the fly!
A few bugs in both the layouts are also fixed. Overall kwin-tiling is pretty stable for now, so give it a whirl and notify me of any bugs you can find.
What it still lacks is Xinerama awareness, but otherwise its virtually feature complete for the first release.
Unfortunately since college has begun I've been able to work on Kwin for only a few hours a week, so progress is a bit slow.
But the good news is that since GSoC is over, we should start seeing loads of new features being integrated into trunk/ to play around with.
A few bugs in both the layouts are also fixed. Overall kwin-tiling is pretty stable for now, so give it a whirl and notify me of any bugs you can find.
What it still lacks is Xinerama awareness, but otherwise its virtually feature complete for the first release.
Unfortunately since college has begun I've been able to work on Kwin for only a few hours a week, so progress is a bit slow.
But the good news is that since GSoC is over, we should start seeing loads of new features being integrated into trunk/ to play around with.
Sunday, August 02, 2009
Introducing Cq
Cq ( Commit Queue ) is a bridge between Mercurial and Subversion. Its whole objective is to allow you to work offline on Subversion repositories, but continue doing atomic commits. Useful when you are on the move and don't have internet access.
The premise is that you copy the working copy into a Mercurial repository. Hack away in the repository, and commit to the repository. Once you are back online, run cq commit to actually commit the changes to the Subversion repository. So it keeps track of commit messages and diffs using Mercurial hooks.
This is not stable software yet, and shouldn't be used for critical code. That said, it definitely won't delete any code unless you tell it to. I also have no idea how this will interact with mercurial branches or some uncommon svn operations. Get it from Bitbucket and read the README to use Cq. You can fork it or send patches or feature requests on Bitbucket or email.
(KDE folks might be interested in this)
The premise is that you copy the working copy into a Mercurial repository. Hack away in the repository, and commit to the repository. Once you are back online, run cq commit to actually commit the changes to the Subversion repository. So it keeps track of commit messages and diffs using Mercurial hooks.
This is not stable software yet, and shouldn't be used for critical code. That said, it definitely won't delete any code unless you tell it to. I also have no idea how this will interact with mercurial branches or some uncommon svn operations. Get it from Bitbucket and read the README to use Cq. You can fork it or send patches or feature requests on Bitbucket or email.
(KDE folks might be interested in this)
Subscribe to:
Posts (Atom)