reports from the firefox (nightly) micronation

Neat explorations! ❤ the name 😄

Was digging into the code and wondering why you have an iOS wrapper? Are there limitations with web gestures in the provided browser?

One of my side projects ages ago was to do with doing gestures on a webpage, so I’m interested in the stack 🥞

Mariano Guerra Fantastic. An explicit goal was to make something with CSS that looks as different as possible in each (current/recent) browser. So far you're winning "most cursed"

Tak Tran Yes, there is one nasty limitation in WebKit — it only gives you events for the fingers or the pen, not both at once, and it doesn't give you much info from each of them. So our Swift wrapper forwards full-fidelity, low latency pencil (at 240hz) and touch (at 120hz), with all the fanciness (tilt angle, barrel roll, pressure, etc) across to the JS context. We've been using this technique since back in Crosscut/Inkling, and I recently rewrote the project to be much simpler (a single Swift file). Hoping to pull it out into its own repo and share it with a little write up. We'll see. Either way, it's great for iPad prototyping, and I encourage everyone to play around with it!

FOR THOSE WHO WONDER WHAT THE HELL THIS IS

Alex Warth and I presented Inkling at LIVE 2024 yesterday, a project we created last year (also with Marcel Goethals, who presented his own wonderful project Subsequently at LIVE).

We've answered the question of how the podcast audio editing carries over to an academic conference talk

Ivan Reese oh do post it if you pull it out as a library. That would be a great tool to play with. Otherwise I'll prob reverse engineer it from your repo 😅 Thanks for sharing the code!

sorry it doesn't let me remove the broken embed on mobile slack app

thank you ivan

Really great talk! Sad not to make it in-person but am enjoying catching up with the talks and hope this kind of discussion can carry on in the live programming conference in barcelona

Actually it might be worth sharing this in the Future of Programming slack.

Two things. It’s not a generic but meta visual programming. Since meta implies that the devs can implement programming language on top of it.

It would be better to make it compatible with the editors and current programming language tech stacks. To easily visualize the debug flow. The way you put requires developers to learn a new tech. It’s not a deal for a lot of people. I am saying it if you want to get it popular

Thanks for your feedback! I am not sure about "generic vs meta" here , but I am going to think about it. You could be right though.

I am planning to make at least a vs.code extension but also other ways of at least easily using it in modern frontend stacks (or a subset of that) and maybe a simple implementation for c#/.net if I can find the time.

But a visual debugger for current programming languages is not the plan if that is what you meant. Creating a tool that will be popular is not the goal. Maybe that will happen one day, who knows, but not in the tools current state 😊. I hope to at least contribute something meaningful and positive to the development of visual programming tools

Demo at 2:00 looks pretty Hest-complete (-; Ivan Reese): valus traveling along edges + time rewinding slider 👏

For that specific feature Hest was for sure an inspiration but I am sure it's not Hest-complete 😊

Yeah, Code Flow Canvas is exploring lots of different ideas that aren't in Hest, and Hest is exploring stuff like bidirectional execution and, like, weird pointless bullshit because that's arty and I like arty. Glad we have both, and they can learn from each other.

Yes, I agree and I also do believe that there's future in visual programming although we might have not found the perfect/best way yet

We should all just keep exploring 😄

Interesting! Just a few days ago, I wrote a blog post saying that I'd like to have a module system in which each module's submodules are entirely independent of other (sub)modules in the system. If I understand your post correctly, miqula is such a system.

Yes. A miqula module is really more like a cache, which can be imported an directly used, but not edited, not "dived into*, can't even copy function contents out of it. I think it works great if it's closed like that, it gives a clear separation. Hopefully this also leads to better design. And you can always look into a module by closing miqula and opening the corresponding package file. If I read your blog correctly, you kind of want both of it. Closed (locked) and being able to inspect it.

Good luck! And hopefully you have less or no streaming issues and off course..no echo 😊

I opted for pre-recording my talk, so at least technical issues are limited to the Q&A session. I have yet to experience a remote presentation without any technical problems.

Good decision!

Judging from the few talks I saw with either remote speakers involved or done completely remote, there’s a good chance it’ll work smoothly. I know, surprising. Fingers crossed and good luck!

it was and went great, well done!