Yes, I was referring to the OpenSCAD2 proposal. Thanks for the actual links!
In that document, perhaps we should add some more concrete use-cases the kind of dictionary usage discussed here, or even hint at things like JSON import?
-Marius
On Dec 30, 2015, at 12:05 PM, doug moen doug@moens.org wrote:
Marius may be referring to my OpenSCAD2 proposal, in which "dictionary objects" are just called "objects".
The OpenSCAD2 docs are in github: https://github.com/doug-moen/openscad2/
The object proposal is here:
https://github.com/doug-moen/openscad2/blob/master/rfc/Objects.md
https://github.com/doug-moen/openscad2/blob/master/rfc/Programming_With_Objects.md
There are lots of use cases given: you might as well click through and read about them in the linked documents.
Johan Jonker wrote
I made a macro in the excel file that reacts on just a button click and
exports the table to an scad file.
So it is just two clicks to modify: One in the excel and then F5 to
refresh Openscad.
Really nice work. That's probably the most you can get outta
excel-controlled openscad. (I was trying to see if openscad has any dll that
I can insert into Excel as Add-in. Guess not).
You can also turn on the "Automatically Reload and Preview" in OpenSCAD.
Then, have excel and openscad opened side by side, you can enjoy one click
on the [Export to SCAD file] button and see it changed automatically.
Comparing to other approach, which focus only on data, this excel-approach
has the advantage of using Excel as both a data holder and a GUI like the
button you put on there.
$ Runsun Pan, PhD
$ libs:
doctest ,
faces ( git ),
offline doc ( git ),
runscad.py( 1 , 2 , git );
$ tips:
hash( 1 , 2 ),
sweep ,
var( 1 , 2 ),
lerp ,
animGif ,
precision( 1 , 2 )
--
View this message in context: http://forum.openscad.org/Parameterlist-Excel-export-to-OpenSCAD-tp15363p15374.html
Sent from the OpenSCAD mailing list archive at Nabble.com.
jdawgaz wrote
can you give some examples of usage of the dictionary objects would be?
Besides what are proposed for the OpenSCAD2, you can also refer to the
hash approach that I've been using: here
http://forum.openscad.org/parameterized-models-td8303.html#a8306 and
here
http://forum.openscad.org/Can-I-get-some-code-review-up-in-here-tp12341p12355.html
$ Runsun Pan, PhD
$ libs:
doctest ,
faces ( git ),
offline doc ( git ),
runscad.py( 1 , 2 , git );
$ tips:
hash( 1 , 2 ),
sweep ,
var( 1 , 2 ),
lerp ,
animGif ,
precision( 1 , 2 )
--
View this message in context: http://forum.openscad.org/Parameterlist-Excel-export-to-OpenSCAD-tp15363p15375.html
Sent from the OpenSCAD mailing list archive at Nabble.com.
I am happy to accept contributions :)
On Wednesday, 30 December 2015, Marius Kintel marius@kintel.net wrote:
Yes, I was referring to the OpenSCAD2 proposal. Thanks for the actual
links!
In that document, perhaps we should add some more concrete use-cases the
kind of dictionary usage discussed here, or even hint at things like JSON
import?
-Marius
On Dec 30, 2015, at 12:05 PM, doug moen <doug@moens.org javascript:;>
wrote:
Marius may be referring to my OpenSCAD2 proposal, in which "dictionary
objects" are just called "objects".
The OpenSCAD2 docs are in github:
The object proposal is here:
https://github.com/doug-moen/openscad2/blob/master/rfc/Objects.md
There are lots of use cases given: you might as well click through and
read about them in the linked documents.