[Bf-committers] request for 2.49?

[Ton Roosendaal]

Hi,

During our game project, a similar topic for CS export came up.
A reliable method for this is complex though, data changes in Blender 
happen all over, and much out of sight of the caller functions.

In 2.5 there's a bit better control, editors can register listeners to 
catch notifications about changes. Also this is not precise or exact 
though, but mainly to define whether UI should refresh.

A good start would be if we first develop our own preview render to 
handle incremental changes well; then such code is maintained and 
tested well, and usable for others.

Certainly not "simple addition" here, and not to rush in for 2.49 
really!

-Ton-

------------------------------------------------------------------------
Ton Roosendaal  Blender Foundation   ton at blender.org    www.blender.org
Blender Institute BV  Entrepotdok 57A  1018AD Amsterdam The Netherlands

On 15 Apr, 2009, at 14:46, Terrence Vergauwen wrote:

> Hi guys,
>
> Don't know if it's too late to ask this at the moment,
> but with a simple addition to 2.49, you could make the life of 
> luxrender and
> other projects a lot easier.
>
> As you know, we are currently exporting scene data, geometry for 
> objects and
> materials to external file(s) for external renderers.
> This can get quite slow when users are finetuning a scene's materials, 
> often
> needing to relaunch a lot of renders with slow response as the exporter
> python script needs to reexport everything.
> To work around this we've used some tricks like separating objects and
> materials in to separate exports, but this workflow is very complex 
> for most
> users.
>
> Would it be possible to add a flag to a blender object's data, a bit 
> like
> created/modified timestamps in a filesystem ?
> I've already inquired about achieving this on #blendercoders a while 
> ago and
> everyone responded that this is'nt currently possible at all.
>
> If blender could set a flag 'modified' or update a 'modified 
> timestamp' on
> objects everytime the data is changed we could use this to only export 
> the
> changed objects and make everything much more fluent.
> I guess this could serve lots of other purposes later on too.
>
> Radiance
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers
>