Empathy List Archives

LH

Les Hall

Thu, Dec 18, 2014 11:55 PM

Hi all, I was generating a set of gears using the involute_gears library for use in RL 3D printing as well as SL (Second Life) virtual world object creation and I found the process to be quite laborious. If it were possible to generate output files from within a for loop, this process would be greatly simplified. Also SL imports only Colada files (*.dae), so I would want that output file type added to the list.

I am offering a $100 bounty for whoever does this.

I will look up bounty source and see if i can figure out how to do this. I’ll ask for help if I have trouble.

Les

Hi all, I was generating a set of gears using the involute_gears library for use in RL 3D printing as well as SL (Second Life) virtual world object creation and I found the process to be quite laborious. If it were possible to generate output files from within a for loop, this process would be greatly simplified. Also SL imports only Colada files (*.dae), so I would want that output file type added to the list. I am offering a $100 bounty for whoever does this. I will look up bounty source and see if i can figure out how to do this. I’ll ask for help if I have trouble. Les

MK

Marius Kintel

Fri, Dec 19, 2014 12:04 AM

On Dec 18, 2014, at 18:55 PM, Les Hall thingsofrings@icloud.com wrote:

Hi all, I was generating a set of gears using the involute_gears library for use in RL 3D printing as well as SL (Second Life) virtual world object creation and I found the process to be quite laborious. If it were possible to generate output files from within a for loop, this process would be greatly simplified. Also SL imports only Colada files (*.dae), so I would want that output file type added to the list.

I am offering a $100 bounty for whoever does this.

Bounties are always cool - it’s both a motivator and a very good indicator of pain points :)

I would split this in two issues: multi-file output and Collada export.
Multi-file export is discussed here: https://github.com/openscad/openscad/issues/1041
Perhaps you could add to that discussion to help arrive at a good method for this.

Cheers,

-Marius

On Dec 18, 2014, at 18:55 PM, Les Hall <thingsofrings@icloud.com> wrote: > Hi all, I was generating a set of gears using the involute_gears library for use in RL 3D printing as well as SL (Second Life) virtual world object creation and I found the process to be quite laborious. If it were possible to generate output files from within a for loop, this process would be greatly simplified. Also SL imports only Colada files (*.dae), so I would want that output file type added to the list. > > I am offering a $100 bounty for whoever does this. > Bounties are always cool - it’s both a motivator and a very good indicator of pain points :) I would split this in two issues: multi-file output and Collada export. Multi-file export is discussed here: https://github.com/openscad/openscad/issues/1041 Perhaps you could add to that discussion to help arrive at a good method for this. Cheers, -Marius

T

tdeagan

Fri, Dec 19, 2014 12:59 AM

Setting aside the file export mechanism, the 'batch process a series of
outputs' part of this request is the kind of problem that is potentially
well related to the parameterization topic discussed at GitHub
https://github.com/openscad/openscad/issues/722 and the forum
http://forum.openscad.org/New-Language-Feature-Parameter-Information-to-generate-GUI-Forms-td10544.html
.

A lot of systems would address this problem by taking the approach of using
a glue-ware scripting tool like Python or shell scripts or somesuch to
execute an OpenSCAD command line that digests parameters.

If the parameter mechanism (as suggested in points in the discussion,)
exposes the parameters via the command line then batch tasks like the one
described in this message could be executed by any of dozens of languages,
web tools, etc. (you could do it today in a brute force, rewrite the .scad
via a script, manner. Painful, but I do that kind of thing a lot in my
database development work.)

Don't get me wrong, file export functions in the OpenSCAD lexicon are
potentially really valuable, but command line parameter access is crazy
powerful.

--
View this message in context: http://forum.openscad.org/100-Bounty-for-easy-feature-tp10618p10620.html
Sent from the OpenSCAD mailing list archive at Nabble.com.

Setting aside the file export mechanism, the 'batch process a series of outputs' part of this request is the kind of problem that is potentially well related to the parameterization topic discussed at GitHub <https://github.com/openscad/openscad/issues/722> and the forum <http://forum.openscad.org/New-Language-Feature-Parameter-Information-to-generate-GUI-Forms-td10544.html> . A lot of systems would address this problem by taking the approach of using a glue-ware scripting tool like Python or shell scripts or somesuch to execute an OpenSCAD command line that digests parameters. If the parameter mechanism (as suggested in points in the discussion,) exposes the parameters via the command line then batch tasks like the one described in this message could be executed by any of dozens of languages, web tools, etc. (you could do it today in a brute force, rewrite the .scad via a script, manner. Painful, but I do that kind of thing a lot in my database development work.) Don't get me wrong, file export functions in the OpenSCAD lexicon are potentially really valuable, but command line parameter access is crazy powerful. -- View this message in context: http://forum.openscad.org/100-Bounty-for-easy-feature-tp10618p10620.html Sent from the OpenSCAD mailing list archive at Nabble.com.

LH

Les Hall

Fri, Dec 19, 2014 1:41 AM

I see your point about the command line parameters, and I would use that option if I knew how. But I think it’s cool to put it either in the GUI or the code (my preference is the code) or both (best of all). I added $50 to the existing $100 bounty on this. I will try to figure out how to post a bounty to add .dae Colada files next for the remaining $50 part of the solution. This bounty source thing is cool!

Note that I will rarely ever donate more than $5 to an open source project to support it’s overall development, but I’m willing to throw a fist full of dollars at a specific item that I want. Go figure eh?

Les
p.s. and I’m a poor boy on disability so this is a lot of $ for me!

On Dec 18, 2014, at 6:59 PM, tdeagan tim@deagan.net wrote:

Setting aside the file export mechanism, the 'batch process a series of
outputs' part of this request is the kind of problem that is potentially
well related to the parameterization topic discussed at GitHub
https://github.com/openscad/openscad/issues/722 and the forum
http://forum.openscad.org/New-Language-Feature-Parameter-Information-to-generate-GUI-Forms-td10544.html
.

A lot of systems would address this problem by taking the approach of using
a glue-ware scripting tool like Python or shell scripts or somesuch to
execute an OpenSCAD command line that digests parameters.

If the parameter mechanism (as suggested in points in the discussion,)
exposes the parameters via the command line then batch tasks like the one
described in this message could be executed by any of dozens of languages,
web tools, etc. (you could do it today in a brute force, rewrite the .scad
via a script, manner. Painful, but I do that kind of thing a lot in my
database development work.)

Don't get me wrong, file export functions in the OpenSCAD lexicon are
potentially really valuable, but command line parameter access is crazy
powerful.

--
View this message in context: http://forum.openscad.org/100-Bounty-for-easy-feature-tp10618p10620.html
Sent from the OpenSCAD mailing list archive at Nabble.com.

OpenSCAD mailing list
Discuss@lists.openscad.org
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org

I see your point about the command line parameters, and I would use that option if I knew how. But I think it’s cool to put it either in the GUI or the code (my preference is the code) or both (best of all). I added $50 to the existing $100 bounty on this. I will try to figure out how to post a bounty to add .dae Colada files next for the remaining $50 part of the solution. This bounty source thing is cool! Note that I will rarely ever donate more than $5 to an open source project to support it’s overall development, but I’m willing to throw a fist full of dollars at a specific item that I want. Go figure eh? Les p.s. and I’m a poor boy on disability so this is a lot of $ for me! > On Dec 18, 2014, at 6:59 PM, tdeagan <tim@deagan.net> wrote: > > Setting aside the file export mechanism, the 'batch process a series of > outputs' part of this request is the kind of problem that is potentially > well related to the parameterization topic discussed at GitHub > <https://github.com/openscad/openscad/issues/722> and the forum > <http://forum.openscad.org/New-Language-Feature-Parameter-Information-to-generate-GUI-Forms-td10544.html> > . > > A lot of systems would address this problem by taking the approach of using > a glue-ware scripting tool like Python or shell scripts or somesuch to > execute an OpenSCAD command line that digests parameters. > > If the parameter mechanism (as suggested in points in the discussion,) > exposes the parameters via the command line then batch tasks like the one > described in this message could be executed by any of dozens of languages, > web tools, etc. (you could do it today in a brute force, rewrite the .scad > via a script, manner. Painful, but I do that kind of thing a lot in my > database development work.) > > Don't get me wrong, file export functions in the OpenSCAD lexicon are > potentially really valuable, but command line parameter access is crazy > powerful. > > > > > > -- > View this message in context: http://forum.openscad.org/100-Bounty-for-easy-feature-tp10618p10620.html > Sent from the OpenSCAD mailing list archive at Nabble.com. > > _______________________________________________ > OpenSCAD mailing list > Discuss@lists.openscad.org > http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org

TA

Taylor Alexander

Fri, Dec 19, 2014 1:42 AM

Sounds like tdeagan has the right idea for batch output. For file formats,
I'd add $50 for IGES export. Apparently it is CSG based. This would allow
import into solidworks of something other than STL, which is awful. Though
maybe collada support would help here.

On Thu, Dec 18, 2014 at 4:59 PM, tdeagan tim@deagan.net wrote:

Setting aside the file export mechanism, the 'batch process a series of
outputs' part of this request is the kind of problem that is potentially
well related to the parameterization topic discussed at GitHub
https://github.com/openscad/openscad/issues/722 and the forum
<
http://forum.openscad.org/New-Language-Feature-Parameter-Information-to-generate-GUI-Forms-td10544.html

.

A lot of systems would address this problem by taking the approach of using
a glue-ware scripting tool like Python or shell scripts or somesuch to
execute an OpenSCAD command line that digests parameters.

If the parameter mechanism (as suggested in points in the discussion,)
exposes the parameters via the command line then batch tasks like the one
described in this message could be executed by any of dozens of languages,
web tools, etc. (you could do it today in a brute force, rewrite the .scad
via a script, manner. Painful, but I do that kind of thing a lot in my
database development work.)

Don't get me wrong, file export functions in the OpenSCAD lexicon are
potentially really valuable, but command line parameter access is crazy
powerful.

--
View this message in context:
http://forum.openscad.org/100-Bounty-for-easy-feature-tp10618p10620.html
Sent from the OpenSCAD mailing list archive at Nabble.com.

OpenSCAD mailing list
Discuss@lists.openscad.org
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org

Sounds like tdeagan has the right idea for batch output. For file formats, I'd add $50 for IGES export. Apparently it is CSG based. This would allow import into solidworks of something other than STL, which is awful. Though maybe collada support would help here. On Thu, Dec 18, 2014 at 4:59 PM, tdeagan <tim@deagan.net> wrote: > > Setting aside the file export mechanism, the 'batch process a series of > outputs' part of this request is the kind of problem that is potentially > well related to the parameterization topic discussed at GitHub > <https://github.com/openscad/openscad/issues/722> and the forum > < > http://forum.openscad.org/New-Language-Feature-Parameter-Information-to-generate-GUI-Forms-td10544.html > > > . > > A lot of systems would address this problem by taking the approach of using > a glue-ware scripting tool like Python or shell scripts or somesuch to > execute an OpenSCAD command line that digests parameters. > > If the parameter mechanism (as suggested in points in the discussion,) > exposes the parameters via the command line then batch tasks like the one > described in this message could be executed by any of dozens of languages, > web tools, etc. (you could do it today in a brute force, rewrite the .scad > via a script, manner. Painful, but I do that kind of thing a lot in my > database development work.) > > Don't get me wrong, file export functions in the OpenSCAD lexicon are > potentially really valuable, but command line parameter access is crazy > powerful. > > > > > > -- > View this message in context: > http://forum.openscad.org/100-Bounty-for-easy-feature-tp10618p10620.html > Sent from the OpenSCAD mailing list archive at Nabble.com. > > _______________________________________________ > OpenSCAD mailing list > Discuss@lists.openscad.org > http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org >

LH

Les Hall

Fri, Dec 19, 2014 1:47 AM

Let’s combine our file formats, IGES and DAE for a total of $100 ($50 from each of us). I can’t figure out how to post a bounty myself, so I must be told how to do it or you can do it.

Les

On Dec 18, 2014, at 7:42 PM, Taylor Alexander tlalexander@gmail.com wrote:

Sounds like tdeagan has the right idea for batch output. For file formats, I'd add $50 for IGES export. Apparently it is CSG based. This would allow import into solidworks of something other than STL, which is awful. Though maybe collada support would help here.

On Thu, Dec 18, 2014 at 4:59 PM, tdeagan <tim@deagan.net mailto:tim@deagan.net> wrote:
Setting aside the file export mechanism, the 'batch process a series of
outputs' part of this request is the kind of problem that is potentially
well related to the parameterization topic discussed at GitHub
<https://github.com/openscad/openscad/issues/722 https://github.com/openscad/openscad/issues/722> and the forum
<http://forum.openscad.org/New-Language-Feature-Parameter-Information-to-generate-GUI-Forms-td10544.html http://forum.openscad.org/New-Language-Feature-Parameter-Information-to-generate-GUI-Forms-td10544.html>
.

A lot of systems would address this problem by taking the approach of using
a glue-ware scripting tool like Python or shell scripts or somesuch to
execute an OpenSCAD command line that digests parameters.

If the parameter mechanism (as suggested in points in the discussion,)
exposes the parameters via the command line then batch tasks like the one
described in this message could be executed by any of dozens of languages,
web tools, etc. (you could do it today in a brute force, rewrite the .scad
via a script, manner. Painful, but I do that kind of thing a lot in my
database development work.)

Don't get me wrong, file export functions in the OpenSCAD lexicon are
potentially really valuable, but command line parameter access is crazy
powerful.

--
View this message in context: http://forum.openscad.org/100-Bounty-for-easy-feature-tp10618p10620.html http://forum.openscad.org/100-Bounty-for-easy-feature-tp10618p10620.html
Sent from the OpenSCAD mailing list archive at Nabble.com.

OpenSCAD mailing list
Discuss@lists.openscad.org mailto:Discuss@lists.openscad.org
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org

OpenSCAD mailing list
Discuss@lists.openscad.org
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org

Let’s combine our file formats, IGES and DAE for a total of $100 ($50 from each of us). I can’t figure out how to post a bounty myself, so I must be told how to do it or you can do it. Les > On Dec 18, 2014, at 7:42 PM, Taylor Alexander <tlalexander@gmail.com> wrote: > > Sounds like tdeagan has the right idea for batch output. For file formats, I'd add $50 for IGES export. Apparently it is CSG based. This would allow import into solidworks of something other than STL, which is awful. Though maybe collada support would help here. > > On Thu, Dec 18, 2014 at 4:59 PM, tdeagan <tim@deagan.net <mailto:tim@deagan.net>> wrote: > Setting aside the file export mechanism, the 'batch process a series of > outputs' part of this request is the kind of problem that is potentially > well related to the parameterization topic discussed at GitHub > <https://github.com/openscad/openscad/issues/722 <https://github.com/openscad/openscad/issues/722>> and the forum > <http://forum.openscad.org/New-Language-Feature-Parameter-Information-to-generate-GUI-Forms-td10544.html <http://forum.openscad.org/New-Language-Feature-Parameter-Information-to-generate-GUI-Forms-td10544.html>> > . > > A lot of systems would address this problem by taking the approach of using > a glue-ware scripting tool like Python or shell scripts or somesuch to > execute an OpenSCAD command line that digests parameters. > > If the parameter mechanism (as suggested in points in the discussion,) > exposes the parameters via the command line then batch tasks like the one > described in this message could be executed by any of dozens of languages, > web tools, etc. (you could do it today in a brute force, rewrite the .scad > via a script, manner. Painful, but I do that kind of thing a lot in my > database development work.) > > Don't get me wrong, file export functions in the OpenSCAD lexicon are > potentially really valuable, but command line parameter access is crazy > powerful. > > > > > > -- > View this message in context: http://forum.openscad.org/100-Bounty-for-easy-feature-tp10618p10620.html <http://forum.openscad.org/100-Bounty-for-easy-feature-tp10618p10620.html> > Sent from the OpenSCAD mailing list archive at Nabble.com. > > _______________________________________________ > OpenSCAD mailing list > Discuss@lists.openscad.org <mailto:Discuss@lists.openscad.org> > http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org <http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org> > _______________________________________________ > OpenSCAD mailing list > Discuss@lists.openscad.org > http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org

TA

Taylor Alexander

Fri, Dec 19, 2014 1:50 AM

Sounds good. Does anyone want to work on these things for the bounty? Or
does anyone want to add to the dollar amount for someone adding DAE and
IGES support?

On Thu, Dec 18, 2014 at 5:47 PM, Les Hall thingsofrings@icloud.com wrote:

Let’s combine our file formats, IGES and DAE for a total of $100 ($50 from
each of us). I can’t figure out how to post a bounty myself, so I must be
told how to do it or you can do it.

Les

On Dec 18, 2014, at 7:42 PM, Taylor Alexander tlalexander@gmail.com
wrote:

Sounds like tdeagan has the right idea for batch output. For file formats,
I'd add $50 for IGES export. Apparently it is CSG based. This would allow
import into solidworks of something other than STL, which is awful. Though
maybe collada support would help here.

On Thu, Dec 18, 2014 at 4:59 PM, tdeagan tim@deagan.net wrote:

Setting aside the file export mechanism, the 'batch process a series of
outputs' part of this request is the kind of problem that is potentially
well related to the parameterization topic discussed at GitHub
https://github.com/openscad/openscad/issues/722 and the forum
<
http://forum.openscad.org/New-Language-Feature-Parameter-Information-to-generate-GUI-Forms-td10544.html

.

A lot of systems would address this problem by taking the approach of
using
a glue-ware scripting tool like Python or shell scripts or somesuch to
execute an OpenSCAD command line that digests parameters.

If the parameter mechanism (as suggested in points in the discussion,)
exposes the parameters via the command line then batch tasks like the one
described in this message could be executed by any of dozens of languages,
web tools, etc. (you could do it today in a brute force, rewrite the
.scad
via a script, manner. Painful, but I do that kind of thing a lot in my
database development work.)

Don't get me wrong, file export functions in the OpenSCAD lexicon are
potentially really valuable, but command line parameter access is crazy
powerful.

--
View this message in context:
http://forum.openscad.org/100-Bounty-for-easy-feature-tp10618p10620.html
Sent from the OpenSCAD mailing list archive at Nabble.com.

OpenSCAD mailing list
Discuss@lists.openscad.org
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org

Sounds good. Does anyone want to work on these things for the bounty? Or does anyone want to add to the dollar amount for someone adding DAE and IGES support? On Thu, Dec 18, 2014 at 5:47 PM, Les Hall <thingsofrings@icloud.com> wrote: > > Let’s combine our file formats, IGES and DAE for a total of $100 ($50 from > each of us). I can’t figure out how to post a bounty myself, so I must be > told how to do it or you can do it. > > Les > > > On Dec 18, 2014, at 7:42 PM, Taylor Alexander <tlalexander@gmail.com> > wrote: > > Sounds like tdeagan has the right idea for batch output. For file formats, > I'd add $50 for IGES export. Apparently it is CSG based. This would allow > import into solidworks of something other than STL, which is awful. Though > maybe collada support would help here. > > On Thu, Dec 18, 2014 at 4:59 PM, tdeagan <tim@deagan.net> wrote: >> >> Setting aside the file export mechanism, the 'batch process a series of >> outputs' part of this request is the kind of problem that is potentially >> well related to the parameterization topic discussed at GitHub >> <https://github.com/openscad/openscad/issues/722> and the forum >> < >> http://forum.openscad.org/New-Language-Feature-Parameter-Information-to-generate-GUI-Forms-td10544.html >> > >> . >> >> A lot of systems would address this problem by taking the approach of >> using >> a glue-ware scripting tool like Python or shell scripts or somesuch to >> execute an OpenSCAD command line that digests parameters. >> >> If the parameter mechanism (as suggested in points in the discussion,) >> exposes the parameters via the command line then batch tasks like the one >> described in this message could be executed by any of dozens of languages, >> web tools, etc. (you could do it today in a brute force, rewrite the >> .scad >> via a script, manner. Painful, but I do that kind of thing a lot in my >> database development work.) >> >> Don't get me wrong, file export functions in the OpenSCAD lexicon are >> potentially really valuable, but command line parameter access is crazy >> powerful. >> >> >> >> >> >> -- >> View this message in context: >> http://forum.openscad.org/100-Bounty-for-easy-feature-tp10618p10620.html >> Sent from the OpenSCAD mailing list archive at Nabble.com. >> >> _______________________________________________ >> OpenSCAD mailing list >> Discuss@lists.openscad.org >> http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org >> > _______________________________________________ > OpenSCAD mailing list > Discuss@lists.openscad.org > http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org > > > > _______________________________________________ > OpenSCAD mailing list > Discuss@lists.openscad.org > http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org > >

MK

Marius Kintel

Fri, Dec 19, 2014 1:56 AM

On Dec 18, 2014, at 20:47 PM, Les Hall thingsofrings@icloud.com wrote:

Let’s combine our file formats, IGES and DAE for a total of $100 ($50 from each of us). I can’t figure out how to post a bounty myself, so I must be told how to do it or you can do it.

Please split such requests into multiple issues. IGES and DAE are very different beasts.

-Marius

On Dec 18, 2014, at 20:47 PM, Les Hall <thingsofrings@icloud.com> wrote: > Let’s combine our file formats, IGES and DAE for a total of $100 ($50 from each of us). I can’t figure out how to post a bounty myself, so I must be told how to do it or you can do it. > Please split such requests into multiple issues. IGES and DAE are very different beasts. -Marius

LH

Les Hall

Fri, Dec 19, 2014 1:57 AM

Ah, understood Marius. Will do.

Les

On Dec 18, 2014, at 7:56 PM, Marius Kintel marius@kintel.net wrote:

On Dec 18, 2014, at 20:47 PM, Les Hall thingsofrings@icloud.com wrote:

Let’s combine our file formats, IGES and DAE for a total of $100 ($50 from each of us). I can’t figure out how to post a bounty myself, so I must be told how to do it or you can do it.

Please split such requests into multiple issues. IGES and DAE are very different beasts.

-Marius

OpenSCAD mailing list
Discuss@lists.openscad.org
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org

Ah, understood Marius. Will do. Les > On Dec 18, 2014, at 7:56 PM, Marius Kintel <marius@kintel.net> wrote: > > On Dec 18, 2014, at 20:47 PM, Les Hall <thingsofrings@icloud.com> wrote: > >> Let’s combine our file formats, IGES and DAE for a total of $100 ($50 from each of us). I can’t figure out how to post a bounty myself, so I must be told how to do it or you can do it. >> > Please split such requests into multiple issues. IGES and DAE are very different beasts. > > -Marius > > > _______________________________________________ > OpenSCAD mailing list > Discuss@lists.openscad.org > http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org

YL

Yann Lossouarn

Fri, Dec 19, 2014 8:36 AM

Hi all,

@Les, I guess this platform might be the right place for your bounty :
http://funding.openinitiative.com/

Bye,
Yann

Le 2014-12-19 02:47, Les Hall a écrit :

Let’s combine our file formats, IGES and DAE for a total of $100
($50 from each of us). I can’t figure out how to post a bounty
myself, so I must be told how to do it or you can do it.

Les

On Dec 18, 2014, at 7:42 PM, Taylor Alexander
tlalexander@gmail.com wrote:

Sounds like tdeagan has the right idea for batch output. For file
formats, I'd add $50 for IGES export. Apparently it is CSG based.
This would allow import into solidworks of something other than STL,
which is awful. Though maybe collada support would help here.

On Thu, Dec 18, 2014 at 4:59 PM, tdeagan tim@deagan.net wrote:

Setting aside the file export mechanism, the 'batch process a
series of
outputs' part of this request is the kind of problem that is
potentially
well related to the parameterization topic discussed at GitHub
<https://github.com/openscad/openscad/issues/722 [1]> and the
forum

<http://forum.openscad.org/New-Language-Feature-Parameter-Information-to-generate-GUI-Forms-td10544.html

[2]>
.

A lot of systems would address this problem by taking the
approach of using
a glue-ware scripting tool like Python or shell scripts or
somesuch to
execute an OpenSCAD command line that digests parameters.

If the parameter mechanism (as suggested in points in the
discussion,)
exposes the parameters via the command line then batch tasks like
the one
described in this message could be executed by any of dozens of
languages,
web tools, etc. (you could do it today in a brute force, rewrite
the .scad
via a script, manner. Painful, but I do that kind of thing a lot
in my
database development work.)

Don't get me wrong, file export functions in the OpenSCAD lexicon
are
potentially really valuable, but command line parameter access is
crazy
powerful.

--
View this message in context:

http://forum.openscad.org/100-Bounty-for-easy-feature-tp10618p10620.html

[3]
Sent from the OpenSCAD mailing list archive at Nabble.com [4].

OpenSCAD mailing list
Discuss@lists.openscad.org

http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org

[5]

OpenSCAD mailing list
Discuss@lists.openscad.org

http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org

Links:

[1] https://github.com/openscad/openscad/issues/722
[2]
http://forum.openscad.org/New-Language-Feature-Parameter-Information-to-generate-GUI-Forms-td10544.html
[3]
http://forum.openscad.org/100-Bounty-for-easy-feature-tp10618p10620.html
[4] http://Nabble.com
[5]
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org

OpenSCAD mailing list
Discuss@lists.openscad.org
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org

--
Yann Lossouarn (06 30 12 62 77)

Hi all, @Les, I guess this platform might be the right place for your bounty : http://funding.openinitiative.com/ Bye, Yann Le 2014-12-19 02:47, Les Hall a écrit : > Let’s combine our file formats, IGES and DAE for a total of $100 > ($50 from each of us). I can’t figure out how to post a bounty > myself, so I must be told how to do it or you can do it. > > Les > >> On Dec 18, 2014, at 7:42 PM, Taylor Alexander >> <tlalexander@gmail.com> wrote: >> >> Sounds like tdeagan has the right idea for batch output. For file >> formats, I'd add $50 for IGES export. Apparently it is CSG based. >> This would allow import into solidworks of something other than STL, >> which is awful. Though maybe collada support would help here. >> >> On Thu, Dec 18, 2014 at 4:59 PM, tdeagan <tim@deagan.net> wrote: >> >>> Setting aside the file export mechanism, the 'batch process a >>> series of >>> outputs' part of this request is the kind of problem that is >>> potentially >>> well related to the parameterization topic discussed at GitHub >>> <https://github.com/openscad/openscad/issues/722 [1]> and the >>> forum >>> >> > <http://forum.openscad.org/New-Language-Feature-Parameter-Information-to-generate-GUI-Forms-td10544.html >>> [2]> >>> . >>> >>> A lot of systems would address this problem by taking the >>> approach of using >>> a glue-ware scripting tool like Python or shell scripts or >>> somesuch to >>> execute an OpenSCAD command line that digests parameters. >>> >>> If the parameter mechanism (as suggested in points in the >>> discussion,) >>> exposes the parameters via the command line then batch tasks like >>> the one >>> described in this message could be executed by any of dozens of >>> languages, >>> web tools, etc. (you could do it today in a brute force, rewrite >>> the .scad >>> via a script, manner. Painful, but I do that kind of thing a lot >>> in my >>> database development work.) >>> >>> Don't get me wrong, file export functions in the OpenSCAD lexicon >>> are >>> potentially really valuable, but command line parameter access is >>> crazy >>> powerful. >>> >>> -- >>> View this message in context: >>> >> > http://forum.openscad.org/100-Bounty-for-easy-feature-tp10618p10620.html >>> [3] >>> Sent from the OpenSCAD mailing list archive at Nabble.com [4]. >>> >>> _______________________________________________ >>> OpenSCAD mailing list >>> Discuss@lists.openscad.org >>> >> > http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org >>> [5] >> _______________________________________________ >> OpenSCAD mailing list >> Discuss@lists.openscad.org >> > http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org > > > > Links: > ------ > [1] https://github.com/openscad/openscad/issues/722 > [2] > http://forum.openscad.org/New-Language-Feature-Parameter-Information-to-generate-GUI-Forms-td10544.html > [3] > http://forum.openscad.org/100-Bounty-for-easy-feature-tp10618p10620.html > [4] http://Nabble.com > [5] > http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org > > _______________________________________________ > OpenSCAD mailing list > Discuss@lists.openscad.org > http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org -- Yann Lossouarn (06 30 12 62 77)

discuss@lists.openscad.org

$100 Bounty for easy feature

Links: