Easiestquickest method for very simple interfaces 4020

On Fri, 08 Jul 2005 20:41:08 +0200, Anton Suchaneck staggered into the Black Sun and said: Anton said he wants to create GUI frontends to start some shell scripts, capture their output, display it, and so forth.

Michael speaks truth here wrt vim. vim (or its less-capable ancestor can edit text anywhere, which can be Really Useful.

? If the tasks are complex, you learn the interface well enough so that you don't have to think about it when you use it. Driving a car is a fairly complex task, but you don't see many people complaining that there's no fancy GUI for their BMW.

Any new thought shoves out anoth... oh look, a puppy!

When your command lines become too complex for you to remember how to compose one of them, you write a script that contains that command line (or lines) and invoke that script. I'd guess you've already done some of that, but the real key is to figure out which operations usually follow one another and invoke those operations automatically.

Specifics on what it is that you want to do might help people buttist you--things like "I want to look for files named FOO in directories BAZ and BARF, and take action QUUX if those files exist in BAZ but not BARF..." Most of what you've said so far is really abstract. With computers, Details Count, and specific examples are really useful.

Computers aren't very smart, and you may wish to look at the Jargon File's entry for "DWIM" to see some of the pitfalls inherent in having a machine try to figure out what it is that you're trying to do.

s-Unintuitive interfaces-Uneducated users. It doesn't matter how intuitive the interface is if the user doesn't know what to do with it.

-- Matt GThere is no Darkness in Eternity-But only Light too dim for us to see Brainbench MVP for Linux Admin mail: TRAP + SPAN don't belong ----------------------------- This space sort of for rent.