Write INSTALLATION.md

[rikedyp]

Until there is a runner, all users are required to run APL locally or on TryAPL.org to try exercises. Instructions need to be written and included in the docs folder as per the exercism docs.

[rikedyp]

Will advise users to install Dyalog for use locally so that they can then use ]Get to retrieve the test cases for exercises. Currently unsure what "submitting" exercises looks like, but presumably it involves uploading a .aplf file for now.

[jonocarroll]

If users work locally, they use the exercism cli tool which pulls down the requested exercise and test file into a configured workspace/track/exercise directory, e.g. exercism download --track=apl --exercise=hello-world results in <workspace>/apl/hello-world containing:

• HELP.md (track-specific help)
• README.md (exercise-specific help)
• hello-world.alpf (template solution)
• test_hello-world.aplf (tests).

They should be able to test with exercism test at the command line in the relevant directory. They then submit their exercise with exercism submit hello-world.aplf.

As a user, I'd like to see instructions for downloading the runtime and probably RIDE for editing; setting up the appropriate directory so that I can just )ed ./hello-world.aplf and edit my solution (including that instruction). It might be really helpful if dyalogscript was able to run the test file, but otherwise the ]Get Test_exercise.aplf and Test_exercise lines should be documented.

Some users may prefer to edit their solution on TryAPL.org, but I don't think we need to link out to a repo for any files at any point. The online editor will allow them to paste in solutions copied out of TryAPL.org and see if they pass the tests.

[rikedyp]

Okay now I think ]Link will be the recommended way to develop solutions. We can provide a dyalogscript that can run tests from a command line and hopefully can integrate with the exercism test command.

Once the folder is downloaded via the exercism cli, you can do like this:

      ]LINK.Create # C:\Users\rpark\Documents\GitHub\exercism\exercises\practice\acronym
Linked: # ←→ C:\Users\rpark\Documents\GitHub\exercism\exercises\practice\acronym
      ]names
Acronym Test_Acronym 

Editing Acronym or Test_Acronym in the Dyalog editor will also update the files, so submission shouldn't require any extra steps. We will include info about the exercism test and dyalogscript stuff which would be more for people who prefer to code entirely in a text editor (but will not have the debugging capabilities of Ride or the Windows IDE).

[jonocarroll]

This seems to work well, albeit removing the need for the 2⎕FIX approach since the solution is defined in the workspace - I'll remove those lines from the test files.