On Fri, 12 Nov 2010 11:23:22 -0700, Chad Perrin <per...@apotheon.com> wrote: > The type of program I specifically meant was the sort of thing that > actually tells the user the command that would perform the same task as > the button-click, so that users of the GUI (or captive interface TUI) > would get to see what is going on behind the scenes and perhaps learn > from it.
Ah, I see. I've in fact wirtten such a wrapper program around the pw program - a set of input fields to define input data (command line parameters) to pw, and a "composited field" that would contain the resulting command. If the wrapper did miss a function, you could access this final command field and also edit it. Depending on which options you had set, the command in that field would change. The GUI wrapper also gave a short explaination of the options used. Sadly, this concept is usually NOT employed by GUI programs because their programmers think about "their way" as the only way existing. So if "my" image viewer allows you to resize and convert ONE picture, why should it show you how to do that with an arbitrary amount of pictures? :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
