-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 15 Mar 2010, Adam Williamson wrote: > On Mon, 2010-03-15 at 09:50 -1000, David Cantrell wrote: > >> The names of the tasks maybe need more description. The reason they are radio >> buttons instead of checkboxes is that the choices indicate preset lists of yum >> package groups to install. > > I may be dim, but why does that mean they have to be radio buttons? > Can't anaconda just sum the list of package groups if you pick more than > one option? I don't see any intrinsic reason why the user _shouldn't_ be > allowed to configure a system that's both a Graphical Desktop and a > Software Development system, say. That's just the way we implemented it. The driving force behind these decisions was to make things simple for the user. When presented with check boxes at this point, we found most users would either (a) leave the default choices in place and continue or (b) check them all for fear of missing something. If you remember older releases of Red Hat Linux, you could select Workstation, Server, or some such list of system types. That was basically the same idea for package selection. That said, I'm not trying to defend the radio buttons, just explain what they are and how they work. Check boxes make perfect sense, but before just changing them over, I would first say we should really look at the tasks as defined now and see if they should be changed, expanded, or reduced. - -- David Cantrell <dcantrell@xxxxxxxxxx> Red Hat / Honolulu, HI -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkuemrkACgkQ5hsjjIy1VkkBOwCgl525iMcRBnRPbANu36tY7d6Z jv8AnRB1wWIULwoWvcRnmSIbcBaW5U9i =E60s -----END PGP SIGNATURE----- -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
