[Bf-committers] 2.49: prevent reading 2.5+ ?

[blender at erwincoumans.com]

It is sad to see you plan to break forward compatibility, the .blend 
fileformat had this great backward/compatibility feature for over 10 years 
now. 

Is there no way to fix mesh compatiblity? Joe's recent email about Mesh 
development freeze seem to be related to this: 

joe <joeedh at gmail.com> wrote
>>Converting editmesh to/from bmesh for tools turned 
>>out to not be stable enough to be releasable.

Is there a way to make this conversion stable? 

Thanks,
Erwin 


Ton Roosendaal writes: 

> Hi all, 
> 
> Currently 2.48 and older will still read 2.5+ files, but without the UI 
> (obviously). That was still sort-of acceptable. 
> 
> Now with new animation system, all of the motion data will get lost if 
> you read 2.50 .blends in older versions. And even worse, the plans for 
> bmesh also include minor upgrades in Mesh data, making it unreadable in 
> older versions too. 
> 
> Without animations or meshes, there's not much use keeping 'forward' 
> compatibility. It's even very hard to predict if you don't get crashes 
> even... So, my proposal would be: 
> 
> - Add in 2.49 (trunk) a warning menu + failure to read 2.5+ .blend 
> files.
> - Make 2.5 save the ~/.B.blend as ~/.B25.blend (this to prevent 
> usability issues). 
> 
> -Ton- 
> 
> ------------------------------------------------------------------------
> Ton Roosendaal  Blender Foundation   ton at blender.org    www.blender.org
> Blender Institute BV  Entrepotdok 57A  1018AD Amsterdam The Netherlands 
> 
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers