[Bf-committers] Proposed changes re: procedural textures

[Joe Eagar]

Emanuel Greisen wrote:
>
>> I'd been thinking about this; collisions would only be a problem for 
>> plugins, and I'd imagined Blender assigning each plugin an ID in the 
>> order they are loaded, starting at 1 greater than the highest builtin 
>> ID. Then it writes a list of plugin filenames so it knows which 
>> plugin corresponds to which generated ID.
>
> Collisions might also occur in built-in. Assume some developer of 
> built-in textures is both developing a new texture AND making cool 
> blender scenes. The same goes for some other developer (assume two 
> teams like Orange project working at the same time, at two different 
> places). Now they are both done, and want to commit back to the 
> core-blender-trunk.... they have both taken the same "next-id", hence 
> one of them will have to take the next one, and then all their blender 
> files will have the wrong textures when running with the latest 
> blender version. Actually, if the core team deside at some point in 
> time to remove procedural texter X, then X+1 will become X, X+2 will 
> become X+1, and so forth. This means that any old blenderfile will 
> have incorrect textures.... due to shifting in indexes !
One way to fix that is to write a temporary version patch that changes 
the plugin version on load.  Basically you write code in readfile.c in 
do_versions() that fixes everything. :)  Then once you convert your 
files you remove the code.

Joe