{"id":1378,"date":"2005-05-06T01:38:55","date_gmt":"2005-05-05T23:38:55","guid":{"rendered":"http:\/\/vizZzion.org\/blog\/2005\/05\/guidances-displayconfig-mockup\/"},"modified":"2005-05-06T01:38:55","modified_gmt":"2005-05-05T23:38:55","slug":"guidances-displayconfig-mockup","status":"publish","type":"post","link":"https:\/\/vizZzion.org\/blog\/2005\/05\/guidances-displayconfig-mockup\/","title":{"rendered":"guidance’s displayconfig mockup."},"content":{"rendered":"

\"a<\/a>
\n\t\tLast night, I visited Simon<\/a> in order to discuss some
\nnew stuff we want to put into displayconfig, one of the applications in guidance<\/a>.
\n\t\tBesides discussing some minor issues, we made good progress with respect to the user
\ninterface and code design of displayconfig, especially of the configuration of multiheaded setups.
\nWe discussed how we wanted to design the user interface, so that it’s not only possible to do
\n“simple” things, such as switching resolutions. We’re planning to implement functionality to
\nconfigure a dual screen Xorg setup from within KDE. One of the results of yesterday night’s session
\nis the screenshot of a mockup, that should give some idea how that’s going to look like.
\n\t\tMoreover, we had a look at different solutions to detect hardware. Basically we need to know
\nthe number of graphics adapters, which is pretty simple since they’re attached via the PCI bus in
\nmost cases. More complex is the problem of detecting the number of monitors attached, the actual
\nsize of monitors, the technical capabilities of the screens (such as refresh and sync rates). There
\nare a couple of tools which can help with that, but all of them have their problems and limits.
\nMandrake ships ddcxinfo<\/em>, which did a pretty good job detecting Simon’s TFT display and its
\ncapabilities, but it pretty much sucked on my notebook, which was in that case reporting a display
\nsize of 90″ (!!). xresprobe<\/em>, which is shipped by e.g. Debian and Kubuntu let my notebook
\nscreen flicker, which scared me a little, and it only managed to return my native resolution, but
\nnot for example the sync and refresh rates. Then, there’s ddcxinfo-kanotix – obviously not packaged
\nfor Debian in that incarnation. It printed out a lot of modelines, which is probably not too bad,
\nbut also not sufficient for what we need. In other words: We still need a good way to get an idea of
\nthe hardware topology of all display-related devices, suggestions – of course – are welcome (contact<\/a>).<\/p>\n

\t\tAlso the configuration of the X server is a pretty complex complex issue since a lot of the
\nsetup depends on the driver used. The most generic solution for a dual screen setup is
\nXinerama<\/em>. However, Xinerama<\/em> has the disadvantage of limiting 3D \/ hardware
\nacceleration capabilities. Vendors like nvidia and ATi work around that in their drivers by
\nproviding support for e.g. proper window placement from “merged framebuffer<\/em>” mode, which is
\na quite different setup with respect to xorg.conf compared to traditional Xinerama<\/em>. So we
\nhave to decide which way we want to do the configuration for the user, depending on the driver used,
\nthe resolutions chosen and so on (Xinerama does work with different resolutions and color depths on
\nthe respective ‘heads’, merged framebuffer does not seem to be capable of that) …<\/p>\n

\t\tAll in all, sticking our heads together was quite productive. Things are much clearer now
\nand there’s lots of code to be written. Sounds like we’re making good progress. :-)<\/p>\n","protected":false},"excerpt":{"rendered":"

Last night, I visited Simon in order to discuss some new stuff we want to put into displayconfig, one of the applications in guidance. Besides discussing some minor issues, we made good progress with respect to the user interface and code design of displayconfig, especially of the configuration of multiheaded setups. We discussed how we… Continue reading guidance’s displayconfig mockup.<\/span> →<\/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-1378","post","type-post","status-publish","format-standard","hentry","category-kde"],"_links":{"self":[{"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/posts\/1378","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=1378"}],"version-history":[{"count":0,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/posts\/1378\/revisions"}],"wp:attachment":[{"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/media?parent=1378"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/categories?post=1378"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/tags?post=1378"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}