From: Sven Luther <luther@dpt-info.u-strasbg.fr>
To: Otto Wyss <otto.wyss@bluewin.ch>
Cc: wx-dev@lists.wxwindows.org, linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Re: [wx-dev] Linux GUI considerations
Date: Wed, 5 Feb 2003 21:13:19 +0100 [thread overview]
Message-ID: <20030205201318.GA1146@iliana> (raw)
In-Reply-To: <3E416980.2B2F85@bluewin.ch>
On Wed, Feb 05, 2003 at 08:44:00PM +0100, Otto Wyss wrote:
> > From: Julian Smart
> > I would certainly be keen to encourage better uptake of Linux through
> > use of wxWindows, but I have to take issue with the argument that
> > a framebuffer-based approach is going to help this. XFree86 has had years
> > of development and tweaking. Are you really saying that we could
> > write a better X11 replacement? Even if we did and managed to write
> > a 3rd super-duper desktop environment with all the required little apps,
> > we'd face a huge struggle in persuading people to use our particular
> > environment instead of X11.
> >
> XFree86 has done a tremendous amount of effort. Still large part of this
> is simply spent in the wrong places. Instead of keeping writing directly
> to the hardware they should concentrate in building kernel drivers,
> maybe separate maybe together with the framebuffer people. Currently it
Well, remember that X don't run on just Linux, so i guess they are
afraid of duplicating the work, having to rewrite the driver for each OS
they run on. And as a X driver writer, i understand that concern.
Friendly,
Sven Luther
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
next prev parent reply other threads:[~2003-02-05 20:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-04 22:19 Linux GUI considerations Otto Wyss
2003-02-05 8:38 ` Fredrik Noring
2003-02-05 19:44 ` [wx-dev] " Otto Wyss
2003-02-05 20:13 ` Sven Luther [this message]
2003-02-05 22:03 ` Jon Smirl
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=20030205201318.GA1146@iliana \
--to=luther@dpt-info.u-strasbg.fr \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=otto.wyss@bluewin.ch \
--cc=wx-dev@lists.wxwindows.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;
as well as URLs for NNTP newsgroup(s).