From: Bruno H. <br...@cl...> - 2017-03-13 22:37:29
|
Hi Jörg, > Maybe we could differentiate user expectations by target platform? > - MS-Windows: single file mostly welcome (think "portable executable (PE)"). > Self-extracting and executing archives are common. OTOH, nowadays the "File Explorer" can unzip .zip files right away, I think. Right? > - trad. UNIX: ... > (I remember other tricks, like a file beginning as a tiny shell script, > then exit, followed by binary stuff). A shell script is also what GNU 'shar' produces. In KDE, when you click on a .zip file in dolphin, it opens 'ark', which allows the user to extract the zip into a target directory, without any use of command-line. But when I click on a .sh file in dolphin, it opens it in an editor by default. It also offers the option to execute it in a terminal emulator, but this does not work (and avoiding the command-line was one of the purposes of the exercise). > - MacOSX: People are used to foo.app for GUI apps. > Some know that they can invoke apps on the CLI via e.g. /Applications/VLC.app/Contents/MacOS/VLC > I have no idea whether a CLISP.app structure would make sense for a program that > only lives on the command line Can you find out? Bruno |