export script development in wiki

[wuzpuz]

As everybody knows indigo export script for blender lives on blender mediawiki page..

I created /0.6 subpage to this page, where the active development could be done... I imagine that workflow could go as following:

1. open page, look at history to see what other people have been working on
2. copy-paste page into text editor, make changes, save file as .py file in your .blender/scripts directory to test
3. if everything is good and you happy with your changes, edit wiki subpage and copy-paste from text editor (the whole new page or only changes) back to wiki to make it public. comment box in wiki editor might be very useful.
4. check in history that changes are actually the ones which you wanted to be
5. in case of any bigger modification/useful feature addition/etc, create zip and upload it to Indigo_exporter page, and post comment here in forum (like before).

That kind of workflow would make it easy to manage development better (see what's going on, better interaction between developers), with wikimedia software having coordinating role..

What do you think? This all good?

[leope]

My contribute at the script depends too much to my spare time (i play also with other 3d sw like AOI) and other things and is "in primis" for my purpose (fun), so in general don't like to be in a workgroup...
I prefer:
1.Grab a OS script file "X".
2.Open it directly in the blender editor so i can edit and test it immediatly avoiding tab/space indentation issues (if i'm right blender editor don't support clipboard).
3.Modify the script 1% at 99% and give the credits at the original authors (keeping their names)
4.Release the modded script "Y" in a place in the net asking for someone interested.
5.If the original script "X" is updated in "Z" and has some feature, "a" that i like, or i modify the script
"Y" adding the feature "a" or i modify the script "Z" with my code: my code that can be in contrast with
the code of the other autors but i prefer (e.g. default settings, way to solve a problem, syntax (for my better reading) etc.).
6.If anyone ask for a feature, if i can, i add that feature.
7.Release the modded script "K" modded from "Z" or "Y" with my defaults&c in a place in the net asking for someone interested.
8.Sure anyone can grab the modded script "Y" or "K" and make their own modifications or merge two or more version of the script in a new one.
etc.
etc.

I started in this way. Then asked for post at wiki so i posted at wiki like an official version, but i'm not sure...
if my mods will be in contrast with the official script i think i not post my modded script at wiki unless different version of script will be officially permitted

I thik all this sounds pretty egoist but it's the easy way for me.



In Italiano:
"Non voglio impegnarmi troppo e creare troppe aspettative o dover scrivere codice
che mi interessa relativamente" ed in aggiunta con indigo ci gioco via wine, il che non e'
che mi entusiasmi molto. Sono veramente un
Inoltre la gui si sta saturando e un eventuale supporto a materiali procedurali o altre cose complesse
e' decisamente fuori dalle mie competenze (confido anche io in zuegs).

Translated by www_dot_reverso_dot_net
"I don't want to hock too much me and to create too expectations or to have to write code that relatively interests me" and additionally with indigo I play away there wine, which not and' that I/you/he/she thrill a lot me. I am really a
Besides the gui he is saturating and a possible support to material procedural or other complex things and' decidedly out of my competences (I also confide in zuegs).



bye
leope

PS:blender2pov, blender2KT... waiting for blender2indigo...

PPS: Maybe this is the worst [english] post i've made.