Hi; On Sun, 2007-08-26 at 05:40 +0100, Alberto Ruiz wrote: [snip - all interesting] > > - What should I do to make an actor not to waste any video memory > - Should I implement the Async/LazyActor as an interface? May I > implement it as a ClutterContainer to be able to show the > PendingTaskActor as well? > - How can I make the PendingTaskActor not to waste any video memory > once the content is loaded? > - Should I split the AsyncActor and the LazyActor as different > interfaces? > - Am I on crack?
No, definitely not - But Im not sure what the best solution is to handling and managing things like texture memory better. One idea I've had is a ClutterTextureProxy which would release texture memory under defined conditions (i.e goes to position offscreen) by unrealizing an underlying texture to free memory but still behave API wise like it was still there. Still thinking about this.. The best I can suggest is implement it and experiment so we get a better understanding. Just note we want to keep the clutter core pretty raw and generic but very flexible. For very high level and very specific functionality we've talked about creating a separate clutter-extras or some such package. Many thanks; -- Matthew -- To unsubscribe send a mail to [EMAIL PROTECTED]
