[interfacekit] Re: :) Again - BBitmap

> 3) Cloning Accelerants - It's a good idea, it has hardware acceleration, but
> we have to write some clipping code and a library to help us make calls like
> StrokeLine(). 

Yeah, that was also be's idea. If you read this article:

http://www.beatjapan.org/mirror/www.be.com/developers/March98/presentations/BDirectWindow/index.html

especially in this part:

"A Speaker: You were saying at the beginning one of the limitations of this was 
that there isn't much rendering support. Is that something that's on the 
drawing board? 

Pierre Raynaud-Richard: That's a good question. Again, imagine in the current 
graphic system everything you need to draw in that sort of direct frame access, 
with all the different modes and clipping, region, it's in the app server. We 
use it to draw. What we need is to clean it, restructure it, make it more like 
a share library so that later it will be directly accessible by the client in a 
different context. So like draw a line, direct, whatever, draw a stream and do 
it through a DirectWindow but on the client's side. But currently it's not 
available and won't be for some time, because before releasing a new API of 
that importance, we want to clean things up. Because once it's done, it's done. 
We have to stay compatible with it for a long time. 
"

In my opinion, we should stay as much close as possible at R5, at least in our 
first release.
We chose the R5 design so we wouldn't have wasted time in design work, right ? 

An example of the desing time we could "waste" is represented by the private 
storage api Ingo has implemented. Just look back at the time/work Ingo has put 
into them, since we weren't going to follow R5 design (I can't say if it's been 
a good or bad decision, that's just a fact).

Other related posts: