[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: kcm randr (Alex Fiestas)
From:       "Timothy Pearson" <kb9vqf () pearsoncomputing ! net>
Date:       2010-11-04 18:29:35
Message-ID: 11a69f00308b94f5d0ce375ffb5f576b.squirrel () vali ! starlink ! edu
[Download RAW message or body]

> Date: Thu, 04 Nov 2010 12:12:10 +0100
> From: Alex Fiestas <alex@eyeos.org>
> Subject: Re: kcm randr
> To: kde-devel@kde.org
> Cc: kde-hardware-devel@kde.org
> Message-ID: <4cd29519.5d1be30a.400e.ffffbe2a@mx.google.com>
> Content-Type: text/plain; charset="us-ascii"
>
> Hi, sorry for the late response
>
> Ereslibre and I are planning to do some work in the xrandr area, but not
> specifically in the kcm but in all KDE Software.
>
> We don't have a roadmap yet, so far what we've done is: research how
> XRandR
> works, understand what are the difference between Output/Screen/Etc and
> create
> an application using libxrandr that emulates the "xrandr" tool.
> With the knowlege we've achieved we pretend to update the overall xrandr
> integration in KDE Plasma Desktop, and in some applications.
>
> Also of course, a new KCM will be done and a plasmoid to replace the
> current
> KRandrTray, but we don't know when and how.
>
> Most probably we will do it in extragear first, and then move it into the
> 4.7
> release.

The Trinity project has had a libkrandr XRandR abstraction library/class
for some time; perhaps KDE4 would like to use a similar idea?  The code
should be portable to KDE4 without much difficulty as very few Qt classes
were used.  In fact, given this, it might be possible to share libkrandr
between KDE4 and the Trinity project.

Thoughts?

Tim

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]