You are viewing archived messages.
Go here to search the history.

Breck Yunits 2021-06-24 00:36:37

https://scroll.pub/ my new static site generator is now mildly interesting. The key idea is instead of markdown it uses Scrolldown, which is a simpler language that is easily extensible Here's a simple sample site with a grammar extension : https://treebase.treenotation.org/treedb/index.html

Ivan Reese 2021-06-24 01:09:25

[moved from top level, original post by Breck Yunits]

I am not sure if I will just use it to start my own domain specific newspapers or if I will focus more on the software and help other people do that. Or move onto something else entirely. Any feedback welcome!

Kartik Agaram 2021-06-24 04:50:06

Another video that's too long for #two-minute-week: giving the Lisp-based Mu shell just a little smidge of syntax.

https://archive.org/details/akkartik-mu-2021-06-23 (8 minutes)

With this I think I'm done with the high-level language or indeed any language design. 3 notations is all this computer will come with:

  • verbose, fast, unsafe
  • verbose, fast, safe
  • terse, slow, safe

(Others are welcome to add more, of course. Part of the goal is to leave some "complexity headroom" for that sort of fun activity.)

What's next: anything but new notations (in this fork)

  • Low-level capabilities. Mouse, timer (Mu still has no clock!), maybe a network driver or six
  • Interesting programs. I might try to build an offline reader for http://internet-in-a-box.org. Or maybe for FoC archives?!
  • Flesh out the prototyping environment a bit more based on experiences actually using it in anger.

Main project page: https://github.com/akkartik/mu

William Taysom 2021-06-25 14:06:56

Whenever I get my hands on a Lisp, my first macro is to replace nonsense like

(let (a b (c 3) (d (+ 1 2))) (list a b c d))

with:

(with

  a = nil

  b = nil

  c = 3

  d = (+ 1 2)

  (list a b c d))
Kartik Agaram 2021-06-25 16:09:01

Ah you noticed the with? πŸ˜„

Jack Rusher 2021-06-24 07:36:17

One of two talks from this year's ClojureD (German Clojure conference) about work with which I've been helping the team at Nextjournal. This talk focuses on a UI/UX redesign that updates context-driven, keyboard-friendly ideas from older environments (especially Lisp Machines!) with modern niceties. One thing we don't talk about here is that in the future the command subsystem will also be expandable and scriptable by end users. There's more Lisp Machine-related goodness coming in the next talk video, which should be released in the coming days. πŸ™‚

Kartik Agaram 2021-06-24 20:59:20

This was awesome.

Srini Kadamati 2021-06-24 22:48:42

this is neat, love the work NextJournal is doing in general. I’m a huge computational notebooks user

Jack Rusher 2021-06-25 05:43:04

Srini Kadamati I think you'll like the next video πŸ˜‰

William Taysom 2021-06-25 14:08:22

Bring it on.

Maikel van de Lisdonk 2021-06-27 11:44:58

Hi,

I’ve decided to step out of my comfort zone and share with you a codesandbox which has the flowrunner-canvas editor embedded. This is the side project I have been working on the last couple of years and shown some video’s of it here. And to manage expectations: this is a small part of what is possible already, and only a very small amount of node-types have been made available when using the editor this way. Also expect some bugs ;-) The editor is responsive but support for touch screens can and will be improved in the future.

But hopefully it gives enough impressions on some of the core ideas of the project.

The flow that is loaded when opening the codesandbox, has a form-node with radio-buttons, when you choose the top most radiobutton, two input fields will appear. The values you enter in those input fields are multiplied together by the expression-node and the output is shown in the debug-node. 

All nodes manipulate the payload (a basic javascript object), which is passed through to the next output. The results are visible in realtime as well as the execution path the flow follows.

In this example, localstorage is used for storing the flow (it is initialised with an example automatically). But this doesn’t work in incognito mode, please be aware of that if you want to try it out like that.

https://codesandbox.io/s/flowrunner-canvas-wljy9

Feedback is very welcome! πŸ™‚ Thanks!

Maikel van de Lisdonk 2021-06-27 14:38:23

An additional example : https://codesandbox.io/s/flowrunner-canvas-wasm-example-p68pz .. you have to play around with the sliders to get some result. The "script" in the ScriptTask-node gets compiled to webassembly in real-time. The sliders are input-parameters to this webassembly module, and the output is shown in the node on the right-hand side.