Environment

The source code for DropToScript is available in this project. It is written in Xojo.

What does it do?

DropToScript is a fairly brainless 'command line script wrapper'.

It does not 'do' anything of importance.

It's aim is to provide a drag/drop interface to a collection of command-line scripts.

These command-line scripts all work perfectly fine without DropToScript, but their user-interface is not very user-friendly: you need to be accustomed to working with a command line, and processing many files via the command-line can be daunting for an inexperienced user.

DropToScript allows you to drop a bunch of files onto a program icon, and it will then proceed to process all of these files through one of the command-line scripts provided.

Do you need to rebuild the Xojo project?

Because DropToScript has so little functionality, you'll rarely, if ever, need to rebuild a new version from the Xojo source code.

Instead, you use the ready-built version available in this repo. There are versions for Mac, Windows and Linux.

Code Certificates

To build a release version from source code, you will need your own code signing certificates obtained from Apple and from a Windows-recognized code-signing authority.

To sign the Windows executable from the Mac, you also need to install osslsigncode.

The easiest is to use MacPorts, and then use that to install osslsigncode

https://www.macports.org

Once MacPorts is installed:

port install osslsigncode

How to build?

To create a release version of the DropToScript app, you need a recent version of Xojo installed on a Macintosh.

I am currently using Xojo 2019r1.

https://xojo.com/

Xojo is a commercial software development tool and not open source.

Step 1: Open the main project file DropToScript.xojo_project with Xojo.

Step 2: Adjust the version number of the app in the Build Settings - Shared section in the left-hand side bar.

Make sure to save the Xojo project before proceeding.

Step 3: Build the project. Three versions should be built into a subfolder 'Builds - DropToScript.xojo_project'

Step 4: Adjust the ReadMe.txt in the distdocs folder

Step 5: Adjust the makerelease.command script so it has all your code signing details in it. The default script has mine (Kris Coppieters/Rorohiko) and you won't have the necessary certificates to use my key. You need to get your own code signing certificates.

Step 6: Double-click 'makerelease.command'. You'll need to enter the code signing password for the Windows code signing certificate. This makerelease.command calls onto a script under the 'DropScripts' folder to automatically collect the available command-line scripts into the final .zip file

You should now have an up-to-date version DropToScript.n.n.n.zip appear in the top-level 'ReleaseVersions' folder.