[interfacekit] Re: Graphics

>>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.
>    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.

Agreed.

>    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.

Hey, send that sample code along or post it -- I'm very intrigued. =)  
The author doesn't seem to be actively maintaining it -- not that it's 
an indictment of the library, just sort of sad.  He seems to have done 
some really cool work with it.

e

Data is not information, and information is not knowledge: knowledge is 
not understanding, and understanding is not wisdom.
        - Philip Adams

Other related posts: