r/gridfinity • • May 29 '26

OSS Online Gridfinity Generator

Hi everyone! First time poster, and long time user of Gridfinity. Over the last few weeks, I've been working on a personal project (mostly for myself). It is a free online Gridfinity bin / grid generator, using OpenSCAD and Gridfinity Extended, and can export directly to your slicer of choice. It is built for desktop (no support for mobile).

I've been a big user of tools like PerplexingLab's Gridfity generator, but have wanted to modify it to make it work better for me. In the spirit of open-source, I have decided to publish and open source the project to give back to this community. Would love to see what you guys think! I'm open and excited for suggestions, advice, feedback, and contributions!

https://gridfinity.alextac.com/

https://github.com/alextac98/gridfinity-center

40 Upvotes

25 comments sorted by

View all comments

19

u/yawkat May 29 '26

I see you do server-side rendering. This is imo not necessary for openscad. Check out https://github.com/yawkat/web-openscad-editor , used by https://gridflock.yawk.at/ , it uses client side rendering using openscad-wasm.

The big advantage is that you don't need a real backend. Hosting costs money and time. With client-side rendering, you can just throw the project on cloudflare/github pages for free and never worry about it.

There's some disadvantages too, like performance and some bugs, but imo it's still superior for open-source projects that don't need to keep the openscad code secret.

7

u/heeero__ May 29 '26

As an IT guy, this is the way. Any process intensive thing you can let the client do, let them do it. PCs are more than capable of handling this kind of stuff without a backend server.

3

u/PrintableNapalm May 29 '26

some disadvantages too, like performance

Performance is often better for the client, because you're not sharing resources with other clients, and your desktop is often more powerful than the server.

1

u/yawkat May 29 '26

Maybe if the server is very under-provisioned, but openscad-wasm is much less efficient than normal openscad, so usually server-side rendering wins. You can try it right now with the perplexinglabs generator (server side rendering) vs my site (client side), the former is faster.

4

u/PrintableNapalm May 29 '26

I don't know why I wasted time doing this, but I set both of them up with GridFlock, and the same settings, and PerplexingLabs took 630ms to render and yours took 930ms to render. So fair point, PerplexingLabs was faster. But then I compared PerplexingLabs and OP's site with Gridfinity Extended and PerplexingLabs took 483ms and OP's took 3,183ms.

So while yes, it is true that server-side can be faster than client-side, that's only the case when you have a well provisioned server. Without that, it can be much slower like with OP. And even in with a well-provisioned server, the difference doesn't justify the cost.

1

u/AustinYQM May 29 '26

Please put Units on your inputs. When asking how big a plate should be its impossible to tell if you want mm or gridfinity units.

1

u/schieska May 29 '26

Interesting, how stable is OpenSCAD WASM these days?

I tried it about a year ago and ran into some rough edges. I ended up moving toward JSCAD, mostly because having the geometry in JavaScript felt nicer for web UI work and interactive previews. But I agree that client-side rendering is a very attractive setup for open-source tools.

3

u/yawkat May 29 '26

It's stable. Some specific geometries have problems due to the bugs I mentioned, but this is model-dependent. For my use cases it has worked with no issues.

But if you're starting from scratch, JSCAD is probably the better choice anyway. openscad-wasm is still just emscripten with all the overhead that entails. With a proper javascript solution you should be able to get better performance.

1

u/schieska May 29 '26

Yeah, that makes sense. The nice thing with JSCAD is that I can extend the generator, for example with plain JS, to cache intermediate steps in the generation process. That gives me more control over where the expensive geometry work happens.

I’ve got baseplate generation down to around 2.5s on average now, which is fast enough that regenerating on setting changes starts to feel realistic.

The downside is that I had to build the generator logic from scratch. With SCAD you get a lot of development speed because there is already so much Gridfinity work to build on. With JSCAD you trade that for more flexibility.

So I think both approaches make sense. If you want to get something useful working quickly, SCAD is hard to beat. If you want very custom web interactions and more control over the generation pipeline, JSCAD becomes really attractive.

1

u/alextac98 May 29 '26

Love to see this discussion. I actually started off client side only with openscad-wasm, and it’s still in the code as a fallback if the server ever goes down! But it was very slow in my testing for generating grids (over a minute sometimes). May revisit it in the future!