Hi,
the drag and drop thing seems very non-intuitive to me. Also it's
weird that you have to drag and drop it over the 3D canvas area. I
would prefer Paste button.
Miro Hrončok

Telefon: +420777974800

2015-03-20 8:56 GMT+01:00 Shaina Sabarwal iamshainasabarwal@gmail.com:

On 03/20/2015 08:56 AM, Shaina Sabarwal wrote:

Just to comment on what's already there... it's basically prototyping
code for two use cases.

1. Define Parameters for a specific Model

   We have a simple keychain that needs some basic features to be
   configurable for other people to use, e.g.

   • The length, width and height of the keychain
   • The text to write on it
   • The diameter of the hole

   This is essentially what the Thingiverse customizer is doing

2. Define Parameters for Parts in a Library

   This refers to libraries like MCAD and maybe even more BOLTS. Right
   now, there is no UI support for using those. For example using
   a M4 bolt from BOLTS is:

   include <BOLTS/BOLTS.scad>
   ISO4014(key = "M4", l = 20);

   So you have to know what parameters are needed / possible. BOLTS
   has a very good documentation, but I think it would be even more
   user friendly if we can just add the include<>, start the compile
   and now a list of all library parts is available with included
   documentation for the parts and the parameters.

   Later we might even have that available via web with some kind of
   library index, but that's a different topic :-).

I'm sure there are more use cases and/or additional variations to the
two described above (e.g, saving parameter sets for the models from use
case 1).

ciao,
Torsten.

Have a look at:  https://www.youtube.com/watch?v=DRS6dhyvU-E

This is some impressive costumisation.

2015-03-20 19:48 GMT+01:00 Peter Falke stempeldergeschichte@googlemail.com
:

--
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!

Ahh, nice example. I guess that's pretty much what we could do when saving
sets of model parameters along with the model itself.
A table view seems to be quite a useful thing, I hope it's not possible to
patent such a thing?

ciao,
Torsten.

On 03/22/2015 03:48 PM, Peter Falke wrote:

Shaina Sabarwal wrote

Thanks for you efforts last year BTW, OpenSCAD is now a lot more user
friendly and starting to look professional.

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/Fwd-OpenSCAD-Customizer-tp12090p12142.html
Sent from the OpenSCAD mailing list archive at Nabble.com.

On Wed, Mar 25, 2015 at 2:58 AM, mitch mtchkll@gmail.com wrote:

I wish we could, but I have moved to other project for this summer, as
the Customizer of the OpenSCAD is at its first step and it requires
more discussions before implementing new features. That's what
understood by talking to mentors.

--
Shaina Sabarwal
blog: shainasabarwal.wordpress.com
github: github.com/shaina7837

You don't have to be great to start but start to be great.

On 03/24/2015 11:09 PM, Shaina Sabarwal wrote:

Yes, it would probably possible to forward the work on this but with the
discussions needed, the timeline is hard to set. Also it's unlikely to
get to a state that could go into a release after the 3 month of GSoC
project. Having things merged is no requirement for GSoC results but I
think the chance of getting the work merged is a nice additional
motivation.

So while it's not an ideal GSoC project, we still can get the discussion
going. Especially regarding libraries it would be nice to collect things
that would make usage much more user friendly than just "use <library.scad>".

ciao,
Torsten.