Thank you for your opinion, Willy,
I know your tutorial, and it has helped me very well in learning to use LSYNTH.
Maybe I can weaken my suggestion a little:
For many flexible parts, its constituent components are anyway available in our library:
Example 1: electric cable: http://www.ldraw.org/cgi-bin/ptdetail.cg...567c03.dat
The ends are plug parts plus cable end.
The flexible portion is made from sweeping x993.dat
Example 2: hose: http://www.ldraw.org/cgi-bin/ptdetail.cg...rts/75.dat
1 subpart for the end and beginning,
and the flexible portion made by sweeping s/75s01.dat
After some more thinking, I agree with you that the lsynth tool itself, or its helper / constraint files
are maybe a separate project, and need an independent release cycle.
However, the real goal of my suggestions above is just to
standardize about how these constituent elements are structured within our library.
And for that standardization, a way which would be directly usable by LSYNTH would be the optimal solution in my eyes;
that solution especially is nice because the positioning I suggested match the cyli primitives.
I know your tutorial, and it has helped me very well in learning to use LSYNTH.
Maybe I can weaken my suggestion a little:
For many flexible parts, its constituent components are anyway available in our library:
Example 1: electric cable: http://www.ldraw.org/cgi-bin/ptdetail.cg...567c03.dat
The ends are plug parts plus cable end.
The flexible portion is made from sweeping x993.dat
Example 2: hose: http://www.ldraw.org/cgi-bin/ptdetail.cg...rts/75.dat
1 subpart for the end and beginning,
and the flexible portion made by sweeping s/75s01.dat
After some more thinking, I agree with you that the lsynth tool itself, or its helper / constraint files
are maybe a separate project, and need an independent release cycle.
However, the real goal of my suggestions above is just to
standardize about how these constituent elements are structured within our library.
And for that standardization, a way which would be directly usable by LSYNTH would be the optimal solution in my eyes;
that solution especially is nice because the positioning I suggested match the cyli primitives.