On Wed, 2007-04-25 at 17:39 +0200, Joerg Schilling wrote: > Calum Benson <[EMAIL PROTECTED]> wrote:
> > One reason for that is that GUIs don't necessarily map 1-to-1 onto CLI > > commands, or vice versa. CLIs tend to be modal and procedural, a good > > GUI is often the opposite. Indeed, most of the worst GUIs I've seen are > > just thin wrappers around a pre-existing CLI command, with a bunch of > > text fields and checkboxes that require you to be familiar with the CLI > > command anyway. > > A well designed GUI is able to wrap around the CLI of cdrecord, mkisofs, > readcd, cdda2wav and give you additional functionality that users do not have > directly with the CLI commands. Yeah, the key word in my email was "thin", really... a thin wrapper often results in the GUI being too-closely tied to one particular CLI. A good GUI will typically be somewhat more abstracted from those details. Cheeri, Calum. -- CALUM BENSON, Usability Engineer Sun Microsystems Ireland mailto:[EMAIL PROTECTED] GNOME Desktop Group http://ie.sun.com +353 1 819 9771 Any opinions are personal and not necessarily those of Sun Microsystems _______________________________________________ opensolaris-discuss mailing list [email protected]
