[interfacekit] Re: App Server Startup procedures and question

>Any that aren't available for a given driver, we'll have to implement.  
>Since none of them are guaranteed to be provided by any driver, we'll 
>have to implement them all. =)  In particular, the first three (the 
>cursor functions) are not available via BWindowScreen.
>
>So the short answer is yes, we'll have to implement all the functions, 
>straight on the framebuffer, baby! ;)  If we end up using Zodius or some 
>other library, it should take care of most of the work for us; we just 
>have to hack it up to use driver-provided functions where available and 
>appropriate.
>
>e
OK. I'll get working on that kind of stuff this week. I've tried using Zodius 
for drawing lines and rectangles, and it is just *horribly* slow for this 
purpose. We'll probably be speeding it up and using it for the BView API. 
However, I have some code left over from BePhotoMagic (now public domain - 
heh) which we can adapt to render directly to the buffer. Mainly a Bresenham 
line function, but I've also got one for ellipses. This shouldn't take too 
long. :^)

--DW

Other related posts: