home.social

#openscad — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #openscad, aggregated by home.social.

  1. @tj Is there an open-source CAD program that has a GUI? That would help a lot, especially for kids transitioning from TinkerCAD to Fusion 360.

    #FreeCAD #OpenScad

  2. If you use CAD software and care about properly owning what you make:

    Do not use Onshape.

    Do not use Fusion360 (or any other Autodesk product).

    Using these tools binds your work to someone else's profit motives. You are a temporary guest in their house. They *will* fuck you over the moment they decide they can make more money by doing so.

    #freecad and #openscad are incredible tools. Learn them and become free.

    #foss

  3. Chcete důkaz, že všichni nosíme v kapse malý počítač? 😄

    #OpenSCAD #Android

  4. Chcete důkaz, že všichni nosíme v kapse malý počítač? 😄

    #OpenSCAD #Android

  5. Chcete důkaz, že všichni nosíme v kapse malý počítač? 😄

    #OpenSCAD #Android

  6. Chcete důkaz, že všichni nosíme v kapse malý počítač? 😄

    #OpenSCAD #Android

  7. Chcete důkaz, že všichni nosíme v kapse malý počítač? 😄

    #OpenSCAD #Android

  8. 🎉 Wow, folks! This groundbreaking article reveals the earth-shattering news that Google Antigravity 2.0 can, in fact, build a virtual Pantheon model. 🏛️ As if #OpenSCAD wasn't already thrilling enough, now we have an entire lineup of AI tools competing to see who can model ancient architecture more efficiently—hold onto your seats! 🚀
    modelrift.com/blog/openscad-ll #GoogleAntigravity2.0 #VirtualPantheon #AItools #AncientArchitecture #HackerNews #ngated

  9. v0.94.0 introduced the element:

    Drop in your .scad code and get an interactive 3D viewer inline. Great for documentation, tutorials, and teaching parametric modeling.

    hyperbook.openpatch.org/elemen

  10. @ianp5a @LovesTha I've managed to mash-up a few designs (like attaching #gridfinity bases to existing designs) in #tinkercad but so far my experiences with #freecad have been frustrating. I suspect once there are more tutorials for the latest release that will help but for a novice like me tinkercad works really well. The advantage of adding the handles to a parametric baseplate in #openscad was I didn't have to redo for each grid layout.

  11. @ianp5a @LovesTha I've managed to mash-up a few designs (like attaching #gridfinity bases to existing designs) in #tinkercad but so far my experiences with #freecad have been frustrating. I suspect once there are more tutorials for the latest release that will help but for a novice like me tinkercad works really well. The advantage of adding the handles to a parametric baseplate in #openscad was I didn't have to redo for each grid layout.

  12. @ianp5a @LovesTha I've managed to mash-up a few designs (like attaching #gridfinity bases to existing designs) in #tinkercad but so far my experiences with #freecad have been frustrating. I suspect once there are more tutorials for the latest release that will help but for a novice like me tinkercad works really well. The advantage of adding the handles to a parametric baseplate in #openscad was I didn't have to redo for each grid layout.

  13. @ianp5a @LovesTha I've managed to mash-up a few designs (like attaching #gridfinity bases to existing designs) in #tinkercad but so far my experiences with #freecad have been frustrating. I suspect once there are more tutorials for the latest release that will help but for a novice like me tinkercad works really well. The advantage of adding the handles to a parametric baseplate in #openscad was I didn't have to redo for each grid layout.

  14. @ianp5a @LovesTha I've managed to mash-up a few designs (like attaching #gridfinity bases to existing designs) in #tinkercad but so far my experiences with #freecad have been frustrating. I suspect once there are more tutorials for the latest release that will help but for a novice like me tinkercad works really well. The advantage of adding the handles to a parametric baseplate in #openscad was I didn't have to redo for each grid layout.

  15. Excited to announce the new era of terminal apps! 🎉

    🐀 **ratSCAD** — CAD for the terminal!

    🧀 Terminal IDE for OpenSCAD with live 3D previews.

    🦀 Made possible by Ratty terminal: github.com/orhun/ratty

    ⭐ GitHub: github.com/qewer33/ratscad

  16. Working in code is much easier than trying to align and drop things with the #freecad tools. I need a better way cut out the excess though - some sort of plane operation? I think I'll use more #openscad in future. github.com/stsquad/gridfinity-

  17. Today I'm experimenting to see if I can avoid learning #freecad and instead just #vibe in #openscad to add handles to a #gridfinity baseplate.

  18. Today I'm experimenting to see if I can avoid learning #freecad and instead just #vibe in #openscad to add handles to a #gridfinity baseplate.

  19. Just designed and printed a vinyl record stand, but somehow something went wrong while printing 🤔

    #3dprinting #vinyl #OpenSCAD

  20. Just designed and printed a vinyl record stand, but somehow something went wrong while printing 🤔

    #3dprinting #vinyl #OpenSCAD

  21. Just designed and printed a vinyl record stand, but somehow something went wrong while printing 🤔

    #3dprinting #vinyl #OpenSCAD

  22. Just designed and printed a vinyl record stand, but somehow something went wrong while printing 🤔

    #3dprinting #vinyl #OpenSCAD

  23. Just designed and printed a vinyl record stand, but somehow something went wrong while printing 🤔

    #3dprinting #vinyl #OpenSCAD

  24. Modéliser vite-fait une pièce pour caler la caméra (dashcam) sur le vélo avec OpenSCAD.

    #OpenSCAD #Impression3D #3DPrint

  25. Modéliser vite-fait une pièce pour caler la caméra (dashcam) sur le vélo avec OpenSCAD.

    #OpenSCAD #Impression3D #3DPrint

  26. Modéliser vite-fait une pièce pour caler la caméra (dashcam) sur le vélo avec OpenSCAD.

    #OpenSCAD #Impression3D #3DPrint

  27. Modéliser vite-fait une pièce pour caler la caméra (dashcam) sur le vélo avec OpenSCAD.

    #OpenSCAD #Impression3D #3DPrint

  28. I did a thing in OpenSCAD! It’s a vertical laptop stand for work. I’m reasonably happy with it. I wish that I’d been able to figure out BOSL2’s texturing to get a pattern on the large front and back faces to make them slightly more visually interesting, but 🤷‍♂️.
    #OpenSCAD #3DPrint

  29. I did a thing in OpenSCAD! It’s a vertical laptop stand for work. I’m reasonably happy with it. I wish that I’d been able to figure out BOSL2’s texturing to get a pattern on the large front and back faces to make them slightly more visually interesting, but 🤷‍♂️.
    #OpenSCAD #3DPrint

  30. I did a thing in OpenSCAD! It’s a vertical laptop stand for work. I’m reasonably happy with it. I wish that I’d been able to figure out BOSL2’s texturing to get a pattern on the large front and back faces to make them slightly more visually interesting, but 🤷‍♂️.

  31. I did a thing in OpenSCAD! It’s a vertical laptop stand for work. I’m reasonably happy with it. I wish that I’d been able to figure out BOSL2’s texturing to get a pattern on the large front and back faces to make them slightly more visually interesting, but 🤷‍♂️.
    #OpenSCAD #3DPrint

  32. I did a thing in OpenSCAD! It’s a vertical laptop stand for work. I’m reasonably happy with it. I wish that I’d been able to figure out BOSL2’s texturing to get a pattern on the large front and back faces to make them slightly more visually interesting, but 🤷‍♂️.
    #OpenSCAD #3DPrint

  33. CW: Advice/opinions from visual art coders/pixel artists needed

    So, I'm working on a library that aims to recreate the experience of using #OpenSCAD but for #pixelart. I decided to use js because that is what I am familiar with.

    I'm between two approaches: one passes around images, so you are passing function results to transformation functions. This means you need an outside `draw()` function to draw the final image and a `merge()` function every time you need to combine images (just like in JSCAD union() is not implied).

    This looks like this
    draw(
    merge(
    translate([15,-5], merge(
    translate([20,20],p("black")),
    translate([31,31],p("black"))
    )),
    translate([21,21],rect([10,10],"black"))
    )
    )

    This implementation looks clean and I have a hunch that it will enable stuff like filtering or more complex image manipulation on the result of part of the pipeline.

    The other approach, uses canvas context to translate/rotate the origin around and back, so you pass functions around. This looks more like OpenSCAD and it simplifies the library code significantly (I don't need to create offscreen canvases for every new item) but it makes the drawing code very idiosyncratically js, i.e. full of various kinds of brackets.

    translate([15,-5],()=>{
    translate([20,20],()=>{p("black")});
    translate([34,34],()=>{p("black")});
    })
    translate([21,21],()=>{rect([10,10],"black")});

    I also have the feeling that with this approach I will at some point hit a wall because I will never really have an "instance" of a module/part/call-it-what-you-want. On the other hand, passing around code seems more versatile but I don't know why.

    What do you prefer as a user of this thing? What would you choose as the creator of the library? What's the best coding practice in your opinion?

    #creativeCoding

    If you have followers that might have some input, please boost.

  34. CW: Advice/opinions from visual art coders/pixel artists needed

    So, I'm working on a library that aims to recreate the experience of using #OpenSCAD but for #pixelart. I decided to use js because that is what I am familiar with.

    I'm between two approaches: one passes around images, so you are passing function results to transformation functions. This means you need an outside `draw()` function to draw the final image and a `merge()` function every time you need to combine images (just like in JSCAD union() is not implied).

    This looks like this
    draw(
    merge(
    translate([15,-5], merge(
    translate([20,20],p("black")),
    translate([31,31],p("black"))
    )),
    translate([21,21],rect([10,10],"black"))
    )
    )

    This implementation looks clean and I have a hunch that it will enable stuff like filtering or more complex image manipulation on the result of part of the pipeline.

    The other approach, uses canvas context to translate/rotate the origin around and back, so you pass functions around. This looks more like OpenSCAD and it simplifies the library code significantly (I don't need to create offscreen canvases for every new item) but it makes the drawing code very idiosyncratically js, i.e. full of various kinds of brackets.

    translate([15,-5],()=>{
    translate([20,20],()=>{p("black")});
    translate([34,34],()=>{p("black")});
    })
    translate([21,21],()=>{rect([10,10],"black")});

    I also have the feeling that with this approach I will at some point hit a wall because I will never really have an "instance" of a module/part/call-it-what-you-want. On the other hand, passing around code seems more versatile but I don't know why.

    What do you prefer as a user of this thing? What would you choose as the creator of the library? What's the best coding practice in your opinion?

    #creativeCoding

    If you have followers that might have some input, please boost.

  35. CW: Advice/opinions from visual art coders/pixel artists needed

    So, I'm working on a library that aims to recreate the experience of using #OpenSCAD but for #pixelart. I decided to use js because that is what I am familiar with.

    I'm between two approaches: one passes around images, so you are passing function results to transformation functions. This means you need an outside `draw()` function to draw the final image and a `merge()` function every time you need to combine images (just like in JSCAD union() is not implied).

    This looks like this
    draw(
    merge(
    translate([15,-5], merge(
    translate([20,20],p("black")),
    translate([31,31],p("black"))
    )),
    translate([21,21],rect([10,10],"black"))
    )
    )

    This implementation looks clean and I have a hunch that it will enable stuff like filtering or more complex image manipulation on the result of part of the pipeline.

    The other approach, uses canvas context to translate/rotate the origin around and back, so you pass functions around. This looks more like OpenSCAD and it simplifies the library code significantly (I don't need to create offscreen canvases for every new item) but it makes the drawing code very idiosyncratically js, i.e. full of various kinds of brackets.

    translate([15,-5],()=>{
    translate([20,20],()=>{p("black")});
    translate([34,34],()=>{p("black")});
    })
    translate([21,21],()=>{rect([10,10],"black")});

    I also have the feeling that with this approach I will at some point hit a wall because I will never really have an "instance" of a module/part/call-it-what-you-want. On the other hand, passing around code seems more versatile but I don't know why.

    What do you prefer as a user of this thing? What would you choose as the creator of the library? What's the best coding practice in your opinion?

    #creativeCoding

    If you have followers that might have some input, please boost.