delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-apps-help AT cygwin DOT com; run by ezmlm |
Sender: | cygwin-apps-owner AT cygwin DOT com |
List-Subscribe: | <mailto:cygwin-apps-subscribe AT cygwin DOT com> |
List-Archive: | <http://sources.redhat.com/ml/cygwin-apps/> |
List-Post: | <mailto:cygwin-apps AT cygwin DOT com> |
List-Help: | <mailto:cygwin-apps-help AT cygwin DOT com>, <http://sources.redhat.com/lists.html#faqs> |
Mail-Followup-To: | cygwin-apps AT cygwin DOT com |
Delivered-To: | mailing list cygwin-apps AT cygwin DOT com |
content-class: | urn:content-classes:message |
Subject: | RE: Keeping base, adding standard. |
MIME-Version: | 1.0 |
Date: | Sat, 23 Mar 2002 10:03:28 +1100 |
Message-ID: | <FC169E059D1A0442A04C40F86D9BA76008AB77@itdomain003.itdomain.net.au> |
X-MimeOLE: | Produced By Microsoft Exchange V6.0.5762.3 |
X-MS-Has-Attach: | |
X-MS-TNEF-Correlator: | |
From: | "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au> |
To: | <cygwin-apps AT cygwin DOT com> |
X-MIME-Autoconverted: | from quoted-printable to 8bit by delorie.com id g2MN77204047 |
> -----Original Message----- > From: Christopher Faylor [mailto:cgf AT redhat DOT com] > Sent: Saturday, March 23, 2002 8:10 AM > To: cygwin-apps AT cygwin DOT com > Subject: Keeping base, adding standard. > > > Now that we have clickable categories, I think we should > consider not making "Base" the default installation, > defaulting to something like "Standard" instead. > > Standard would include things like: > ... > The rationale is that people can still select a minimal > install with base but still choose a usable setup with Standard. > > How does this sound? This comes back to what I said some time ago - that categories are necessary but not sufficient to provide a good user experience. Something like 'configurations' are needed (which may indeed be categories under the skin) that builds user focused combinations like: Workstation Developer Server Minimal. I'm very unhappy with the idea of overloading categories per se to achieve that, but I won't vote against it. OTOH leveraging dependencies via meta-packages to achieve it makes a lot of sense to me, the question is how to present it to the user in a meaningful way. Rob
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |