Introduction

classic Classic list List threaded Threaded
29 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Introduction

Amarjeet Kapoor
Hi, I am Amarjeet Singh Kapoor, 3rd year student of B.tech in computer
science and engineering at Guru Nanak Dev Engineering College,
Ludhiana. Ludhiana
I have worked on Image Processing using OpenCV and made a project
regarding analysis of dynamic of structures (CivilOctave). Then I
started SIM (Structure information model). Idea behind the project is
modeling the structure based on information and storing it in database
so that information can be used for analysis.
At present just parsing Staad-pro files to extract information for
Sim. For more information, you can visit my github account.

https://github.com/amarjeetkapoor1

I have knowledge of C++, python,shell script,HTML, cgi, sql, latex,
doxygen, etc.

I'm interested to contribute in Project: Form based script parameterization
during my summers as much I have understand this project we want that
should be able to change certain variables or parameters in .scad file
through the use of form like interface which may include slide bar or
check box etc. so, that we can visualize the changes in output on the
base of input through the form side by side instead of manual changing
different parameters instead.

Please tell did I understood the project correctly or if I have missed
something important?




--
Amarjeet Singh
https://amarjeetkapoor1.wordpress.com
https://github.com/amarjeetkapoor1
https://bitbucket.org/amarjeetkapoor

"knowledge about knowledge is power"

_______________________________________________
OpenSCAD mailing list
[hidden email]
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
tp3
Reply | Threaded
Open this post in threaded view
|

Re: Introduction

tp3
Hi!

Welcome to the list.

On 03/07/2016 06:13 PM, Amarjeet Kapoor wrote:

> I'm interested to contribute in Project: Form based script parameterization
> during my summers as much I have understand this project we want that
> should be able to change certain variables or parameters in .scad file
> through the use of form like interface which may include slide bar or
> check box etc. so, that we can visualize the changes in output on the
> base of input through the form side by side instead of manual changing
> different parameters instead.
>
> Please tell did I understood the project correctly or if I have missed
> something important?
>
Yes, that's a good summary of the core functionality. The github issue
has links to some short screencasts that illustrate how it could look
like. I guess the first challenge is to divide the topic into smaller
parts that can be handled easily. This is certainly a project where
it's possible to get lost in all the ideas that can be put into it :-).

ciao,
  Torsten.


_______________________________________________
OpenSCAD mailing list
[hidden email]
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
-- Torsten
Reply | Threaded
Open this post in threaded view
|

Re: Introduction

Amarjeet Kapoor


   
On Mar 8, 2016 2:32 AM, "Torsten Paul" <[hidden email]> wrote:
>
> Hi!
>
> Welcome to the list.
>

Thanks Torsten.

> Yes, that's a good summary of the core functionality. The github issue
> has links to some short screencasts that illustrate how it could look
> like. I guess the first challenge is to divide the topic into smaller
> parts that can be handled easily. This is certainly a project where
> it's possible to get lost in all the ideas that can be put into it :-).

Yes, your right about geting lost in all the ideas for projects like this.

At Present I am trying to know the software little bit from user's point of veiw. so, as to know is their anything provided to user by openscad that can be used in for above project like system arguments while executing the .scad file.

And I have not found the developer's documentation of openscad just found some charts which provided information regarding how a module in .scad file is run by opensacd but it doesn't tells in which file the starting code exits or relationship and functionality of code in each file.

Would you guide me from where can I get an abstract view of the softwares based on flow of data in openscad.

--
Amarjeet Singh
https://amarjeetkapoor1.wordpress.com
https://github.com/amarjeetkapoor1
https://bitbucket.org/amarjeetkapoor


_______________________________________________
OpenSCAD mailing list
[hidden email]
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
tp3
Reply | Threaded
Open this post in threaded view
|

Re: Introduction

tp3
On 03/09/2016 02:35 AM, Amarjeet Kapoor wrote:
> And I have not found the developer's documentation of openscad
> just found some charts which provided information regarding how
> a module in .scad file is run by opensacd but it doesn't tells
> in which file the starting code exits or relationship and
> functionality of code in each file.
>
There is an overview of the main flow and relation of the core
objects in:
https://github.com/openscad/openscad/blob/master/doc/OpenSCAD-compile.pdf
Otherwise the existing developer documentation focuses more on
things like building the application on various platforms.

For myself I found the best strategy to get to know new code
base is to find some small topic and dig into the part of code
that is related to this. Understanding then grows from there.
Sitting down and trying to understand all details of the code
by just looking at it is a very scary and dreary work and rarely
needed to be productive.

> Would you guide me from where can I get an abstract view of
> the softwares based on flow of data in openscad.
>
The PDF mentioned above shows the main steps involved when
compiling and displaying a model. This is a good base for
understanding OpenSCAD in general and will also help a bit
for the "Customizer" project. It's probably not needed to
understand every detail to work on the project. A big part
of this project is also GUI/Qt to give the user the means
to modify the parameters.

In parallel, I'd suggest to just get the code from github and
get it compiling. For GSoC we'll follow the framework of our
umbrella org BRL-CAD, so a small and simple patch would be
required as well. This could be one of the tasks tagged as
"low hanging" in github, or we can discuss some other options
(probably easier in a more interactive way on IRC).

ciao,
  Torsten.


_______________________________________________
OpenSCAD mailing list
[hidden email]
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
-- Torsten
Reply | Threaded
Open this post in threaded view
|

Re: Introduction

Amarjeet Kapoor


On Mar 9, 2016 1:05 PM, "Torsten Paul" <[hidden email]> wrote:
> There is an overview of the main flow and relation of the core
> objects in:
> https://github.com/openscad/openscad/blob/master/doc/OpenSCAD-compile.pdf
> Otherwise the existing developer documentation focuses more on
> things like building the application on various platforms.
>

Thanks I will go through.

<snipe>

> In parallel, I'd suggest to just get the code from github and
> get it compiling. For GSoC we'll follow the framework of our
> umbrella org BRL-CAD, so a small and simple patch would be
> required as well. This could be one of the tasks tagged as
> "low hanging" in github, or we can discuss some other options
> (probably easier in a more interactive way on IRC).

Yes, sure  and I have complied it.

--
Amarjeet Singh
https://amarjeetkapoor1.wordpress.com
https://github.com/amarjeetkapoor1
https://bitbucket.org/amarjeetkapoor

   


_______________________________________________
OpenSCAD mailing list
[hidden email]
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
Reply | Threaded
Open this post in threaded view
|

Re: Introduction

Amarjeet Kapoor
In reply to this post by tp3
On 9 March 2016 at 13:04, Torsten Paul <[hidden email]> wrote:

<snip>

> In parallel, I'd suggest to just get the code from github and
> get it compiling. For GSoC we'll follow the framework of our
> umbrella org BRL-CAD, so a small and simple patch would be
> required as well. This could be one of the tasks tagged as
> "low hanging" in github, or we can discuss some other options
> (probably easier in a more interactive way on IRC).

As per you suggested, I have gone through issues with "low hanging"
tag and choose the easiest one to be solved the issue number #1526
https://github.com/openscad/openscad/issues/1526

Please, review it so that I can try to solve other ones. I have send
pull request

https://github.com/openscad/openscad/pull/1601





--
Amarjeet Singh
https://amarjeetkapoor1.wordpress.com
https://github.com/amarjeetkapoor1
https://bitbucket.org/amarjeetkapoor

"knowledge about knowledge is power"

_______________________________________________
OpenSCAD mailing list
[hidden email]
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
Reply | Threaded
Open this post in threaded view
|

Re: Introduction

kintel
Administrator
>
> Please, review it so that I can try to solve other ones. I have send
> pull request
>
> https://github.com/openscad/openscad/pull/1601
>
Thanks!

A few comments:
o Please mention in the commit message and/or pull request description which issue you’ve solved. Otherwise it’s hard to follow the development for other members.
o In issue #1526 there’s a discussion on which shortcut to use. I would recommend posting your suggestion there, asking if anyone disagrees with the choice of shortcut.
o Before merging, we should document the shortcut in the wiki page mentioned in issue #1526
o A tip: Don’t use your master branch for pull requests. If you have more than one pull request open, you’ll run into problems as the pull request automatically tracks your branch.

 -Marius


_______________________________________________
OpenSCAD mailing list
[hidden email]
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
Reply | Threaded
Open this post in threaded view
|

Re: Introduction

Amarjeet Kapoor


   
On Mar 12, 2016 3:27 AM, "Marius Kintel" <[hidden email]> wrote:
> Thanks!
>
> A few comments:
> o Please mention in the commit message and/or pull request description which issue you’ve solved. Otherwise it’s hard to follow the development for other members.
> o In issue #1526 there’s a discussion on which shortcut to use. I would recommend posting your suggestion there, asking if anyone disagrees with the choice of shortcut.
> o Before merging, we should document the shortcut in the wiki page mentioned in issue #1526
> o A tip: Don’t use your master branch for pull requests. If you have more than one pull request open, you’ll run into problems as the pull request automatically tracks your branch.

Thanks for the above. I will take care for all of them.

--
Amarjeet Singh
https://amarjeetkapoor1.wordpress.com
https://github.com/amarjeetkapoor1
https://bitbucket.org/amarjeetkapoor


_______________________________________________
OpenSCAD mailing list
[hidden email]
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
Reply | Threaded
Open this post in threaded view
|

Re: Introduction

Amarjeet Kapoor
As per your suggestion I was understanding the code and found the
issue https://github.com/openscad/openscad/issues/722 from which
customizer project was developed. There were a lot of suggestions like
using meta data, using explicit function or using special keywords
like param for specifying the parameters etc. were given by
contributers of repository that how it should be implemented and what
I was thinking was that we can make all variables assigned values in
.scad file be displayed as parameters and then get information from
user about how they want to change that variable like using ranges,
radio button, also other descriptions etc and then we can  generate
input form from that.

Now I want to Know from you that which approach you want to be used so
that I could be able to write my proposal accordingly.

When I was reading all the issues there was a link of branch, in which
the project was already developed.
https://github.com/openscad/openscad/tree/model-meta-data3

Now what should I do that we need to use different approach for that
project or you want to continue with that only.

While reading code, I found that there are no comments related to
code. Comments should be there for easy understanding. Please add
comments in your code, It will pace up developed and will be easy to
understand.
Currently I'm using doxygen to understand flow of your code but there
is lack of comments.




--
Amarjeet Singh
https://amarjeetkapoor1.wordpress.com
https://github.com/amarjeetkapoor1
https://bitbucket.org/amarjeetkapoor

"knowledge about knowledge is power"

_______________________________________________
OpenSCAD mailing list
[hidden email]
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
tp3
Reply | Threaded
Open this post in threaded view
|

Re: Introduction

tp3
On 03/18/2016 10:28 AM, Amarjeet Kapoor wrote:
> Now I want to Know from you that which approach you want to be
> used so that I could be able to write my proposal accordingly.
>
My view on this topic is that we should follow the existing
prototype code and make it actually usable for at least one
of the use cases, main use case being the actual customizer
logic that sparked the feature request.

This could then be integrated as experimental feature in the
dev versions of OpenSCAD to gather some feedback based on
actual use of this feature.

Details for the proposal we can easier discuss on IRC, which
would also be the main communication channel for code related
discussions, it's easier to clarify those questions in a more
interactive way. So I'd suggest to join there.

> When I was reading all the issues there was a link of branch,
> in which the project was already developed.
> https://github.com/openscad/openscad/tree/model-meta-data3
>
Yes, this has some groundwork in the parser and a partial UI.
It's not really in a state where we can merge it and give it
to users. I do have to refresh my mind about the exact state
of that code, but I think the remaining topics are well
enough to fill the timeline of a GSoC project. And if we
find there's some time left, there's lots of room to expand
to another use case, some of those I started collecting in
https://github.com/openscad/openscad/wiki/Meta-Data-Use-Cases

ciao,
  Torsten.




_______________________________________________
OpenSCAD mailing list
[hidden email]
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
-- Torsten
Reply | Threaded
Open this post in threaded view
|

Re: Introduction

Amarjeet Kapoor
On 19 March 2016 at 20:56, Torsten Paul <[hidden email]> wrote:
> Yes, this has some groundwork in the parser and a partial UI.
> It's not really in a state where we can merge it and give it
> to users. I do have to refresh my mind about the exact state
> of that code, but I think the remaining topics are well
> enough to fill the timeline of a GSoC project. And if we
> find there's some time left, there's lots of room to expand
> to another use case, some of those I started collecting in
> https://github.com/openscad/openscad/wiki/Meta-Data-Use-Cases

I have figure out some features by talking to some of my group and
civil students regarding UI that I am sharing for feedback-:

1. Make UI modular so as make it easy to work and adjust panels
according to users need (like that of gimp)
2. grouping of parameters
3. collapsing and expanding of individual parameter widget.
4. option to hide certain parameters from display.
5. saving .scad file without annotation code after setting value of
parameters it will make scad file backward compatible.
6. option to make slider vertical (as for parameter like height it
would make more appealing with vertical slider).
7. possibly radio buttons.

and their is last one for which I don't the difficulty level of this.

8. A Pearson get list of all parameter associated with the object by
clicking on it in view plane.( like a Pearson click on cube in a
drawing he may get all parameter associated with that square in
parameter widget).

Please share the if some issues associated with parser are their and
share your feedback for above suggestions



--
Amarjeet Singh
https://amarjeetkapoor1.wordpress.com
https://github.com/amarjeetkapoor1
https://bitbucket.org/amarjeetkapoor

"knowledge about knowledge is power"

_______________________________________________
OpenSCAD mailing list
[hidden email]
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
Reply | Threaded
Open this post in threaded view
|

Re: Introduction

jpmendes

Useful from my point of view would be an input console line acting on the view-port to pan, rot, zooming, and defining rotation point in an easy typing way like:

r(x,y,z) t(x,y,z), z(v), rp(x,y,z), or even better: rx, ry, rz, etc

Optionally a reset viewpoint command "rv" without automatic zoom would be useful, although this option already exist in a UI button for viewing all the scene.
The standard views are not enough and using $vpr and $vpt in the script is not user friendly, and for complex multi-part objects is an head ache. The use of mouse drives me crazy mostly because the extreme lag and the lack to define a rotation point.

jpmendes





Reply | Threaded
Open this post in threaded view
|

Re: Introduction

Amarjeet Kapoor
On 21 March 2016 at 21:09, jpmendes <[hidden email]> wrote:
>
> Useful from my point of view would be an input console line acting on the
> view-port to pan, rot, zooming, and defining rotation point in an easy
> typing way like:
>
> r(x,y,z) t(x,y,z), z(v), rp(x,y,z), or even better: rx, ry, rz, etc
>

You mean to say a separate command line mode like control below view
port to control the view point.

> Optionally a reset viewpoint command "rv" without automatic zoom would be
> useful, although this option already exist in a UI button for viewing all
> the scene.

A shortcut key can be added for reset view.

> The standard views are not enough and using $vpr and $vpt in the script is
> not user friendly, and for complex multi-part objects is an head ache. The
> use of mouse drives me crazy mostly because the extreme lag and the lack to
> define a rotation point.
>





--
Amarjeet Singh
https://amarjeetkapoor1.wordpress.com
https://github.com/amarjeetkapoor1
https://bitbucket.org/amarjeetkapoor

"knowledge about knowledge is power"

_______________________________________________
OpenSCAD mailing list
[hidden email]
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
Reply | Threaded
Open this post in threaded view
|

Re: Introduction

togo

Like this idea. Maybe if I could hit r for render or b for build, f5 can go back to being find next as my muscle memory keeps demanding

--
sent from nexus c
   

On Mar 21, 2016 10:13 PM, "Amarjeet Kapoor" <[hidden email]> wrote:
On 21 March 2016 at 21:09, jpmendes <[hidden email]> wrote:
>
> Useful from my point of view would be an input console line acting on the
> view-port to pan, rot, zooming, and defining rotation point in an easy
> typing way like:
>
> r(x,y,z) t(x,y,z), z(v), rp(x,y,z), or even better: rx, ry, rz, etc
>

You mean to say a separate command line mode like control below view
port to control the view point.

> Optionally a reset viewpoint command "rv" without automatic zoom would be
> useful, although this option already exist in a UI button for viewing all
> the scene.

A shortcut key can be added for reset view.

> The standard views are not enough and using $vpr and $vpt in the script is
> not user friendly, and for complex multi-part objects is an head ache. The
> use of mouse drives me crazy mostly because the extreme lag and the lack to
> define a rotation point.
>





--
Amarjeet Singh
https://amarjeetkapoor1.wordpress.com
https://github.com/amarjeetkapoor1
https://bitbucket.org/amarjeetkapoor

"knowledge about knowledge is power"

_______________________________________________
OpenSCAD mailing list
[hidden email]
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org

_______________________________________________
OpenSCAD mailing list
[hidden email]
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
tp3
Reply | Threaded
Open this post in threaded view
|

Re: Introduction

tp3
On 21 March 2016 at 21:09, jpmendes wrote:
>
> Useful from my point of view would be an input console line acting on the
> view-port to pan, rot, zooming, and defining rotation point in an easy
> typing way like:
>
> r(x,y,z) t(x,y,z), z(v), rp(x,y,z), or even better: rx, ry, rz, etc
>
Interesting idea. Blender has a similar type of control which is
very useful, and I've seen that in other places too.

Von: "Tony Godshall"
> Like this idea. Maybe if I could hit r for render or b for build,
> f5 can go back to being find next as my muscle memory keeps
> demanding
>
Right, I guess that could be extended to most of the GUI actions
available, not just to viewport manipulation.

Actually the core infrastructure for the feature itself is already
part of the branch that is working on adding more input devices
(mainly for 3d-mouse devices, but at least for Linux this could
easily add an udev-based remote control command interface).

That topic is a bit different from the meta-data/customizer discussion,
so I guess it would be better to continue in a separate thread and
not mix both...

ciao,
  Torsten.


_______________________________________________
OpenSCAD mailing list
[hidden email]
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
-- Torsten
tp3
Reply | Threaded
Open this post in threaded view
|

Re: Introduction

tp3
In reply to this post by Amarjeet Kapoor

On 21 March 2016 at 14:33 Amarjeet Kapoor wrote:
> 1. Make UI modular so as make it easy to work and adjust panels
> according to users need (like that of gimp)
>
We are a bit restricted by the features Qt provides, which
is not as nice as Gimp shows with the flexible docking&floating
windows. But it should be possible to find way that's working
well enough.

> 2. grouping of parameters
>
For bigger models, that's useful for sure.

> 3. collapsing and expanding of individual parameter widget.
>
That probably depends a bit on what a single widget
will show. It might be a bit tedious to open and
collapse lots of small widgets.
Assuming we want to show a long description for all
the parameters, maybe there could be a single on/off
for  all the detailed descriptions to make more room for
the actual parameters?

> 4. option to hide certain parameters from display.
>
If we annotate the parameters to show, we'll get that
automatically. I think it's good to not just show all
available variables.

> 5. saving .scad file without annotation code after
> setting value of parameters it will make scad file
> backward compatible.
>
This might be useful, but I'd rate it as relatively
low priority as it's main usefulness is for the time
of migration (which could be a couple of years though).

> 6. option to make slider vertical (as for parameter
> like height it would make more appealing with vertical
> slider).
>
Good point, in a more general way this is would give
the user a way to define options for the actual
presentation of the parameter. In the simple case
this could be automatically determined based on the
values the user specified, but having some addtional
control about the presentation might be useful.

> 7. possibly radio buttons.
>
This should be covered by a generalized point 6.

> 8. A Pearson get list of all parameter associated with
> the object by clicking on it in view plane.( like a
> Pearson click on cube in a drawing he may get all
> parameter associated with that square in parameter
> widget).
>
Object picking would be a very nice thing to have,
but I think that's a bigger topic in itself, so I'd
recommend to leave that as separate project.

ciao,
  Torsten.

_______________________________________________
OpenSCAD mailing list
[hidden email]
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
-- Torsten
Reply | Threaded
Open this post in threaded view
|

Re: Introduction

Amarjeet Kapoor
On 22 March 2016 at 23:23, Torsten Paul <[hidden email]> wrote:
>
> On 21 March 2016 at 14:33 Amarjeet Kapoor wrote:

Thank you for your views but their are some features which I was not
able to convey
correctly.

>> 4. option to hide certain parameters from display.
> If we annotate the parameters to show, we'll get that
> automatically. I think it's good to not just show all
> available variables.
>

I was explaining the situation when person has annotated the variable
and he has been changing the value from form but he want to fix that
particular value for some time and want to remove that parameter from
parameter form so has to make room for other parameters in that
widget.


>> 5. saving .scad file without annotation code after
>> setting value of parameters it will make scad file
>> backward compatible.
>>
> This might be useful, but I'd rate it as relatively
> low priority as it's main usefulness is for the time
> of migration (which could be a couple of years though).

We can modify this feature that is we can assign new values to
variables from form i.e changes we made to model through form are
temporary, don't exist after we open that model file again but we can
make it permanent in program.




--
Amarjeet Singh
https://amarjeetkapoor1.wordpress.com
https://github.com/amarjeetkapoor1
https://bitbucket.org/amarjeetkapoor

"knowledge about knowledge is power"

_______________________________________________
OpenSCAD mailing list
[hidden email]
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
Reply | Threaded
Open this post in threaded view
|

Re: Introduction

Amarjeet Kapoor
In reply to this post by Amarjeet Kapoor
I have written project proposal according to features that I think could
be added you can suggest more.
Milestones are not fixed till now.

Need your review on it

https://docs.google.com/document/d/1hXXQI0PEPQnu6e-x0huNQsMt_3Ocn8aBtpwJ_0C-uiM/edit#heading=h.n3vseu6e2l4g

--
Amarjeet Singh
https://amarjeetkapoor1.wordpress.com
https://github.com/amarjeetkapoor1
https://bitbucket.org/amarjeetkapoor

"knowledge about knowledge is power"

_______________________________________________
OpenSCAD mailing list
[hidden email]
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
tp3
Reply | Threaded
Open this post in threaded view
|

Re: Introduction

tp3
On 03/23/2016 11:55 AM, Amarjeet Kapoor wrote:
> I have written project proposal according to features that I think
> could be added you can suggest more.
>
Thanks. Just a quick first response...

The detailed description already has some good points and
lists examples for the topics we discussed. That looks
like a good base for approaching the project and defining
the specific things to do.

The Milestones part could use some more details. I know it's
not easy to give a very detailed plan for this type of project
with a number of unknowns that will only become clear in the
first phase. So one option to get the steps a bit clearer
could be to explain how you want to approach the different
parts of the project.
So what I mean is basically the first part of the proposal
list some things to do with "We can...", the milestone part
should outline the (small) steps that say how it will be
possible to decide what will be done, ideally on a weekly
basis.

(Note that weekly here mainly stands for "something that
might be done in a couple of days and does not need like
3 weeks"; The timeline given will be guideline, not a strict
work plan and can be adjusted)

ciao,
  Torsten.


_______________________________________________
OpenSCAD mailing list
[hidden email]
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
-- Torsten
Reply | Threaded
Open this post in threaded view
|

Re: Introduction

jpmendes
In reply to this post by Amarjeet Kapoor
Hello,

Maybe I'm wrong but I'm not enthusiastic about the use of sliders on the UI. I would prefer a direct entry of values or both options. Since we do not have real variables, each time you move a slider the script is recompiled to reflect the actual state, when the project gets complicated the lag will be not negligible if not insupportable. And not everybody have top speed machines.
With direct entree boxes you could define ranges for the parameters and observe the respective evolution result.
Another thing I feel is important, although outside the scope of the UI, would be the existence of an echof() echo to file functionality. That would allow the recording of parameters, or even better, interacting with the outside world. For instance the use of sound, or performing real actions.  I'm seeing for instance a python script interacting with the logs from the OpenSCAD app.

jpmendes

12