[Bf-committers] blender toolkit [Re: blender sub-components]

Ton Roosendaal bf-committers@blender.org
Thu, 15 Jan 2004 11:49:41 +0100


>> It will be quite difficult, but possible. However, you might end up
>> then with a library that is not used by Blender itself.
> that is my main fear actually. there several parts of blender [or of  
> the
> future blender] which i'd like to reuse in my own application, GUI
> design and real time engine being the most prominent.
> will Blender always remain "everything in one" monolith? i don't mean
> the application, but it's code. i would think splitting the code into
> more easily reusable pieces could attract other developers to (a) reuse
> these pieces (b) contribute to them. the whole source code could still
> be kept in one "hierarchical" source tree, and "cvs co blender" would
> get it all, but say "cvs co ghost" would only checkout ghost, without
> the need for ghost to be separate desynchronized project.

Hah, there's a gap between 'having plans' and finishing them. :)

Some things just need time. Developers getting familiar with parts of  
the code is the first step, which steadily happens for more and more  
parts. What still works best is little steps forward, small projects  
that immediate benefit using Blender in a next release.
If you are motivated for working on the UI code, it might work best to  
help on our current Blender related projects first. Based on that  
experience you can much easier decide what's feasible or interesting  
todo in modularizing code. Which *is* something we'd like, but not by  
sacrificing all progress for a long period.


Ton Roosendaal  Blender Foundation ton@blender.org