Or : https://www.bountysource.com/ https://bountyoss.com/ https://bountyfunding.com/workflow/ :) Le 2014-12-19 09:36, Yann Lossouarn a écrit : > 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)

I haven't done one, but from observation; Your raise a Github issue here <https://github.com/openscad/openscad/issues/new> mentioning the bounty proposal, Marius sprinkles magic power, and the option of adding a bounty appears against the issue, you can click on the link to do the formalities. I think... ----- Unless specifically shown otherwise above, my contribution is in the Public Domain; To the extent possible under law, I have waived all copyright and related or neighbouring rights to this work. This work is published globally via the internet. :) Inclusion of works of previous authors is not included in the above. The TPP is no simple “trade agreement.” Fight it! http://www.ourfairdeal.org/ -- View this message in context: http://forum.openscad.org/100-Bounty-for-easy-feature-tp10618p10630.html Sent from the OpenSCAD mailing list archive at Nabble.com.

> 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). Superficially these appear to cover different use cases. In the GUI it could be rather simple: The animation feature has a "dump picture" feature. A dump model checkbox could be added next to it. Then you draw your models in relation to $t. Doesn't have to be the same model animated, it could be different models. In the code, an stl() module could be added and work similar to render(), except the output is saved to a file. In either case you need to specify your needs _much_ more detailed than in your first post. Else the chance is big you won't get what you want. Maybe you can post a code example of what you would like. -- View this message in context: http://forum.openscad.org/100-Bounty-for-easy-feature-tp10618p10632.html Sent from the OpenSCAD mailing list archive at Nabble.com.

I see you already discussed this on github. Github has so insanely complex rules for passwords that I can never mine! :) -- View this message in context: http://forum.openscad.org/100-Bounty-for-easy-feature-tp10618p10633.html Sent from the OpenSCAD mailing list archive at Nabble.com.

Bananafofanapeel (heh, couldn’t resist), This seems reasonable with one exception - one might want to parameterize the files by more than one variable, in which case the $t would have to be decomposed by conditionals or logic to derive the separate variables, kinda messy. Same for the code as was discussed on github/bountysource where we might have something like: for (x=[0;2], y=[0:1]) write(myModel(x, y), “myFileName” . x . y . “.dae, [params]); where the dot (.) is the concatenation operator (I forget what it is in OpenSCAD) and the file format is taken from the extension plus the details of the file format are taken from the params (i.e. ascii vs binary for still). Les > On Dec 19, 2014, at 5:32 AM, Bananapeel <lunatica.xiaoyu@gmail.com> wrote: > >> 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). > > Superficially these appear to cover different use cases. > > In the GUI it could be rather simple: The animation feature has a "dump > picture" feature. A dump model checkbox could be added next to it. Then you > draw your models in relation to $t. Doesn't have to be the same model > animated, it could be different models. > > In the code, an stl() module could be added and work similar to render(), > except the output is saved to a file. > > In either case you need to specify your needs _much_ more detailed than in > your first post. Else the chance is big you won't get what you want. Maybe > you can post a code example of what you would like. > > > > > -- > View this message in context: http://forum.openscad.org/100-Bounty-for-easy-feature-tp10618p10632.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

@Bananapeel Your Idea is ingenious. Lets add a check box to Animate to export the stl. Animate would have to do an F6 instead of an F5, so. Is this possible? This would not break any existing designs. And if this feature gets implemented in the GUI later this could be depreciated. This is not the most convenient way to export different stl's but with a little thinking it is sure doable. +1 Sincerely, TakeItAndRun > > > > > -- > > View this message in context: > http://forum.openscad.org/100-Bounty-for-easy-feature-tp10618p10632.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 > -- stempeldergeschichte@googlemail.com <karsten@rohrbach.de> P.S. Falls meine E-Mail kürzer ausfällt als Dir angenehm ist: Ich probiere gerade aus kurze Antworten statt gar keine Antworten zu schreiben. Wenn Du gerne mehr lesen möchtest, dann lass es mich bitte wissen. P.S. In case my e-mail is shorter than you enjoy: I am currently trying short replies instead of no replies at all. Please let me know, if you like to read more. Enjoy!

On 12/19/2014 03:53 PM, Peter Falke wrote: > And if this feature gets implemented in the GUI later this could be depreciated. > Implementing already deprecated features does not sound like the best solution. Also I really don't want to imagine how that would be explained in the documentation ;-) If that feature is needed now, it's easily possible on command line without any changes to OpenSCAD itself. Just call with -Dpart=x and use that in code. Why misuse $t for that? ciao, Torsten.

Torsten, where in the docs is the command line info? or do i try —help or something? I’d really like to do this the command line way. Les > On Dec 19, 2014, at 9:02 AM, Torsten Paul <Torsten.Paul@gmx.de> wrote: > > On 12/19/2014 03:53 PM, Peter Falke wrote: >> And if this feature gets implemented in the GUI later this could be depreciated. >> > Implementing already deprecated features does not sound like the best solution. > > Also I really don't want to imagine how that would be explained in the documentation ;-) > > If that feature is needed now, it's easily possible on command line without any changes > to OpenSCAD itself. Just call with -Dpart=x and use that in code. Why misuse $t for that? > > ciao, > Torsten. > > > _______________________________________________ > OpenSCAD mailing list > Discuss@lists.openscad.org > http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org

On Dec 19, 2014, at 10:30 AM, Les Hall <thingsofrings@icloud.com> wrote: > Torsten, where in the docs is the command line info? or do i try —help or something? I’d really like to do this the command line way. > https://en.wikibooks.org/wiki/OpenSCAD_User_Manual/Using_OpenSCAD_in_a_command_line_environment -Marius

On 12/19/2014 04:30 PM, Les Hall wrote: > Torsten, where in the docs is the command line info? or do i try —help or > something? I’d really like to do this the command line way. A (very short) explanation is there: https://en.wikibooks.org/wiki/OpenSCAD_User_Manual/Using_OpenSCAD_in_a_command_line_environment#Constants Another simple example: mode = 0; module part1() { cube(20, center = true); } module part2() { cylinder(r = 5, h = 21, center = true); } module assembly() { difference() { part1(); part2(); } } if (mode == 1) { part1(); } else if (mode == 2) { part2(); } else { assembly(); } Create a batch file (or shell script, or processing sketch, ...): openscad -Dmode=0 -o all.stl params.scad openscad -Dmode=1 -o part1.stl params.scad openscad -Dmode=2 -o part2.stl params.scad ciao, Torsten.