Date: Fri, 12 Nov 2010 12:22:38 -0700 From: Chad Perrin <perrin@apotheon.com> To: freebsd-questions@freebsd.org Subject: Re: Tips for installing windows and freeBSD both.. anyone?? Message-ID: <20101112192238.GA40427@guilt.hydra> In-Reply-To: <4CDD8907.3060405@laposte.net> References: <201011100009.oAA09mfG024502@mail.r-bonomi.com> <AANLkTi=KNcjf6bo52=D9ioh7c8Fu%2BTHOzusvEdA_KRt6@mail.gmail.com> <20101112011934.GC35128@guilt.hydra> <AANLkTi=E7oow_Ej6Fgm6%2BqWJ%2B_Azse4VFsjUoQoKMLv_@mail.gmail.com> <20101112071646.GF37058@guilt.hydra> <AANLkTimZ3Jb5L6Gwq%2BiJNdh7QpYkncQJi8zqgAVe4GPY@mail.gmail.com> <4CDD8907.3060405@laposte.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--ReaqsoxgOBHFXBhH Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Nov 12, 2010 at 07:35:51PM +0100, Michael Gr=FCnewald wrote: >=20 > But in my opinion, a complete GUI software should also provide some=20 > command line facilities. I mean, for instance, a word processing=20 > software could be shipped with command line tools that could be used to > * inspect document properties (word count, meta information fields); > * convert the document to a publishable form such as PostScript; > * do field replacement for mailings; > and many less elementary treatments could also be useful! Some software= =20 > comes with a scripting language, but for simple operation and batch=20 > processing, this may not be so convenient as a command line tool. The "easy" way to do that would probably be to write things as single-purpose libraries with command line interfaces, then write GUI interfaces that use those libraries. Failing that, just write command line tools and write GUIs that use those tools on the back end; writing them as libraries with command line interfaces is not *entirely* necessary. In addition to being the "easy" way, I'd say it's the *right* way to do it as well. That way, someone who *just* wants the functionality of one or two CLI utilities, and not all the functionality of some bloated GUI all-in-one application, can get the parts independently. Last I checked, I think K3b uses cdrdao, cdrtools, and growisofs on the back end, with the GUI just an interface layer over the top of those tools. While I'm not a fan of things being tied into a set of DE libraries for applications I actually use, at least the basic premise of composing GUI tools from CLI tools is well used in this case. At least two of those three CLI tools are also actually composed of several smaller CLI tools, themselves. --=20 Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] --ReaqsoxgOBHFXBhH Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAkzdk/4ACgkQ9mn/Pj01uKVl8gCg9Z/1uXZFYhqR23l62pnyQsws oVEAoNa3UPsTd8QKwiiJo3Xy2Kc18m3P =r7wr -----END PGP SIGNATURE----- --ReaqsoxgOBHFXBhH--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20101112192238.GA40427>