search

BlenderVR / source

Blender Virtual Reality Main Code
52 stars 21 forks source link

Decide on a name and stick to it #30

Closed dfelinto closed 9 years ago

dfelinto commented 9 years ago

We are using different names in the documentation: blenderVR, Blender-VR, BlenderVR. We should stick to one and go with it.

My suggestion is either BlenderVR or Blender-VR

PyrApple commented 9 years ago

go for BlenderVR!

Le 7 avr. 2015 à 15:58, Dalai Felinto notifications@github.com a écrit :

We are using different names in the documentation: blenderVR, Blender-VR, BlenderVR. We should stick to one and go with it.

My suggestion is either BlenderVR or Blender-VR

— Reply to this email directly or view it on GitHub.

dfelinto commented 9 years ago

I updated the manual (blenderVR | Blender-VR > BlenderVR), but not the main source code or the samples.

To do so all we need is the following: for i in find -name *.py; do sed 's/blenderVR/BlenderVR/g' $i > /tmp/a; mv /tmp/a $i; done

But by doing so it will be a bit of a pain to merge the ieee branches in master. So once we are done with them we can proceed with the above.

dfelinto commented 9 years ago

done

PyrApple commented 9 years ago

Yop,

I would say we stuck to blenderVR for variables and BlenderVR for strings? (or is it such a pain that we'd rather change everything into BlenderVR for the moment?)

David

Le 8 avr. 2015 à 00:49, Dalai Felinto notifications@github.com a écrit :

done

— Reply to this email directly or view it on GitHub.

PyrApple commented 9 years ago

Which would force us to change every sample and configuration file.

++ variable: .blenderVR | strings BlenderVR

David

Le 8 avr. 2015 à 12:30, David Poirier-Quinot davipoir@gmail.com a écrit :

Yop,

  • the modif of strings "blenderVR" to "BlenderVR", ok.
  • the modif of every .blenderVR variable to BlenderVR: 1) wise? (pep-8, etc.) 2) not coherent for the moment (i.e. ./BlenderVR launch fails because BlenderVR

I would say we stuck to blenderVR for variables and BlenderVR for strings? (or is it such a pain that we'd rather change everything into BlenderVR for the moment?)

David

Le 8 avr. 2015 à 00:49, Dalai Felinto notifications@github.com a écrit :

done

— Reply to this email directly or view it on GitHub.

dfelinto commented 9 years ago

I would say let's change everything now (pre-1.0) and stick to it. Poke me on Skype to sync/coordinate if you think otherwise. (The samples were updated yesterday already, and today I updated the sample configuration files)