From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64] Re: kde4, xorg, xf86-video-ati/radeon, and multi-panel display
Date: Sun, 23 Nov 2008 12:33:34 +0000 (UTC) [thread overview]
Message-ID: <pan.2008.11.23.12.33.34@cox.net> (raw)
In-Reply-To: d257c3560811230338m78e3f60bg40754ac934ea0025@mail.gmail.com
Beso <givemesugarr@gmail.com> posted
d257c3560811230338m78e3f60bg40754ac934ea0025@mail.gmail.com, excerpted
below, on Sun, 23 Nov 2008 11:38:54 +0000:
> if you put your fb as a line input for the script it would be more
> adaptable than is now. but it's a good script.
Well, there's a balance between simple and adaptable. One of my goals
was to keep the number of parameters to a minimum. However, if I had
really intended it for public use (as I've basically setup my kernel
scripts to be, now), I'd have setup a config file and read the
framebuffer size from it. Of course, I'd have the various resolution
choices setup in the config file as well, if I were doing it that way, as
well as the various xrandr output interface names (VGA1, DVI1, etc). I'd
have abstracted out the stacked relationship to the config file as well,
making side-by-side and option, and may have allowed setting the default
position to the four corners and centered on the four edges (much like
kde3's kicker panel positions), as well as centered and possibly
arbitrary, as well.
But when the positioning thing didn't work I kind of lost my motivation,
as I could neither fully debug it nor use it as intended, so I didn't do
much to it after that, except update the hard-coded resolutions for my
pair of LCDs, when I got them.
But... it's a reasonable start (proof of concept, working demo) for
someone with reasonable bash skills, who has a system where the xrandr
position functionality works as documented, so he can test and debug if
necessary that bit of it. Feel free! =:^)
BTW, I didn't document it when I posted, but consider that script to be
in the public domain. That gives anyone who wishes to improve it the
freedom to choose whatever license they want (preferably freedomware, of
course, maybe MIT, since that's the license xorg uses and it'd be rather
pointless without that), for their improved version.
> i think i'll attach it over a hotkey. if i manage to
> have it attached to a hal event it would be even better... thanks for
> it.
I hadn't thought about a hal event... Interesting idea, tho my
configuration here is a reasonably stationary desktop, so there's little
reason to think of the hal trigger. But maybe when I get my netbook
(Acer Aspire One) setup with Gentoo... we'll see.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2008-11-23 12:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-23 7:23 [gentoo-amd64] kde4, xorg, xf86-video-ati/radeon, and multi-panel display Duncan
2008-11-23 10:20 ` [gentoo-amd64] " ABCD
2008-11-23 11:00 ` ABCD
2008-11-23 11:03 ` Beso
2008-11-23 11:39 ` Duncan
2008-11-23 11:56 ` Beso
2008-11-23 13:10 ` Duncan
2008-11-23 11:06 ` Duncan
2008-11-23 11:38 ` Beso
2008-11-23 12:33 ` Duncan [this message]
2008-11-23 11:24 ` [gentoo-amd64] " Beso
2008-11-23 12:08 ` [gentoo-amd64] " Duncan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=pan.2008.11.23.12.33.34@cox.net \
--to=1i5t5.duncan@cox.net \
--cc=gentoo-amd64@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox