I'm OK with the python stuff, because it shows a different way to solve a problem. Dan On Wed, Aug 16, 2023 at 7:46 PM jon <jon@jonbondy.com> wrote: > I agree that this should be separate. Thanks for pointing this out. > > Jon > On 8/16/2023 1:44 PM, Michael Möller wrote: > > Well, that question should be debated in its own thread/subj:-line. > > I feel we have 3 subject areas: > 1) The "pure" OpenSCAD usage questions: syntax, funktion, getting data > in&out, versions, bugs ... > 2) The "add ons" - BOSL2 and Sanjeev's python frontend. > 3) Hardware related- ie on how to get a physical implementation of a model. > The list could be subdivided a bit further. > > IMHO the list should restrict itself to 1. The occasional hardware > question is not a problem, but it gets a bit strained in that many OpenSCAD > questions are answered with "use this instead". Admittedly, pure (and > simple) OpenSCAD can not solve all 3D model desires, but should that be a > problem? > > I found it nice to hear about BOSL2, but find longer problems irrelevant. > BOSL2 is bigger than OpenSCAD in the number of features and functions, i.e. > it is like a new language (perhaps like C++ is "just" an extension of C ?) > Sanjeev's python work is also a new language which only uses OpenSCAD as a > render, as it produces one large polyhedra. Fantastic, but has almost > nothing to do with OpenSCAD. > > Msquare > > > > > On Wed, 16 Aug 2023 at 18:52, jon <jon@jonbondy.com> wrote: > >> How do the forum members feel about postings like this, which have more >> to do with python than with OpenSCAD? I personally find it to be >> unnecessary and distracting, but I will defer to the feelings of the group. >> >> Jon >> >> >> On 8/16/2023 12:22 PM, Sanjeev Prabhakar wrote: >> >> openscad version >> [image: Screenshot 2023-08-16 at 9.44.44 PM.png] >> >> #python code to create this: >> >> from openscad1 import * >> sec=circle(25) >> path=cr(pts1([[0,0,0],[0,15,1],[-6,50,1],[0,18,0]]),10) >> sol=prism(sec,path) >> sol1=prism(circle(24),path) >> sol0=swp_prism_h(sol,sol1) >> sec2=circle(15) >> path2=cr_3d([[0,0,15,0],[-60,0,40,20],[0,0,30,0]],10) >> sol2=path_extrude_open(sec2,path2) >> sol3=path_extrude_open(offset(sec2,-1),path2) >> sol02=swp_prism_h(sol2,sol3) >> fillet1=ip_fillet(sol,sol2,3,3) >> >> sec3=cr(pts1([[0,0],[-2,1,.2],[2,1]]),10) >> path3=helix(14,2.5,6,5) >> sol4=path_extrude_open(sec3,path3) >> >> sol4=sol2vector([0,0,1,],sol4,[-60,0,70]) >> with open('/Users/sanjeevprabhakar/iCloud Drive >> (Archive)/Documents/Download/openscad/trial.scad','w+') as f: >> f.write(f''' >> difference(){{ >> {swp_c(sol0)} >> {swp(sol3)} >> }} >> difference(){{ >> {swp_c(sol02)} >> {swp(sol)} >> }} >> {swp_c(fillet1)} >> intersection(){{ >> color("blue"){swp(sol4)} >> {swp(sol3)} >> }} >> >> ''') >> >> #for this code to work you would need file openscad1.py >> >> >> _______________________________________________ > OpenSCAD mailing list > To unsubscribe send an email to discuss-leave@lists.openscad.org >

Torsten: Can you elaborate on "there's going to be some native Python support" please?  Could we also add support for Modula 2 and Algol? I'm trying to understand where the lines are being drawn, and why. Jon On 8/16/2023 3:14 PM, Torsten Paul wrote: > There is simple way of subdividing the mailing list, reasonable > mail clients should be able to suppress unwanted threads though. > > I'm still trying to figure out if there's anything we could self- > host that could bring back the combined forum/mail usage we had > earlier. Maybe the new fediverse apps (Lemmy/Kbin...) bring some > new options to the table... > > Declaring a strict "pure OpenSCAD" policy seems both too limited > and also difficult to enforce anyway. > > Declaring BOSL2 or any library off-topic is just wrong in my > personal opinion. It does not get more OpenSCAD related than that. > > The python topic is debatable, especially in it's current form, > but considering there's going to be some native Python support > it could become much more integrated / native soon. > > In summary, I'm seeing all 3 topics in the on-topic category, > maybe with the hope the hardware topics would not take a too > big percentage. > > ciao, >   Torsten. > _______________________________________________ > OpenSCAD mailing list > To unsubscribe send an email to discuss-leave@lists.openscad.org

On 16.08.23 21:26, jon wrote: > Can you elaborate on "there's going to be some native Python > support" please? I'd point to http://www.guenther-sohler.net/openscad/ for that. > Could we also add support for Modula 2 and Algol? > I'm trying to understand where the lines are being drawn, and why. - Language widely in demand - Someone (else) doing the actual work (Thanks Günther!) - Language supports "easy" integration into a C++ application So without much analysis, my judgement would look something like: Modula 2 - no Algol - no Tcl - no Lua - probably not Lisp/Scheme - maybe? JavaScript - well...? Also it's extremely unlikely *now* while the python support is still moving towards integration. It's going to be another option, in addition to the "normal" SCAD. The code changes implementing the python support are surprisingly small as it's using all the geometry infrastructure that exists for SCAD. The bigger challenge are more the build, deployment and release topics. For further discussion, lets maybe create a new dedicated topic / mail thread ;-). Or use the one from a couple of days ago, where Sanjeev was asking for "python support for openscad". ciao, Torsten.

Personally I don't care what gets discussed on the list as long as it is related to OpenSCAD or 3D printing in some way. I have a fully functional delete key so anything that doesn't interest me is gone very quickly. On Wed, 16 Aug 2023 at 20:51, Torsten Paul <Torsten.Paul@gmx.de> wrote: > On 16.08.23 21:26, jon wrote: > > Can you elaborate on "there's going to be some native Python > > support" please? > > I'd point to http://www.guenther-sohler.net/openscad/ for that. > > > Could we also add support for Modula 2 and Algol? > > I'm trying to understand where the lines are being drawn, and why. > > - Language widely in demand > - Someone (else) doing the actual work (Thanks Günther!) > - Language supports "easy" integration into a C++ application > > So without much analysis, my judgement would look something like: > > Modula 2 - no > Algol - no > Tcl - no > Lua - probably not > Lisp/Scheme - maybe? > JavaScript - well...? > > Also it's extremely unlikely *now* while the python support is > still moving towards integration. > > It's going to be another option, in addition to the "normal" > SCAD. The code changes implementing the python support are > surprisingly small as it's using all the geometry infrastructure > that exists for SCAD. The bigger challenge are more the build, > deployment and release topics. > > For further discussion, lets maybe create a new dedicated topic / > mail thread ;-). Or use the one from a couple of days ago, where > Sanjeev was asking for "python support for openscad". > > ciao, > Torsten. > _______________________________________________ > OpenSCAD mailing list > To unsubscribe send an email to discuss-leave@lists.openscad.org >

Turbo Pascal?

The main difficult part of this is the fillet between the tubes. That should be doable with `join_prism()` (see example 12) in rounding.scad. The curve of the smaller tube can be done either with turtle3d, or with `path_sweep()` in skin.scad. The threading, of course, is available in threading.scad. - https://github.com/BelfrySCAD/BOSL2/wiki/rounding.scad#functionmodule-join_prism - https://github.com/BelfrySCAD/BOSL2/wiki/skin.scad#functionmodule-path_sweep - https://github.com/BelfrySCAD/BOSL2/wiki/threading.scad#module-threaded_rod I am unsure if `join_prism()` can use a cone as a base, though. Adrian, is there a way to do that? - Revar > On Aug 16, 2023, at 12:11 AM, Karl Exler <karl.exler@meinklang.cc> wrote: > > Dear all > I found the enclosed adapter on Thingiverse. Unfortunately nearly all diameters are not in that size I need it. Did anyone of you created such an (similar) object in Openscad? Is it possible to get that file? > Or- if not- how would an expert start with that projects? > > Until now I only use Openscad functions and some of the BOSL libraries. > > Many thanks in advance > Karl > <dewalt.png>_______________________________________________ > OpenSCAD mailing list > To unsubscribe send an email to discuss-leave@lists.openscad.org

On Wednesday, August 16, 2023 at 03:51:47 PM EDT, Torsten Paul <torsten.paul@gmx.de> wrote: >I'd point to http://www.guenther-sohler.net/openscad/ for that. Okay, trying to get that running, I installed: http://www.guenther-sohler.net/openscad/downloads/OpenSCAD-2023.04.25-x86-64-Installer.exe and edited my Windows System Environment variables to include: PYTHONHOME pointing at: C:\Users\willa\AppData\Local\Programs\Python\Python310 which contains: "C:\Users\willa\AppData\Local\Programs\Python\Python310\python310.dll" and rebooted. but when I try to run it I get: >The code execution cannot proceed because libpython3.10.dll was not found. Reinstalling the program may fix this problem." Unfortunately the similar question: https://superuser.com/questions/1422878/how-can-i-install-libpython-in-windows is unanswered. Apparently the recommendation is msys2 and a package in there --- which one? Why won't an extant Python 3.10 install serve? Why can't the DLL just be included? William

Forums let people pose questions which are sidelines, and no one protests as long as the content is polite. Mailing lists create all these questions of what is appropriate for all, and effectively create an atmosphere of would-be censorship. On Wed, Aug 16, 2023 at 10:18 PM Father Horton <fatherhorton@gmail.com> wrote: > Turbo Pascal? > _______________________________________________ > OpenSCAD mailing list > To unsubscribe send an email to discuss-leave@lists.openscad.org >

just want to clarify on "nothing to do with openSCAD" I am only using python for calculating the vertices in space. polyhedron() is an openscad feature difference () is an openscad feature intersection () is an openscad feature hull() is an openscad feature Without the above, models cannot be made. It is not like an stl file import. Also it is not 1 large polyhedron, there are multiple of them. Thanks On Wed, 16 Aug, 2023, 11:14 pm Michael Möller, <private2michael@gmail.com> wrote: > Well, that question should be debated in its own thread/subj:-line. > > I feel we have 3 subject areas: > 1) The "pure" OpenSCAD usage questions: syntax, funktion, getting data > in&out, versions, bugs ... > 2) The "add ons" - BOSL2 and Sanjeev's python frontend. > 3) Hardware related- ie on how to get a physical implementation of a model. > The list could be subdivided a bit further. > > IMHO the list should restrict itself to 1. The occasional hardware > question is not a problem, but it gets a bit strained in that many OpenSCAD > questions are answered with "use this instead". Admittedly, pure (and > simple) OpenSCAD can not solve all 3D model desires, but should that be a > problem? > > I found it nice to hear about BOSL2, but find longer problems irrelevant. > BOSL2 is bigger than OpenSCAD in the number of features and functions, i.e. > it is like a new language (perhaps like C++ is "just" an extension of C ?) > Sanjeev's python work is also a new language which only uses OpenSCAD as a > render, as it produces one large polyhedra. Fantastic, but has almost > nothing to do with OpenSCAD. > > Msquare > > > > > On Wed, 16 Aug 2023 at 18:52, jon <jon@jonbondy.com> wrote: > >> How do the forum members feel about postings like this, which have more >> to do with python than with OpenSCAD? I personally find it to be >> unnecessary and distracting, but I will defer to the feelings of the group. >> >> Jon >> >> >> On 8/16/2023 12:22 PM, Sanjeev Prabhakar wrote: >> >> openscad version >> [image: Screenshot 2023-08-16 at 9.44.44 PM.png] >> >> #python code to create this: >> >> from openscad1 import * >> sec=circle(25) >> path=cr(pts1([[0,0,0],[0,15,1],[-6,50,1],[0,18,0]]),10) >> sol=prism(sec,path) >> sol1=prism(circle(24),path) >> sol0=swp_prism_h(sol,sol1) >> sec2=circle(15) >> path2=cr_3d([[0,0,15,0],[-60,0,40,20],[0,0,30,0]],10) >> sol2=path_extrude_open(sec2,path2) >> sol3=path_extrude_open(offset(sec2,-1),path2) >> sol02=swp_prism_h(sol2,sol3) >> fillet1=ip_fillet(sol,sol2,3,3) >> >> sec3=cr(pts1([[0,0],[-2,1,.2],[2,1]]),10) >> path3=helix(14,2.5,6,5) >> sol4=path_extrude_open(sec3,path3) >> >> sol4=sol2vector([0,0,1,],sol4,[-60,0,70]) >> with open('/Users/sanjeevprabhakar/iCloud Drive >> (Archive)/Documents/Download/openscad/trial.scad','w+') as f: >> f.write(f''' >> difference(){{ >> {swp_c(sol0)} >> {swp(sol3)} >> }} >> difference(){{ >> {swp_c(sol02)} >> {swp(sol)} >> }} >> {swp_c(fillet1)} >> intersection(){{ >> color("blue"){swp(sol4)} >> {swp(sol3)} >> }} >> >> ''') >> >> #for this code to work you would need file openscad1.py >> >> On Wed, 16 Aug 2023 at 14:29, Sanjeev Prabhakar <sprabhakar2006@gmail.com> >> wrote: >> >>> This seems to me as quite a simple case although haven't tried it yet. >>> >>> As per my understanding it should be easy to do with BOSL library. May >>> be Adrian can comment. >>> >>> If you want, I can make it through my python approach. >>> >>> It is mainly 2 tubes which needs to be fused together and some easy >>> filleting. >>> >>> Threads parts maybe a little tricky, but not too difficult for sure. >>> >>> >>> >>> >>> On Wed, 16 Aug, 2023, 12:42 pm Karl Exler, <karl.exler@meinklang.cc> >>> wrote: >>> >>>> Dear all >>>> I found the enclosed adapter on Thingiverse. Unfortunately nearly all >>>> diameters are not in that size I need it. Did anyone of you created >>>> such >>>> an (similar) object in Openscad? Is it possible to get that file? >>>> Or- if not- how would an expert start with that projects? >>>> >>>> Until now I only use Openscad functions and some of the BOSL libraries. >>>> >>>> Many thanks in advance >>>> Karl >>>> _______________________________________________ >>>> OpenSCAD mailing list >>>> To unsubscribe send an email to discuss-leave@lists.openscad.org >>>> >>> >> _______________________________________________ >> OpenSCAD mailing list >> To unsubscribe send an email to discuss-leave@lists.openscad.org >> >> _______________________________________________ >> OpenSCAD mailing list >> To unsubscribe send an email to discuss-leave@lists.openscad.org >> >

The scope and richness of BOSL2 always amazes me.  It is more than I can keep in my head.  Thanks for the extensive documentation and examples. Jon On 8/16/2023 4:51 PM, Revar Desmera wrote: > The main difficult part of this is the fillet between the tubes.  That > should be doable with `join_prism()` (see example 12) in > rounding.scad.  The curve of the smaller tube can be done either with > turtle3d, or with `path_sweep()` in skin.scad. The threading, of > course, is available in threading.scad. > > - > https://github.com/BelfrySCAD/BOSL2/wiki/rounding.scad#functionmodule-join_prism > - > https://github.com/BelfrySCAD/BOSL2/wiki/skin.scad#functionmodule-path_sweep > - > https://github.com/BelfrySCAD/BOSL2/wiki/threading.scad#module-threaded_rod > > I am unsure if `join_prism()` can use a cone as a base, though. >  Adrian, is there a way to do that? > > - Revar > > > >> On Aug 16, 2023, at 12:11 AM, Karl Exler <karl.exler@meinklang.cc> wrote: >> >> Dear all >> I found the enclosed adapter on Thingiverse. Unfortunately nearly all >> diameters are not in that size I need it. Did anyone of you created >> such an (similar) object in Openscad? Is it possible to get that file? >> Or- if not- how would an expert start with that projects? >> >> Until now I only use Openscad functions and some of the BOSL libraries. >> >> Many thanks in advance >> Karl >> <dewalt.png>_______________________________________________ >> OpenSCAD mailing list >> To unsubscribe send an email to discuss-leave@lists.openscad.org > > > _______________________________________________ > OpenSCAD mailing list > To unsubscribe send an email todiscuss-leave@lists.openscad.org