Date: Tue, 2 Jan 1996 11:44:57 -0700 (MST) From: Terry Lambert <terry@lambert.org> To: hasty@rah.star-gate.com (Amancio Hasty Jr.) Cc: sos@FreeBSD.org, jkh@time.cdrom.com, msmith@atrad.adelaide.edu.au, jdli@linux.csie.nctu.edu.tw, freebsd-hackers@FreeBSD.org Subject: Re: syscons driver Message-ID: <199601021844.LAA12261@phaeton.artisoft.com> In-Reply-To: <199512291939.LAA01052@rah.star-gate.com> from "Amancio Hasty Jr." at Dec 29, 95 11:39:22 am
next in thread | previous in thread | raw e-mail | index | archive | help
> > We cannot assume that Joe Random User has X capable HW, and much less > > that he knows what it is he has. > > We *should* assume that Joe out on the Net has X capable HW . > If we have problems with *supported* X hardware then we should addressed > them and not say that we should not be emphasizing X capable apps. We should assume that Joe User has X capable hardware if he has a card capable of graphics at all, from CGA/MGS on up. The problem then is getting an X that can run on it. I think that the install itself, which is sort of off topic for this particular part of the thread (which is apps oriented), should use an API that allows interchanging GUI/TUI components underlying some basic abstractions, like pick lists, etc. And the first option is to GUI or TUI, and is presented as text. This resolves the issues without introducing unnecessary complexity or cutting out the test-only people. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199601021844.LAA12261>