I really wish there were more GUI wrappers that literally wrote the CLI commands out on screen as the GUI was modified, to help with bridging the GUI/CLI gap for people.
Also, I miss arRsync.
Also, I miss arRsync.
http://mirror.informatimago.com/next/developer.apple.com/too...
You don't have to use that feature; the "SQL" tab can be ignored, but it's almost available as the last tab of any dialog..
You would type the command name, then "..." and up pops a dialog box with all the options and popup help for what different things meant. As you fiddled with the GUI, it would generate the flags as text you could see. And finally, you could execute, or paste the command line text into the console, or both. It was awesome.
Besides, when colleagues of mine decided to demystify the command line and learn it proper, they're always surprised how much easier it is than they expected.
The GUI/CLI gap, as far as I have seen, is one of willingness to invest some time to learn.
That's not true, CLI programs would still exist even if they could not be composed. And I would guess that if you counted how many of our commands include 1, 2, or 3 executables, the 1 column would be the biggest by far.
One of the major headaches of CLI programs is that they're hard to learn interactively because there's no starting point. You have to read the docs. The point of a GUI command builder is that it gives you something interactive to play with to start to learn how the CLI commands work. The point is not to do everything through the builder, the point is to bootstrap people to the point where they no longer need it.
Also, there's no reason a GUI command builder couldn't also show you how to do composition.