[haiku-development] Re: Compositing window management

  • From: "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Wed, 15 Jun 2011 13:31:02 +0200 (MEST)

Clemens<clemens.zeidler@xxxxxxxxxxxxxx> wrote:
> was thinking the same while reading it :-) Thanks for the nice overview!  
> One question, would it make sense to be able to switch between compositing 
> and the current drawing mode?

Something like this would certainly not be just nice for older or embedded 
hardware but pretty much mandatory.
But while this would probably quite complicate things when taken into account 
right from the start. In the end, the per window memory buffers should be 
maintained similar to direct windows -- this would also allow to continue to 
draw them into a single frame buffer if needed, and to allocate them only when 
needed (ie. make it a real cache whose data can be recreated if needed).

In the long run, the Painter classes should be moved into libbe.so, and drawing 
should then be possible client side as well (optionally, since older hardware 
will still want to benefit from acceleration, etc., but this could also be 
possible by cloning the accelerant into the client, just like some games 
currently do).


Other related posts: