00:04 <peepsalot> linext: all 3d stuff in browser is WebGL

00:05 <linext> what's the difference between WebGL and OpenGL?

00:07 <peepsalot> webgl is based on OpenGL ES, which is designed for mobile devices. https://www.khronos.org/webgl/wiki/WebGL_and_OpenGL_Differences

00:09 <peepsalot> for openscad, we can't really do ES yet, mainly because of OpenCSG preview, and reliance on a lot of the (VERY) old style of "fixed function pipeline", as opposed to shader based graphics

00:10 <peepsalot> OpenGL ES is an “embeddable subset” of OpenGL. It slims down the rather large OpenGL API to the bare essentials, so that it can be implemented on devices with simpler, cheaper hardware, and above all, low enough power requirements to run on batteries.

00:11 <peepsalot> so ES doesn't support legacy fixed function stuff which our codebase still uses in many places

00:14 <peepsalot> and webgl is even less feature filled than ES, since its specifically designed to run inside a browser

00:15 <peepsalot> linext: check out https://www.shadertoy.com/ for some fun eye candy and other examples of what can be done in webGL

00:18 <linext> wow

00:19 <linext> reminds me of openprocessing.org

00:19 <linext> https://openprocessing.org/discover/#/shader

01:51 <InPhase> JordanBrown: Oh. That bezier curve feature of the paths tool plus "stroke path" does in fact do a good job of curves. I guess they do support this now, and I just didn't notice. :) Thanks for the tip.

01:52 <InPhase> Perhaps my next quick triangle breakdown of an OpenSCAD design will be prettier.

02:50 <JordanBrown> Well, I should hope so!

10:21 <crazy_imp> what is the best way to "trace" parts to make a model? i need to make some case parts and i already put the old ones on the flatbed scanner (so i have a nice reference)

10:25 <J1A847854> crazy_imp  create an svg via inkscape  -  or use blender and background image

10:26 <J1A847854> if your case sides are flat .. just measure them and create the parts in openSCAD

10:27 <crazy_imp> J1A847854: good point with tracing it in inkscape first, then i can simply import and extrude it :)

10:27 <J1A847854> maybe look at polygons if the shape is not just a square.

10:29 <crazy_imp> it's a bit more complex compared to a square, but not too bad - https://i.imgur.com/RZLmr7B.jpg

10:29 <J1A847854> im using the "fill bucket"  in inkscape to re create areas of an image by color

10:29 <crazy_imp> time to clean it up and vectorize it

10:30 <J1A847854> if you have coordinates of the corner points .. use the polygon and offset

11:26 <crazy_imp> J1A847854: thanks for the hint with tracing it first - created a path in gimp, exported it as svg and extruded it. now i'm waiting for a test print to check the physical fit before continuing with it :)

18:48 <peepsalot> teepee: after the big beautify run, do you think there is a reason to keep the clang format script option + config file? as opposed to uncrustify?

18:49 <peepsalot> are we sure the two configs are in sync even?

19:30 <teepee> peepsalot: yeah, good point, I suppose they are not in sync, so dropping the unused one makes a lot of sense

22:52 <JordanBrown> I don't remember whether I did it with Inkscape or CorelDraw, but what I did once was to import an image, get it scaled correctly so that it matched the coordinate system, then drew over it with the drawing tools until it matched well enough, then read off the coordinates and transferred them into

22:52 <JordanBrown> OpenSCAD. (I suppose that I could have just import

22:52 <JordanBrown> ed the SVG, but that didn't really work well for the purpose - for one thing, various components were at different Z values.) It helps to have a Bézier function available.