Skip to content

Latest commit

 

History

History
24 lines (16 loc) · 1.53 KB

README.md

File metadata and controls

24 lines (16 loc) · 1.53 KB

He too spoke well - whoever it was, for his identity is uncertain - who said, when asked why he took so much trouble over a piece of craftsmanship that would never reach more than a very few people: "A few is enough for me; so is one; so is none."

Seneca, Epistles 7.11

No man but a blockhead ever wrote code except for money.

Samuel Johnson

Dado

Dado is a collection of User Commands that implements a framework for Dyalog APL development operations. See the wiki for how to install and use Dado in your Dyalog APL session as a user (as an APL developer).

These notes are for working and developing Dado itself.

Bootstrapping

Dado functions can be called directly from the Dado project space when working on Dado itself. This is useful for testing new functionality and debugging. You can also use a properly installed version of Dado when working on Dado. Thus when working on Dado, you can decide whether to use the current state of things or the installed state.

You can call #.Dado.BootStrapBuild 0 to install the current state of the project as a User Command. This function creates a new application folder (dist/Application) but does not create a new release, or push or publish anything. The application folder is then automatically copied over to the location of the user command. Restart APL to see the effects. Note that if you do not see the effects as expected, you may have saved your session with a stale copy of Dado. If this is the case, delete the copy of Dado in the session, save the session, and restart APL.