I’ll get it up soon. Been deep in a creative project.
re: licensing, you can just use anything from the streams as you please. The streams are CC licensed, and i just assume people will rip any chunk of code they find useful. You can attribute me if you like, but I’m not precious about these relatively informal stream documents. Just happy they’re proving useful!
@dan_derks First, I want to say how thankful I am that you’ve gone through and timestamped these episodes and laid out all the info so well. Without this outline It would’ve taken me so much longer to grasp the concepts. I’ve been digging into Crow a lot lately and there’s only so far that the scripting reference can take me. So your outlines of these Maps episodes have been a real boon for my learning.
I just wanted to note that I believe I may have found a small typo in the Zippers code. I saw that you link to the Github in your post for making notes and addressing typos but I’m not too Github savvy so I thought I’d post it here.
For Zippers this code seems to be missing a parenthesis. I’ve added it below and bolded it (or I suppose asterisked it **). There should be a parenthesis on the second to last end at the bottom to close the clock.run(function().
This typo also exists for the shorter clock.run(function() code example you added just above this longer code that I’ve pasted below.
Thanks again for all the work laying out this info!!
while true do
local stage = stages() -- pass the currently-indexed table to 'stage'
output.slew = stage/2 -- the second entry describes time
output.volts = stage -- the first entry describes voltage
if stage then -- if there's a third entry, for shape...
output.shape = stage -- change the output shape!
else -- otherwise...
output.shape = 'linear' -- keep it linear
clock.sleep(stage) -- the second entry describes time
once installed, either:
a. navigate to GitHub - monome/docs: monome.org/docs, click the green Code button and select ‘Open with GitHub Desktop’
b. in the Desktop application, navigate to File > Clone Repository > URL, enter https://github.com/monome/docs for the Repository URL, select a meaningful local path for yourself, and hit ‘Clone’
(if you’ve already done steps 1-3 before, make sure to hit the ’ Fetch origin’ button in the top-middle of the Desktop app’s interface to grab the most recent version of the repository)
once the repository is cloned to your computer, you can either open the individual files from your file browser or open the entire repo from the GitHub app – either way, we’re looking to edit docs/crow/maps/s2e2.md (if you need a Markdown editor, I like MarkText)
make your changes to the file, save, and navigate back to the GitHub Desktop application – you’ll see your file changes as well as a warning message which lets you know that you can’t write to the repository directly: