HL
Hans L
Tue, Nov 19, 2019 4:35 PM
It seems like 3MF is being set up to take over from STL as the exchange
format for 3D printing. How difficult would it be for OpenSCAD to output
3MF?
It already does if you use a 2019 release.
On Tue, Nov 19, 2019 at 10:22 AM gasstationwithoutpumps <
karplus@soe.ucsc.edu> wrote:
> It seems like 3MF is being set up to take over from STL as the exchange
> format for 3D printing. How difficult would it be for OpenSCAD to output
> 3MF?
>
It already does if you use a 2019 release.
G
gasstationwithoutpumps
Tue, Nov 19, 2019 4:35 PM
Making OpenSCAD faster would be nice.
It seems like 3MF is being set up to take over from STL as the exchange
format for 3D printing. How difficult would it be for OpenSCAD to output
3MF?
Sent from: http://forum.openscad.org/
Making OpenSCAD faster would be nice.
It seems like 3MF is being set up to take over from STL as the exchange
format for 3D printing. How difficult would it be for OpenSCAD to output
3MF?
-----
gasstationwithoutpumps.wordpress.com
www.thingiverse.com/gasstationwithoutpumps/things
--
Sent from: http://forum.openscad.org/
C
corpsman
Tue, Nov 19, 2019 4:48 PM
It would be really cool, if the double click and snap to object feature
would be reeanabled under linux.
For further details:
http://forum.openscad.org/Center-by-double-click-on-a-part-on-2015-03-not-working-on-2019-05-td26881.html
https://github.com/openscad/openscad/pull/2466
NH
nop head
Tue, Nov 19, 2019 5:25 PM
I have never tried it but the source code says it should import AMF as well.
On Tue, 19 Nov 2019 at 17:21, gasstationwithoutpumps karplus@soe.ucsc.edu
wrote:
On Tue, Nov 19, 2019 at 10:22 AM gasstationwithoutpumps <
It seems like 3MF is being set up to take over from STL as the exchange
format for 3D printing. How difficult would it be for OpenSCAD to
It already does if you use a 2019 release.
I have never tried it but the source code says it should import AMF as well.
On Tue, 19 Nov 2019 at 17:21, gasstationwithoutpumps <karplus@soe.ucsc.edu>
wrote:
> thehans wrote
> > On Tue, Nov 19, 2019 at 10:22 AM gasstationwithoutpumps <
>
> > karplus@.ucsc
>
> >> wrote:
> >
> >> It seems like 3MF is being set up to take over from STL as the exchange
> >> format for 3D printing. How difficult would it be for OpenSCAD to
> output
> >> 3MF?
> >>
> >
> > It already does if you use a 2019 release.
>
> Thanks, I'd not noticed the addition to the export menu. It doesn't seem
> that the 3MF files can be imported, though, so this is still only partial
> support.
>
>
>
> -----
> gasstationwithoutpumps.wordpress.com
> www.thingiverse.com/gasstationwithoutpumps/things
> --
> Sent from: http://forum.openscad.org/
>
> _______________________________________________
> OpenSCAD mailing list
> Discuss@lists.openscad.org
> http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
>
DM
Doug Moen
Tue, Nov 19, 2019 5:33 PM
3MF import works for me. It's in version 2019.05.
On Tue, Nov 19, 2019, at 12:34 PM, gasstationwithoutpumps wrote:
On Tue, Nov 19, 2019 at 10:22 AM gasstationwithoutpumps <
It seems like 3MF is being set up to take over from STL as the exchange
format for 3D printing. How difficult would it be for OpenSCAD to output
3MF?
It already does if you use a 2019 release.
3MF import works for me. It's in version 2019.05.
On Tue, Nov 19, 2019, at 12:34 PM, gasstationwithoutpumps wrote:
> thehans wrote
> > On Tue, Nov 19, 2019 at 10:22 AM gasstationwithoutpumps <
>
> > karplus@.ucsc
>
> >> wrote:
> >
> >> It seems like 3MF is being set up to take over from STL as the exchange
> >> format for 3D printing. How difficult would it be for OpenSCAD to output
> >> 3MF?
> >>
> >
> > It already does if you use a 2019 release.
>
> Thanks, I'd not noticed the addition to the export menu. It doesn't seem
> that the 3MF files can be imported, though, so this is still only partial
> support.
>
>
>
> -----
> gasstationwithoutpumps.wordpress.com
> www.thingiverse.com/gasstationwithoutpumps/things
> --
> Sent from: http://forum.openscad.org/
>
> _______________________________________________
> OpenSCAD mailing list
> Discuss@lists.openscad.org
> http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
>
G
gasstationwithoutpumps
Tue, Nov 19, 2019 5:34 PM
On Tue, Nov 19, 2019 at 10:22 AM gasstationwithoutpumps <
It seems like 3MF is being set up to take over from STL as the exchange
format for 3D printing. How difficult would it be for OpenSCAD to output
3MF?
It already does if you use a 2019 release.
Thanks, I'd not noticed the addition to the export menu. It doesn't seem
that the 3MF files can be imported, though, so this is still only partial
support.
Sent from: http://forum.openscad.org/
thehans wrote
> On Tue, Nov 19, 2019 at 10:22 AM gasstationwithoutpumps <
> karplus@.ucsc
>> wrote:
>
>> It seems like 3MF is being set up to take over from STL as the exchange
>> format for 3D printing. How difficult would it be for OpenSCAD to output
>> 3MF?
>>
>
> It already does if you use a 2019 release.
Thanks, I'd not noticed the addition to the export menu. It doesn't seem
that the 3MF files can be imported, though, so this is still only partial
support.
-----
gasstationwithoutpumps.wordpress.com
www.thingiverse.com/gasstationwithoutpumps/things
--
Sent from: http://forum.openscad.org/
N
NateTG
Tue, Nov 19, 2019 5:51 PM
- Optimize existing code, make OpenSCAD faster
I haven't used OpenSCAD in a while, but "render" had a habit of taking an
unreasonable amount of time.
I really wanted "user land geometry." Ideally some kind of geometry object
that can include feature information as well as raw geometry information so
that "align on feature" stuff is relatively easy to implement.
- More / improved documentation
I don't know how much of my inability to get good use out of libraries was a
documentation issue and how much of it was a feature issue.
- Something else not mentioned
I'm not sure where annoyances with floating point and unreliable vertex
locations fit in. When I worked on beveled text generation, it was
something that I had to work around in an awkward fashion.
--
Sent from: http://forum.openscad.org/
> 2) Optimize existing code, make OpenSCAD faster
I haven't used OpenSCAD in a while, but "render" had a habit of taking an
unreasonable amount of time.
> 3) Addition of new features
I really wanted "user land geometry." Ideally some kind of geometry object
that can include feature information as well as raw geometry information so
that "align on feature" stuff is relatively easy to implement.
> 4) More / improved documentation
I don't know how much of my inability to get good use out of libraries was a
documentation issue and how much of it was a feature issue.
> 7) Something else not mentioned
I'm not sure where annoyances with floating point and unreliable vertex
locations fit in. When I worked on beveled text generation, it was
something that I had to work around in an awkward fashion.
--
Sent from: http://forum.openscad.org/
JB
Jordan Brown
Fri, Nov 22, 2019 6:00 PM
Here's a stupid little feature that I often want: a "clip" operator
that cuts away everything on one side of a plane.
Yes, you can do this with difference or intersection with a big cube,
but I find it ... aesthetically unpleasant ... to have to decide how big
the cube should be.
At its simplest (and probably as a default) it should just cut away
everything where Z<0, so
clip() sphere();
gives a half-sphere above Z=0.
That's enough, but for extra credit let the caller specify a normal
vector (as for mirror()), or for double extra credit a point and normal
vector so as to define a plane and an orientation.
Here's a stupid little feature that I often want: a "clip" operator
that cuts away everything on one side of a plane.
Yes, you can do this with difference or intersection with a big cube,
but I find it ... aesthetically unpleasant ... to have to decide how big
the cube should be.
At its simplest (and probably as a default) it should just cut away
everything where Z<0, so
clip() sphere();
gives a half-sphere above Z=0.
That's enough, but for extra credit let the caller specify a normal
vector (as for mirror()), or for double extra credit a point and normal
vector so as to define a plane and an orientation.
NH
nop head
Fri, Nov 22, 2019 8:14 PM
Here's a stupid little feature that I often want: a "clip" operator that
cuts away everything on one side of a plane.
Yes, you can do this with difference or intersection with a big cube, but
I find it ... aesthetically unpleasant ... to have to decide how big the
cube should be.
At its simplest (and probably as a default) it should just cut away
everything where Z<0, so
clip() sphere();
gives a half-sphere above Z=0.
That's enough, but for extra credit let the caller specify a normal vector
(as for mirror()), or for double extra credit a point and normal vector so
as to define a plane and an orientation.
OpenSCAD mailing list
Discuss@lists.openscad.org
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
I use this: https://github.com/nophead/NopSCADlib#Clip Not quite what you
want but it can clip against any plane perpendicular to one of the axes.
On Fri, 22 Nov 2019 at 18:01, Jordan Brown <openscad@jordan.maileater.net>
wrote:
> Here's a stupid little feature that I often want: a "clip" operator that
> cuts away everything on one side of a plane.
>
> Yes, you can do this with difference or intersection with a big cube, but
> I find it ... aesthetically unpleasant ... to have to decide how big the
> cube should be.
>
> At its simplest (and probably as a default) it should just cut away
> everything where Z<0, so
> clip() sphere();
> gives a half-sphere above Z=0.
>
> That's enough, but for extra credit let the caller specify a normal vector
> (as for mirror()), or for double extra credit a point and normal vector so
> as to define a plane and an orientation.
> _______________________________________________
> OpenSCAD mailing list
> Discuss@lists.openscad.org
> http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
>
RD
Revar Desmera
Fri, Nov 22, 2019 8:19 PM
I have to upvote this one. It’d be stupid simple, and I could use it to better implement the front_half(), left_half(), etc modules in my library.
Another language request that’s make my life easier would be a way to assign multiple variables from elements of a list.
a, b, c = func_returning_three_item_list();
Instead of having to write:
foo = func_returning_three_item_list();
a = foo[0];
b = foo[1];
c = foo[2];
On Nov 22, 2019, at 10:08 AM, Jordan Brown openscad@jordan.maileater.net wrote:
Here's a stupid little feature that I often want: a "clip" operator that cuts away everything on one side of a plane.
Yes, you can do this with difference or intersection with a big cube, but I find it ... aesthetically unpleasant ... to have to decide how big the cube should be.
At its simplest (and probably as a default) it should just cut away everything where Z<0, so
clip() sphere();
gives a half-sphere above Z=0.
That's enough, but for extra credit let the caller specify a normal vector (as for mirror()), or for double extra credit a point and normal vector so as to define a plane and an orientation.
OpenSCAD mailing list
Discuss@lists.openscad.org
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
I have to upvote this one. It’d be stupid simple, and I could use it to better implement the `front_half()`, `left_half()`, etc modules in my library.
Another language request that’s make my life easier would be a way to assign multiple variables from elements of a list.
a, b, c = func_returning_three_item_list();
Instead of having to write:
foo = func_returning_three_item_list();
a = foo[0];
b = foo[1];
c = foo[2];
- Revar
> On Nov 22, 2019, at 10:08 AM, Jordan Brown <openscad@jordan.maileater.net> wrote:
>
> Here's a stupid little feature that I often want: a "clip" operator that cuts away everything on one side of a plane.
>
> Yes, you can do this with difference or intersection with a big cube, but I find it ... aesthetically unpleasant ... to have to decide how big the cube should be.
>
> At its simplest (and probably as a default) it should just cut away everything where Z<0, so
> clip() sphere();
> gives a half-sphere above Z=0.
>
> That's enough, but for extra credit let the caller specify a normal vector (as for mirror()), or for double extra credit a point and normal vector so as to define a plane and an orientation.
> _______________________________________________
> OpenSCAD mailing list
> Discuss@lists.openscad.org
> http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
