00:29 <UltimateCodeWarr> So I would like to make a street sign, or a stencil for one.  Of course the printer can only handle 8"x8".  So I would have to tile the stencil up and then piece it back together somehow.   Has anyone ever done anything like that?

00:31 <UltimateCodeWarr> Shooting from the hip:  I was thinking about some sort of horizontal (on spaces between textual lines) track/snap/zip tongue and grove type system to snap the tiles back together.  And then spray paint over it

00:49 <kintel> JordanBrown I've reviewed the objects PR. Once you're happy from your side, please just click Approve. Once I see the green flag I'll merge when my comments are addressed.

01:16 <gbruno> [github] marcuserronius opened issue #6015 (Support for OpenType features in code editor) https://github.com/openscad/openscad/issues/6015

02:22 <JordanBrown> UltimateCodeWarr people have done that. My personal couple of examples I just butt-glued the pieces together.

02:22 <JordanBrown> BOSL2 has a couple of functions to support cutting with jigsaw or dovetail connectors: https://github.com/BelfrySCAD/BOSL2/wiki/partitions.scad

02:39 <gbruno> [github] kintel edited issue #6013 (Manifold union result not convertible to Nef polyhedron via Surface_mesh) https://github.com/openscad/openscad/issues/6013

08:13 <bitbasher> hey code writing people .. this bit for the import() module ... Parameters::parse(std::move(arguments), inst->location(), {"file", "layer", "convexity", "origin", "scale"}, {"width", "height", "filename", "layername", "center", "dpi", "id"} );

08:15 <bitbasher> that is two structures with parameters ... first {file etc, .. then {width etc .. why are there 2? and what is the inst->location() doing ? is that the location that the imported object should be created at?

11:40 <bitbasher> me again .. the code shows that a .nef3 format can be imported .. but i can't find anything about that format .. what, please, is it related to?

11:41 <bitbasher> ah .. expanding my search shows a .nef format .. a Nikon proprietary RAW image format .. is that it?

11:55 <bitbasher> and .. the AMF format is marked "deprecated" but is actually the evolution of the STL format so .. still in use? or not

12:02 <Guest79> / Basic Belt Drive Sketch (OpenSCAD)

12:02 <Guest79> / Driver pulley diameter = 150 mm

12:02 <Guest79> / Driven pulley diameter = 300 mm

12:02 <Guest79> / Center distance = 1000 mm

12:02 <Guest79> / Belt shown as a simple loop around pulleys

12:02 <Guest79> $fn = 100; // smoothness

12:02 <Guest79> / Parameters

12:02 <Guest79> driver_dia = 150;

12:02 <Guest79> driven_dia = 300;

12:02 <Guest79> center_dist = 1000;

12:02 <Guest79> belt_thickness = 10;

12:02 <Guest79> belt_width = 15;

12:02 <Guest79> / Calculate pulley radii

12:02 <Guest79> driver_rad = driver_dia / 2;

12:02 <Guest79> driven_rad = driven_dia / 2;

12:02 <Guest79> / Positions of pulleys

12:02 <Guest79> driver_pos = [0, 0, 0];

12:03 <Guest79> driven_pos = [center_dist, 0, 0];

12:03 <Guest79> translate([driver_pos[0] + driver_rad, -belt_width - 2, belt_thickness/2])

12:03 <Guest79>     cube([center_dist - driver_rad - driven_rad, belt_width, belt_thickness], center=false);

12:03 <Guest79> / Arcs to connect (approximate)

12:03 <Guest79> translate(driver_pos)

12:03 <Guest79>     rotate([0,0,90])

12:03 <Guest79>         belt_arc([0,0,0], driver_rad, 0, angle_contact);

12:03 <Guest79> translate(driven_pos)

12:03 <Guest79>     rotate([0,0,-90])

12:03 <Guest79>         belt_arc([0,0,0], driven_rad, 180 - angle_contact, 180);

12:37 <kintel> bitbasher: I believe the first list is for positional parameters, while the second list can only be specified using key=value

12:38 <kintel> The loc is the source code location of the user's code being parsed, for e.g. error reporting

12:40 <kintel> .nef3 is a file format used for CGAL Nef polyhedron I/O - it's really only meant as a debugging tool to help building test cases for CGAL issues for upstream reporting.

12:55 <kintel> teepee, InPhase, guso78 & al: Inspired by a new contributor collaborating with Jordan to agree on a object feature subset, it looks like we'll try to fast-forward object creation as an experimental feature: https://github.com/openscad/openscad/pull/6012

12:56 <kintel> Please give it a spin post merge and be liberal with writing up GitHub tickets if you see something. I expect there to be some post-merge cleanup opportunities

12:57 <kintel> I'm hoping to get some people using this to help evaluate the opportunity for this to making it into the next release, but I'd like a bit more certainty about both the current feature set and potential extensions before committing. It is a pretty isolated feature though, so the risk should be limited.

13:48 <gbruno> [github] pkriens synchronize pull request #6012 (object function from #4337) https://github.com/openscad/openscad/pull/6012

13:59 <bitbasher> so .. anyone know what a .nef3 file format is?

14:10 <kintel> bitbasher I answered above :)

14:20 <bitbasher> drat .. i missed it, sorry kintel .. i did eventually find it in the CGAL docs on Nef Polygons .. thanks for the info!

14:21 <bitbasher> ah .. scrolling back i do not see your answer .. maybe came in while i was logged out of the channel

14:36 <gbruno> [github] pkriens synchronize pull request #6012 (object function from #4337) https://github.com/openscad/openscad/pull/6012

14:53 <kintel> bitbasher check the logs: https://libera.catirclogs.org/openscad/2025-07-08

14:54 <kintel> In general, it's always good to scroll through (or search your handle) in the logs, as people may answer very asynchronously

15:00 <InPhase> kintel: Awesome. I tried to help coordinate with Jordan on that, but then had a big chunk of things explode in the life on the other side of the computer screen, so my apologies that I never did the follow-ups on that project which I had planned on doing. But I'm glad someone else has picked it up, because I continue to think it's important.

15:01 <InPhase> Also apologies to JordanBrown for all those "Yeah, I'll take a look at that soon"s that got deferred indefinitely. (Along with a large pile of things that got deferred indefinitely.)

15:03 <InPhase> I'm still working my way back to something resembling schedule normalcy from like 3 years ago, and only actually getting close around now.

15:09 <bitbasher> kintel: i guess i am into "dead horse" territory but .. search the log and scrollback as i might i cannot find a response from you on the topic of the .nsf3 file format .. which is fine as i did find the info i needed

15:09 <bitbasher> just letting you know in case there is some IRC issue messing around with me

15:19 <kintel> bitbasher Did you follow the link I posted. It should be there, at 12:40 today

19:32 <JordanBrown> bitbasher: kintel said: .nef3 is a file format used for CGAL Nef polyhedron I/O - it's really only meant as a debugging tool to help building test cases for CGAL issues for upstream reporting.

20:17 <bitbasher> kintel: for me there is nothing in the scroll back between 10:40 and 1:03 today .. i see nothing at 12:40 . from anyone

20:19 <JordanBrown> https://libera.catirclogs.org/openscad/2025-07-08 at 12:40. I don't know what TZ that is, but it isn't Pacific so it's probably not cleverly picking up my browser's TZ.

20:20 <JordanBrown> It's the third message down from a large block by Guest79.

20:21 <JordanBrown> In that log, it's approximately 24 messages (not lines) above this message.