[OpenSCAD] OpenSCAD Digest, Vol 15, Issue 7
elmo.mantynen at iki.fi
Tue Feb 15 15:04:38 CET 2011
On 02/15/2011 01:10 PM, tigger at interthingy.com wrote:
> Hey all,
> This conversation _is_ getting interesting.....
> I just wanted to make a few observations and comments .
> OpenSCAD is awsome , thanks Clifford.
> An advantage that openscad has now is that there is growing code base of
> objects , porting across to another front end will need a translater so
> that work is not lost.
A translation is possible, but for the python->openscad generating
frontend, you can just import openscad code. The other way is blocking
on the feature request to have shell access (everything else could be
quickly implemented on top of that).
> I use Python for most of my work , so I'm biased , but I think wrapping
> the CSG ( and AST ) formats in a nice OO language is a really good idea.
> There are heaps of Makers that use python already , why learn a new
> syntax when an 'import openscad' is much easier.
> When this thread came up the first things that would be possible in
> python/scad would be.
> 1. Recursion
> 2. Better conditionals
> 3. Inheritance
> 4. database access <- collections of scad instances , like all the bolts
> , ever.
> 5. integration into other systems.
> I'm all for it , but as Kpykcъ said , pythonocc is there too.
Yes, having a third backend for pyscad using pythonocc would be awesome
too. But let's first experiment on the syntax/API/DSL design with the
two backends that are being developed now.
> On Tue 15/02/11 8:31 PM , "Kpykcъ" kpykcb at gmail.com sent:
> On Mon, 14 Feb 2011, Tony Buser wrote:
> > On Mon, Feb 14, 2011 at 5:12 PM, Giles Bathgate
> <giles.bathgate at gmail.com <mailto:giles.bathgate at gmail.com>> wrote:
> > Its obvious that there would be a lot of features from something like
> > Python that are irrelevant to OpenSCAD for example threading, string
> > processing (regular expressions, Unicode, calculating differences
> > between files), Internet protocols (HTTP, FTP, SMTP, XML-RPC, POP,
> > IMAP, CGI programming), software engineering (unit testing, logging,
> > profiling, parsing Python code), and operating system interfaces
> > (system calls, filesystems, TCP/IP sockets).
> > I'm not sure I agree with that. It might be irrelevant to strictly
> 3D model creation... however, access to such features
> > would be potentially very powerful to do unforeseen things... then
> there's string processing - that could be very handy
> > with parametric scripts (look at what I had to do to handle
> strings in my bitmap text module) Filesystem access would be
> > really nice for loading external data. Interesting things could be
> done in terms of dynamic objects if the script could
> > call webservices...
> Hi all,
> I want to some my thoughts in addition to what Giles said. I'm mostly
> end-user here, not a programmer by a proffesion.
> Its obvious, that Linux (especially) have no access to truely
> feature complete CAD. And for that reason it will be realy better to
> have features like: egde fillet or full DXF support or sizes placment,
> 2D drawings export; than hypotetically useful web-services interaction
> Every other Linux CAD tools like FreeCAD, HeeksCAD have some level
> of python scripting, but main OpenSCAD advantage over them is
> of his embedded language. And i'm in doubt that OpenSCAD will win for
> example with python-occ or any OpenCASCADE-based python engine if it
> start to try compete with them.
> WBR Lavruschenko Oleksandr
> OpenSCAD mailing list
> OpenSCAD at rocklinux.org <mailto:OpenSCAD at rocklinux.org>
> OpenSCAD mailing list
> OpenSCAD at rocklinux.org
More information about the OpenSCAD