Jared (Jan 26 2024 at 18:38): Jared (Jan 26 2024 at 18:38):I'd like to make an SDL platform, where the main function accepts & returns a "State" type that is defined by the end-user programmer, not by the platform. I'm not really sure how to define the State type though; can I list a type in the requires part of the platform declaration?
(also is there documentation on the platform declaration syntax anywhere?)
Folkert de Vries (Jan 26 2024 at 19:10):I believe @Luke Boswell tried this somewhere. it is a bit like the elm architecture right?
Brendan Hansknecht (Jan 26 2024 at 19:18):roc-wasm4 and roc-ray both do this
Brendan Hansknecht (Jan 26 2024 at 19:20):You have to be care if you do a classic init, update, render though. Your render function if written the default way will free the model leading to future calls accessing already freed memory.
Luke Boswell (Jan 26 2024 at 19:53):I just wrote an article on how I developed roc-ray which goes into this in some detail. https://lukewilliamboswell.github.io/roc-ray-experiment/
Luke Boswell (Jan 26 2024 at 19:57):The way the platform is currently setup you can use tasks directly like setWindowSize etc, your not only providing a tree for things to render.
I think it should be pretty straightforward to swap out raylib for SDL if you want, though the libraries are very similar from what I can tell.
Jared (Jan 26 2024 at 20:22):nice!
Luke Boswell (Jan 26 2024 at 21:50):If your interested we could collaborate on roc-ray? Was there anything in particular you wanted to build with SDL?
Jared (Jan 26 2024 at 22:50):Sure! yeah raylib seems just as good, I'd be happy to hack on it
Jared (Jan 31 2024 at 18:29):@Luke Boswell checking out roc-ray -- the raylib submodule is referencing a commit that doesn't exist on the public raylib.zig repo, or on your fork. Is it something you just have locally?
Luke Boswell (Jan 31 2024 at 19:38):First time using git submodules... I thought I had pushed that commit. It's just a one liner to make something public I think. I'll have a look again and see if I can push it to my fork.
Luke Boswell (Jan 31 2024 at 19:47):I think I figured out the issue, I has pushed to main but the raylib repository uses master as the default. I've just pushed the commit to both branches on my fork now, so I hope that works. Can you let me know if you have any issues?
Jared (Jan 31 2024 at 20:49):hm the submodule is registered to the ryupold github link, not your fork
Jared (Jan 31 2024 at 20:53):ok after fixing that, checkout is working
Jared (Jan 31 2024 at 20:54):+ zig build
/Users/jared/clone/fork/roc-ray/build.zig:18:9: error: no field named 'force_pic' in struct 'Build.Step.Compile'
lib.force_pic = true;
^~~~~~~~~
/Users/jared/bin/zig-0.12/lib/std/Build/Step/Compile.zig:1:1: note: struct declared here
const builtin = @import("builtin");
error while building
Luke Boswell (Jan 31 2024 at 20:55):Are you running zig 0.11.0? otherwise Im not sure
Jared (Jan 31 2024 at 20:56):oh yeah 0.12. i just downloaded it
Jared (Jan 31 2024 at 20:58):ok 0.11
+ zig build
/Users/jared/clone/fork/roc-ray/build.zig:21:21: error: expected error union type, found 'void'
try raylib.addTo(b, lib, target, mode, .{
~~~~~~~~~~~~^
referenced by:
runBuild__anon_6734: /Users/jared/bin/zig-11/lib/std/Build.zig:1639:37
remaining reference traces hidden; use '-freference-trace' to see all reference traces
/Users/jared/clone/fork/roc-ray/raylib/build.zig:105:21: error: expected type '*Build.Step.Compile', found '@typeInfo(@typeInfo(@TypeOf(raylib.raylib.src.build.addRaylib__anon_13150)).Fn.return_type.?).ErrorUnion.error_set!*Build.Step.Compile'
exe.linkLibrary(lib_raylib);
^~~~~~~~~~
/Users/jared/clone/fork/roc-ray/raylib/build.zig:105:21: note: cannot convert error union to payload type
/Users/jared/clone/fork/roc-ray/raylib/build.zig:105:21: note: consider using 'try', 'catch', or 'if'
/Users/jared/bin/zig-11/lib/std/Build/Step/Compile.zig:672:41: note: parameter type declared here
ah I see https://github.com/lukewilliamboswell/raylib/commit/7ca0edde71b7154f16b638a42003ea68283de4e5
Jared (Jan 31 2024 at 21:07):working!!!! nice
Jared (Jan 31 2024 at 21:20):now if I can get it all running on android, we'd really be cookin'
Jared (Jan 31 2024 at 21:30):How hard is it to send collections over the bridge? I think my ideal API would be to have a single task like "renderDrawables" where you send a list of shapes / text / etc and it draws them all, instead doing a ton of chained tasks.
Brendan Hansknecht (Jan 31 2024 at 21:51):Without glue it will probably be quite tedious. The collection isn't the hard part. The hard part is the tagged union type that can wrap anything that is drawable.
Luke Boswell (Jan 31 2024 at 21:59):Without glue for zig I imagine that would be cumbersome to write by hand. Definitely possible, just not ergonomic. If it's just small for a proof of concept or experiment I would. But if I wanted to change things and iterate I'd make a start on Zig glue instead.
Jared (Jan 31 2024 at 22:08):hmmm yeah that makes sense. I could get by with just a small handful of drawables, so maybe it wouldn't be too bad?
Jared (Jan 31 2024 at 22:09):on the other hand, I could make a layer on top of the imperative API in roc, and get the user experience I want
Brendan Hansknecht (Jan 31 2024 at 23:12):That probably would be much easier to do and what I would advise for now.
Luke Boswell (Feb 01 2024 at 00:07):Yeah, should be pretty easy actually if we do it in the platform layer. So in e.g. platform/main.roc.
Jared (Feb 01 2024 at 03:25):pong.mp4
solitaire pong :)
Luke Boswell (Feb 01 2024 at 04:15):That's awesome. Did you have to make many modifications to get that working?
Jared (Feb 01 2024 at 04:40):Nope! Made a PR with the code
Luke Boswell (Feb 03 2024 at 02:19):@Jared what do you think of this? https://github.com/lukewilliamboswell/roc-ray/pull/2
Luke Boswell (Feb 03 2024 at 02:20):I added a Drawable ability to see how that might feel for an API.
Luke Boswell (Feb 03 2024 at 02:21):render : Model -> Task Model []
render = \_ ->
shapes = [
Shape2D.rect { posX: 10, posY: 50, width: 200, height: 50, color: white },
Shape2D.rectGradientV { posX: 10, posY: 150, width: 200, height: 50, top: white, bottom: blue },
Shape2D.text { text: "Hello World", posX: 10, posY: 250, size: 20, color: white },
Shape2D.circle { centerX: 300, centerY: 100, radius: 50, color: red },
Shape2D.circleGradient { centerX: 300, centerY: 200, radius: 35, inner: red, outer: blue },
]
_ <- shapes |> Task.forEach draw |> Task.await
Task.ok {}
Looks neat!
Last updated: Jul 26 2025 at 12:14 UTC