{"id":1269,"date":"2007-10-31T02:10:44","date_gmt":"2007-10-31T00:10:44","guid":{"rendered":"http:\/\/vizZzion.org\/blog\/2007\/10\/kwin-fglrx-and-aiglx\/"},"modified":"2007-10-31T02:10:44","modified_gmt":"2007-10-31T00:10:44","slug":"kwin-fglrx-and-aiglx","status":"publish","type":"post","link":"https:\/\/vizZzion.org\/blog\/2007\/10\/kwin-fglrx-and-aiglx\/","title":{"rendered":"KWin, fglrx and AIGLX."},"content":{"rendered":"<p>I upgraded my notebook to Kubuntu Gutsy last week. In the end, I decided to<br \/>\n    cleanly install it since I had made quite<br \/>\n    some modifications to (mostly powermanagement-related) pieces, and I wanted to sync with the current state of<br \/>\n    the art of fellow Ubuntu developers.<br \/>\n    It has been a bit of a bumpy ride, and I have yet suspend to get working again, some debugging is needed there.<br \/>\n    I&#8217;m suspecting the ipw3945 driver and fglrx.ko to not play nicely, so that&#8217;s left for further investigation.<br \/>\n    <br \/>\n    I have now installed the newest fglrx driver (42.3) which includes brand-spanking new support for AIGLX. KWin<br \/>\n    from KDE4 works now on that machine. Hooray! (No Xgl tricks needed.) I didn&#8217;t get the driver to compile with<br \/>\n    a 2.6.23 kernel, but I heard the support for this is already in the pipeline. It would really be nice if those<br \/>\n    things wouldn&#8217;t be held back. I guess that&#8217;s me really waiting for a driver for ati chips that is developed in<br \/>\n    the open, so hopefully the newly released specs and driver will fix that within a reasonable timeframe.<\/p>\n<p \/>\n    KWin (running with this new AIGLX support) still appears to suffer from some performance problems, application<br \/>\n    resizing is slower than in Kwin3 (but<br \/>\n    feels better than in Beryl where I really find it annoyingly slow). I understood that there are also some problems<br \/>\n    with knotify4, but dfaure should have already fixed that. Transparency in konsole works smoothly. I find the shadows<br \/>\n    of windows not perfect yet, they seem to be painted when the application still fades in and create a dark<br \/>\n    background and a less smooth transition. Also, the edges look a bit artificial to me, maybe some more blur towards<br \/>\n    the outer edges would do good here. (Lubos, Rivo!? :-))<br \/>\n    I really do like the sliding animations when changing virtual desktops. (Bonus point for making that one respect<br \/>\n    the ordering of desktops on pager plasmoid :> ) Also the expose effect with its &#8220;find as you type&#8221; is really a<br \/>\n    useful thing. Big thanks for that!<br \/>\n    Another thing that struck me in a positive way is kickoff. It works really well, feels snappy, the search feature<br \/>\n    rocks compared to the &#8216;classic&#8217; menu. I had tried kickoff in KDE 3 some time ago, but it didn&#8217;t seem to be my cup<br \/>\n    of tea. I&#8217;m astonished how this addition makes the new desktop really a useful and intuitive tool.<\/p>\n<p \/>\n    It&#8217;s good to see many things falling into place right now, and experiencing the progress that is currently being<br \/>\n    made towards a release. For some, it turns rather stressful at times. Dealing with high expectations, a lot of<br \/>\n    feedback that is not always equally useful (hello, armchair developers!) can be daunting. Nevertheless, the<br \/>\n    critical point of the development cycle leading up to KDE 4.0 lies well behind us. Putting this into context,<br \/>\n    we&#8217;re now pretty close to having our work in a state where we can actually use it, take advantage of it and<br \/>\n    have fun with it &#8212; and make it a smooth release.<\/p>\n<p \/>\n","protected":false},"excerpt":{"rendered":"<p>I upgraded my notebook to Kubuntu Gutsy last week. In the end, I decided to cleanly install it since I had made quite some modifications to (mostly powermanagement-related) pieces, and I wanted to sync with the current state of the art of fellow Ubuntu developers. It has been a bit of a bumpy ride, and&hellip; <a class=\"more-link\" href=\"https:\/\/vizZzion.org\/blog\/2007\/10\/kwin-fglrx-and-aiglx\/\">Continue reading <span class=\"screen-reader-text\">KWin, fglrx and AIGLX.<\/span> <span class=\"meta-nav\" aria-hidden=\"true\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[29],"tags":[],"class_list":["post-1269","post","type-post","status-publish","format-standard","hentry","category-kde"],"_links":{"self":[{"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/posts\/1269","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/comments?post=1269"}],"version-history":[{"count":0,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/posts\/1269\/revisions"}],"wp:attachment":[{"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/media?parent=1269"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/categories?post=1269"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/tags?post=1269"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}