Fortunately XF86VidModeSetGammaRamp() and friends allow these values
to be altered by any application while the server continues to run.
This means that a configuration program can write the data to a file,
then have a simple user-mode app run as part of the start-up script
which reads the data
On Fri, 3 Oct 2003, Sottek, Matthew J wrote:
Absolutely nothing says that both can't co-exist. If the default
tools try to allow configuration of everything, even some
hardware specific things, they can try where possible and
feasible to generalize these things, or in cases where that isn't
On Thu, 2 Oct 2003, Sottek, Matthew J wrote:
The thing is, a unified device-configuring front-end would be better
than having every driver writer roll their own. (I mean, we can follow
Windows if we want, but why incur development risk by developing what
essentially is several versions of the
Absolutely nothing says that both can't co-exist. If the default
tools try to allow configuration of everything, even some
hardware specific things, they can try where possible and
feasible to generalize these things, or in cases where that isn't
possible, they can provide hardware specific
Sottek, Matthew J wrote:
What are you doing now? I assume this is a real product; what are you
putting into the XF86Config file now?
It was a hypothetical example. I don't know of a decent way to do it
with XF86Config short of 256*3 Options.
It's 3 curves of 256 datapoints. Floating point or
On Fri, 03 Oct 2003 15:55:47 -0500, Bryan W. Headley wrote:
It's 3 curves of 256 datapoints. Floating point or integer. What you
have to assume is that every point on the curve is grabbable, either
through a spline curve widget, or something like
datapoint [123]^ red [ 45] green [ 23] blue
Tim Roberts wrote:
On Fri, 03 Oct 2003 15:55:47 -0500, Bryan W. Headley wrote:
It's 3 curves of 256 datapoints. Floating point or integer. What you
have to assume is that every point on the curve is grabbable, either
through a spline curve widget, or something like
datapoint [123]^ red [ 45]
Tim Roberts wrote:
On Fri, 03 Oct 2003 15:55:47 -0500, Bryan W. Headley wrote:
It's 3 curves of 256 datapoints. Floating point or integer. What you
have to assume is that every point on the curve is grabbable, either
through a spline curve widget, or something like
datapoint [123]^ red [ 45]
]
Subject: Starting XFree86 without an XF86Config file
The first part of the work I'm doing to improve the XFree86 configuration
experience for users is now available. Some details about it, and a link
to the source patch can be found at http://www.x-oz.com/autoconfig.html.
The goal of this first stage
Sottek, Matthew J wrote:
The thing is, a unified device-configuring front-end would be better
than having every driver writer roll their own. (I mean, we can follow
Windows if we want, but why incur development risk by developing what
essentially is several versions of the same thing?)
You will never be able to create a GUI that covers everything
that is configurable across a wide variety of vendor products...
nor should you try.
Not true. Look at the limited vocabulary you presently have in
XF86Config: keywords, list-of-values, integers, bools. Bools map to
radio buttons,
Sottek, Matthew J wrote:
You will never be able to create a GUI that covers everything
that is configurable across a wide variety of vendor products...
nor should you try.
Not true. Look at the limited vocabulary you presently have in
XF86Config: keywords, list-of-values, integers, bools. Bools
On Thu, Oct 02, 2003 at 02:34:42PM -0500, Bryan W. Headley wrote:
Now, as to anyone who say, eww, it's Gtk, or it's Qt, or I hate
Tk, I have only one thing to say to them: Athena Widgets.
Jesus, no.
The point of this is that it's meant to be *easy* and *simple*. This means that
it should
13 matches
Mail list logo
