Group items tagged

Microsoft's new "Command Line Standard" guidance on how to write applications which behave nicely as part of a command line interface pipeline ... specifically, PowerShell Commandlets implement most of this by default, but this willl allow unmanaged apps to better coexist in the PowerShell world ...

C++ Command Line Interfaces Standard C++-based implementation. No external dependencies, not even on a runtime library. Any fundamental or user-defined C++ type can be used as an option type. Automatic printing of formatted program usage information. Automatic documentation generation in the HTML and man page formats. Ability to read arguments from the argv array, file, and custom sources. Support for erasing parsed arguments from the argv array. Support for custom option formats. Multi-value option parsing into the std::vector, std::set, and std::map containers. Support for option aliases.

Want to know what I think the next UI breakthroughs will be? Here are two, both of which can be considered a return to fundamentals: 1. Command line languages; 2. Physicality: the return to physical devices, where we control things by physical body movement, by turning, moving, and manipulating appropriate mechanical devices.

Expect is an extension to the Tcl scripting language to create an automation and testing tool for CLI applications such as telnet, ftp, passwd, fsck, rlogin, tip, ssh, et., and because it wraps the standard command-line interface, it can be used to automate any arbitrary applications that are accessed over a terminal.