[OpenSCAD] OpenSCAD2 design docs
doug at moens.org
Tue Sep 1 15:57:17 EDT 2015
I haven't touched this since July 9; I had started to make some changes to
fix design flaws in the scoping rules, but ran out of steam before I
finished incorporating that change and cleaning up the document. The worst
problem is that I started writing a new RFC called "Scoping Rules for
Scripts" but ran out of energy before I finished it. The missing text is
where I prove that the design is sound.
However, this is a small problem, relatively speaking. You are welcome to
read the document and provide feedback. I did get feedback from 2 other
people who read the whole thing (in a previous version), but none of that
feedback was transformative, in the sense of pointing out real problems, or
pointing out fundamentally better approaches. The only good transformative
feedback I've ever received was from you. So I'm interested in hearing what
you have to say.
Right now I'm working through some medical issues, and don't have a lot of
energy: mostly the problem is that my arm hurts, so I can't do large
amounts of typing right now. But I can still read, think and answer
On 1 September 2015 at 15:05, Marius Kintel <marius at kintel.net> wrote:
> Hi Doug,
> I was out traveling for a long while, but back again now.
> Catching up on OpenSCAD issues, but hopefully able to contribute to this
> again soon.
> Drop me a note if there are anything in particular you’re looking for now,
> or if I should just start reviewing it top-down.
> On Jul 20, 2015, at 10:07 AM, doug moen <doug at moens.org> wrote:
> > I have very little time to spare for this right now. I hope to have time
> to start writing code in August or September.
> > At the moment, I've got a first draft of parser.y, and I've planned out
> some algorithms and data structures, but that's it.
> > I was hoping to get more feedback from Marius, but he's gone off and
> started a new company, so he's busy.
> > There is no "release schedule", but the general plan is:
> > * get feedback from the community, update the design based on feedback
> > * carve up the design into smaller pieces that can be implemented
> independently, or in phases
> > * recruit people to write code for the various pieces
> > * start coding
> > Doug Moen
> OpenSCAD mailing list
> Discuss at lists.openscad.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Discuss