[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

DarkWyrm wrote:
> 
> Well, I've been toying around with a lot of stuff, lately, and I wanted to
> toss something out to see what you guys thought. As we all know, the BView
> API utilizes a number of functions which do some pretty complicated stuff
> IMHO, like Beziers, etc. I'm no idiot, but the stuff they do is out of my
> league and quite involved, as well. I've looked at some vector libraries, as
> a result, and I was wondering if using such a beast is worthwhile for our
> purposes.
>     It'd be nice to have some vector-based stuff in the graphics API. There
> are three which I consider possibilites: Vector++, libart, and Zodius.
> Thoughts anyone? Is this worth looking into? Would it be anywhere near fast
> enough?
> 
> -DW

Other related posts: