Parametric design in MoI?

 From:  mkdm
7713.556 In reply to 7713.553 
Hi Karsten and good morning!

It was bound to happen and finally it did!!

Thank you very much for your work!!!

I think that now we are going into the right direction, in order to straighten up a all the (actually) messy things related to Project Elephant.

Your idea goes exactly in the same direction I wanted to take with my "Project Elephant's UNOFFICIAL Repository" thread,
that i created some days ago (http://moi3d.com/forum/index.php?webtag=MOI&msg=8197.1).

But IMHO using Moi's Wiki-System it's definitely the best thing!!

With your page, my "Project Elephant's UNOFFICIAL Repository" thread it's now totally useless, and it's for the best.

> "..If you have ideas for improvements or find mistakes - let me know"

Well, I think that could be a very good thing to replicate in those Wiki pages,
a section where anyone can easily seek and download all the various versions of Projects Elephant written right now.
A section similar to that I described in my "Project Elephant's UNOFFICIAL Repository" thread.

I'd like to suggest a standardized format for its entries :

code:
########################
- (<Version Code>) Project Elephant version : <Versione Name>
- downloadable at <Download Url>
- Support files :
     - <Support file title 1>
       <Support file Download Url 1>
     ...
     ...
     - <Support file title N>
       <Support file Download Url N>
########################


Where :

- <Version Code> : simply an incremental counter starting from 0 (zero)
   If you want, you can even get rid of this information.

- <Version Name> : for example : "Project Elephant v.0.85mod3"

- <Download Url> : a public link to download the ZIPPED version of that Project Elephant

- Support files : i think that this is the most important section.

  It should include anything useful to easily know and learn all the updates occurred in that version.
  For example it could include a list like this :
       - Latest changes
         <Url to a txt file>
        (I think that TXT format it's the best because it's readable by anyone.)
      - A video or some screen capture of the nodes in action
        <Url of the video or the pictures>
     - One or more .nod files (this is very important in order to easily learn latest functionality)
        <Url of the .nod file>
     - A TXT file that explain the .NOD files
        <Url of the .TXT file>



I sincerely hope that Max will appreciate all these efforts.

See you and thanks again Karsten.

Please, let me know what do you think of this ideas.

Best,

- Marco (mkdm)

EDITED: 1 Dec 2016 by MKDM