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:

OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org

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:

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:

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

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:

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:

OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org

On 16.08.23 21:26, jon wrote:

I'd point to http://www.guenther-sohler.net/openscad/ for that.

• 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

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:

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

OpenSCAD mailing list
To unsubscribe send an email todiscuss-leave@lists.openscad.org