[Bf-extensions-cvs] SVN commit: /data/svn/bf-extensions [913] external: == External Extensions ==

[Luca Bonavita]

Revision: 913
          http://projects.blender.org/plugins/scmsvn/viewcvs.php?view=rev&root=bf-extensions&revision=913
Author:   mindrones
Date:     2010-08-17 01:40:48 +0200 (Tue, 17 Aug 2010)

Log Message:
-----------
== External Extensions ==

Starting this folder after discussing with Ton about:
- addons that are not developed in bf-extensions, or
- addons that need binaries not developed in bf-extensions.

Examples are luxrender, yafaray, gamekit, etc...

This folder has not to be used as a development tool but just as a mirror of development work being done elsewhere.

The only development permitted in this folder is for fixing Blender API changes: developers of the external projects can then merge these fixes 
in their repository. Hopefully the API will stabilize soon and there will no need for this.

Please read external/README.txt to get a picture of the proposed workflow.

Added Paths:
-----------
    external/
    external/README.txt
    external/py/
    external/py/scripts/
    external/py/scripts/addons/

Added: external/README.txt
===================================================================
--- external/README.txt	                        (rev 0)
+++ external/README.txt	2010-08-16 23:40:48 UTC (rev 913)
@@ -0,0 +1,86 @@
+EXAMPLE OF DEVELOPMENT CYCLE FOR AN ADDON DEVELOPED OUTSIDE OF BLENDER.ORG
+AND THAT COULD NEED A BINARY ALSO DEVELOPED OUTSIDE OF BLENDER.ORG
+
+------------------------------------------------------------------------
+
+This example is based on a discussion with Doug Hammond (dougal2) 
+from the Luxrender dev team, hence I use Lux here as a practical example.
+To clarify:
+"luxrender" = name of the addon
+"luxblend" = python exporter blender -> lux, it can:
+    - export ascii file to be read, or
+    - use pylux to show lux renders inside blender render view
+"pylux" = name of the binary
+
+------------------------------------------------------------------------
+
+We start with:
+- Blender 2.53 (which has a 2.53 Python API)
+- Lux 0.7
+
+We have:
+external/py/scripts/addons/luxrender/0.7/luxblend/<python files>
+external/py/scripts/addons/luxrender/0.7/pylux/linux/32/pylux.so
+external/py/scripts/addons/luxrender/0.7/pylux/linux/64/pylux.so
+external/py/scripts/addons/luxrender/0.7/pylux/windows/32/pylux.pyd
+external/py/scripts/addons/luxrender/0.7/pylux/windows/64/pylux.pyd
+external/py/scripts/addons/luxrender/0.7/pylux/osx/universal/pylux.so
+
+which gets imediately tagged to:
+
+tags/2.53_external/py/scripts/addons/luxrender/0.7/luxblend/<python files>
+tags/2.53_external/py/scripts/addons/luxrender/0.7/pylux/linux/32/pylux.so
+tags/2.53_external/py/scripts/addons/luxrender/0.7/pylux/linux/64/pylux.so
+tags/2.53_external/py/scripts/addons/luxrender/0.7/pylux/windows/32/pylux.pyd
+tags/2.53_external/py/scripts/addons/luxrender/0.7/pylux/windows/64/pylux.pyd
+tags/2.53_external/py/scripts/addons/luxrender/0.7/pylux/osx/universal/pylux.so
+
+IMPORTANT NOTE:
+
+When The Blender API changes, Blender API developers do updates in 
+external/py/scripts/addons/luxrender/ to fix changes.
+These gets merged in the Lux repository, where the development can then continue.
+
+------------------------------------------------------------------------
+
+Later, Lux devs release Lux 0.8, hence in bf-extensions we will have:
+
+external/py/scripts/addons/luxrender/0.8/luxblend/<python files>
+external/py/scripts/addons/luxrender/0.8/pylux/linux/32/pylux.so
+external/py/scripts/addons/luxrender/0.8/pylux/linux/64/pylux.so
+external/py/scripts/addons/luxrender/0.8/pylux/windows/32/pylux.pyd
+external/py/scripts/addons/luxrender/0.8/pylux/windows/64/pylux.pyd
+external/py/scripts/addons/luxrender/0.8/pylux/osx/universal/pylux.so
+
+which is in line with Blender 2.53 API and uses the new Lux 0.8 binary.
+
+We tag it in bf-extensions:
+
+tags/2.53_external/py/scripts/addons/luxrender/0.7/luxblend/<python files>
+tags/2.53_external/py/scripts/addons/luxrender/0.7/pylux/linux/32/pylux.so
+tags/2.53_external/py/scripts/addons/luxrender/0.7/pylux/linux/64/pylux.so
+tags/2.53_external/py/scripts/addons/luxrender/0.7/pylux/windows/32/pylux.pyd
+tags/2.53_external/py/scripts/addons/luxrender/0.7/pylux/windows/64/pylux.pyd
+tags/2.53_external/py/scripts/addons/luxrender/0.7/pylux/osx/universal/pylux.so
+tags/2.53_external/py/scripts/addons/luxrender/0.8/luxblend/<python files>
+tags/2.53_external/py/scripts/addons/luxrender/0.8/pylux/linux/32/pylux.so
+tags/2.53_external/py/scripts/addons/luxrender/0.8/pylux/linux/64/pylux.so
+tags/2.53_external/py/scripts/addons/luxrender/0.8/pylux/windows/32/pylux.pyd
+tags/2.53_external/py/scripts/addons/luxrender/0.8/pylux/windows/64/pylux.pyd
+tags/2.53_external/py/scripts/addons/luxrender/0.8/pylux/osx/universal/pylux.so
+
+------------------------------------------------------------------------
+
+Later, Blender 2.54 gets released. We make changes in external/ and then tag:
+
+tags/2.54_external/py/scripts/addons/luxrender/0.8/luxblend/<python files>
+tags/2.54_external/py/scripts/addons/luxrender/0.8/pylux/linux/32/pylux.so
+tags/2.54_external/py/scripts/addons/luxrender/0.8/pylux/linux/64/pylux.so
+tags/2.54_external/py/scripts/addons/luxrender/0.8/pylux/windows/32/pylux.pyd
+tags/2.54_external/py/scripts/addons/luxrender/0.8/pylux/windows/64/pylux.pyd
+tags/2.54_external/py/scripts/addons/luxrender/0.8/pylux/osx/universal/pylux.so
+
+------------------------------------------------------------------------
+
+And so on.
+


Property changes on: external/README.txt
___________________________________________________________________
Name: svn:eol-style
   + native