Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
A modernised version of Wilfredo Sánchez's old DropScript utility.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
|Type||Name||Latest commit message||Commit time|
|Failed to load latest commit information.|
This is a revised version of "Bryan's" version of Wilfredo Sánchez's old DropScript utility. DropScript is a utility for easy conversion of Unix commandline applications and shell scripts into standalone Mac OS X application bundles, so-called "droplets". Just drop the file to be converted onto the DropScript app, and the converted application will be placed alongside the original file. The original behaviour of "droplets" created this way was to pass on the names of all dropped files to the embedded shell script or commandline utility. Modifications I made: - The source script can be a shell script proper, but also an executable, an alias or an application bundle - I added the possibility to launch the droplet without dropping any files onto it, in which case the script (or utility) is launched without arguments. Creating droplets from Finder aliases is possible only by selection the source with a file dialog, not by drag-and-drop. - Launching the DropScript app itself without dropping a file onto it will open as a standard application. Use the Open menu item to select a script, binary executable or even a Finder alias to create a Droplet with. Use the New menu item to create and open a new file in the default text editor, allowing to create a script from scratch - Launching a droplet by command+shift-double-clicking its icon will open the embedded script in the default text editor, unless the script points to an app bundle. - If the script resides on a read-only filesystem (say a disk image), DropScript will ask for a destination to save the droplet. - Droplets created from an application bundle will contain a Finder alias to that application, instead of a copy of the application. - If the source executable/alias has an icon set, it's copied to the droplet instead of keeping the DropScript icon. - I modified the Xcode project for building on 10.6 and higher; there's also an Xcode project for 10.9 and higher September 2014: - The internal copy of the script or binary executable (payload) will now have the same name as the original (instead of being renamed to "drop_script"), ensuring that the command will be seen under the expected name in the task switcher when running. - I've added a switch in the Info.plist (WrapperClosesStdIO) that, when set, will cause DropScript to close stdin, stdout and stderr before launching the payload. This is to prevent particularly chatty applications from polluting the (console) logs. Source: http://head-lights.blogspot.fr/2013/05/dropscript-for-mac-os-x-108-mountain.html