[interfacekit] Re: Graphics

>Yeah, I had been thinking of proposing libart, but I didn't see anything
>for doing fills and the like, which would mean a goodly chunk of coding
>for us.  Zodius is looking like a more complete solution that way (gotta
>love those gradients!), though I don't know if it's as robust/mature as
>libart.  No doubt we'll have to spend some time with the possible libs
>to see what's really going to work for us.
>
>We should definitely try to use pre-existing stuff whereever possible
>and feasible.  The more we can do that, obviously the faster we can make
>stuff happen.
>
>e
    I wasn't going to mention my preference when I posted the RFC about these 
libs, but I also like Zodius best of the three. I've done some playing with 
it today. It appears to be quite extensible and is done much in the style of 
the rest of the BeOS API. Unlike libart, I think the fact that it's not as 
mature is a good thing - we can really modify it to suit our needs and 
attempt to speed it up, as well. It also integrates easily into existing 
code.
    The nice part is that it's designed to render to a frame buffer. I hacked  
around on my little test app and made it draw something resembling a window, 
and it didn't take much effort. I did it mostly to see how easily it could be 
done. I think that we as a team should seriously look at using it. There are 
some really cool-looking things that we could do with it.

--DW

Other related posts: