guerd has quit [Read error: Connection reset by peer]
akash_ has quit [Quit: Client closed]
hyperair has joined #openscad
SamantazFox has quit [Killed (NickServ (GHOST command used by SamantazFox_))]
SamantazFox_ has joined #openscad
mtm has quit [Ping timeout: 252 seconds]
hyperair has quit [Read error: Connection reset by peer]
mtm has joined #openscad
<InPhase>
J25k8: Very impressive... Not even a renderer with sdf. He goes straight to the image representation by equation form.
<InPhase>
J25k8: It'd be nice if he'd drop the source code somewhere.
<InPhase>
I see he's well known for this, including an entry on ams.org, where he mentions "running a program on a Linux operating system", but I don't see the source.
<InPhase>
There's a github page by someone else marked as "Note: Previously this package contained functions for generating data from parametric equations discovered by the mathematical artist Hamid Naderi Yeganeh. ... To ensure that I do not inadvertently receive credit for Hamid's work and out of respect for the artist I have removed any functions and plots derived from his equations"
<InPhase>
They're very long equations though. I'm not about to try to type them in from an image like that to check them. :)
<kintel>
Those images essentially look like shadertoy raymarching shaders expressed as math instead of GLSL. I would assume he built a tool to convert from GLSL_like code to MathML :)
<InPhase>
teepee: In a better world, programs would get an error message specific to "flatpak blocked that" or similar, so this could be passed along to users, and people would stop blaming programs for their security buckets blocking stuff.
<InPhase>
There are legitimate reasons for these blocks to exist in general, but it creates confusion when they are non-informative blocks. This is a giant systems level issue in how these were setup and rolled out.
<InPhase>
Flatpak, snap, and apparmor all have this problem.
TheCoffeMaker has quit [Ping timeout: 244 seconds]
mmu_man has joined #openscad
<kintel>
What do people think about the extrusion/skin PR? It looks slightly challenging to pull together considering the for loop extension. Easy to add as experimental of course, but the big question is whether it will make it, how in interacts with other work and what competing longer-term work might happen
<teepee>
I have not looked at that loop thing, in general it seems like a useful feature that can stand on it's own, introducing 2.5d polygons would help with hull and maybe minkowski too
<teepee>
we discussed not long ago extrude is probably not the best name, skin seems to match better
<JordanBrown>
I thought skin and extrude were very different things. I thought skin took a bunch of caller-supplied shapes and sort-of-hulled them, while extrude took a single 2D shape and moved it along a path, perhaps transforming it along the way.
<teepee>
yep and that PR does skin
<JordanBrown>
OK. Haven't looked at it. But I thought that was the essence of the skin-vs-extrude thing, whether the input was a set of polygons (or points?), or a single polygon and a path and maybe transforms.
<JordanBrown>
So if it's a set of polygons (or points) and not a polygon-plus-path, then I totally agree that "skin" is the more correct name.
<JordanBrown>
Another test would be that I would think that it would be trivial to use a general-purpose extrude to implement linear extrude, and most of rotational extrude.
<JordanBrown>
(Not quite all of rotational extrude, because it has the magic of connecting the two ends.)
TheCoffeMaker has joined #openscad
TheCoffeMaker has quit [Ping timeout: 248 seconds]
TheCoffeMaker has joined #openscad
kintel has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
lastrodamo has quit [Quit: Leaving]
kintel has joined #openscad
<kintel>
Yeah, I agree that 2.5D objects and non-union for could be good "horizontal" features. ..and the skin PR is a good end-to-end example of how those two together can support a feature like skin().
kintel has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
kintel has joined #openscad
<kintel>
On the challenge side; we should probably integrate both 2.5D objects and non-union for loops across other features, or lock it down so that it cannot be accidentally used.