21 Followers
27 Following
52 Posts

(🔊) Made a little harness to livecode vscode extensions.

Here I change the extension (local to the project) to treat notes in parens as a chord.

No more compile, close, re-open workflow. And that's assuming you've created the extension to begin with. I often make one-off short-lived things and having to manage an extension is annoying.

Now I can just have a .vscode-sandbox.js in each project and make useful little one-off things.

I made a game for GMTK with the goal of making a game that I would spend longer playing than building it. Here's my first 1M point run. (you'll notice there are still visual bugs to fix!)

You can play it here: https://sqrz.app

Sound on! 🔊

"Code lenses" in the space of live programming feel very relevant.

What do you use for visualizing / sanity checking parsing / compiling stages?

I feel like until things are stable, I want the equivalent of rainbow brackets on each node of the AST.

Also thinking about optimization steps, like what happens to each node etc

Lide (live language) dev log 6

Decided to spend some time on async - very rudimentary, but can call multiple functions at a time without blocking.

There are some experiments I want to perform where this behavior will be needed.

Plenty more attention deserved here.

Live language devlog 5 (working name "lide")

I've also been working on graceful error handling, runtime seamlessly continuing even when there are syntax errors. Here's a demonstration.

Also been investigating state management a lot and hoping to give a fun update about it soon.

Edit: And after posting this I see a bug where somehow it parsed the text draw improperly when the circle draw call was not closed- I'll need to investigate!

I'm started a live programming discord. Come talk about and share live programming related stuff. Invite your friends. @albertzak @xavier @akkartik @disconcision- I don't know too many folks on here yet, but I know you're all working on cool stuff!

https://discord.gg/JbMyNGKd8b

Join the Live Programming Discord Server!

Check out the Live Programming community on Discord - hang out with 1 other members and enjoy free voice and text chat.

Discord
On the language design front, I'm finding myself using "once" a lot. I realized the pattern isn't quite complete. I think "once" continues working as is (only re-executes if it changes) but I want another pattern/keyword where instead of everything always reevaluating on any change, it will only re-evaluate if one of its dependencies change (or it changes). But there should also be a way to always do something. Maybe there should be a way to set the change default behavior for a specific scope.

Live language dev log 4

Spent a bunch of time figuring out how to go about doing rust bindings / native functionality / live evaluation when there's an event loop involved! I'm effectively handing it off.

Here's the result! Both native window update and graphics updates.