>> Well, naming each time rgba32 in all calls was
>> annoying, hope
>> that is fixed now :)
> Still, it remains. I got rid of a lot files, though.
> Well, the reason of these kinds of names is to refer
> to the physical pixel format in memory. LibArt, for
> instance works only with RGB and RGBA. AGG has RGB555,
> RGB565, RGB, BGR, RGBA, ARGB, BGRA, ABGR. You have to
> admit it's not good to convert the whole buffer from
> RGB to BGR on Windows. Moreover, the infrastructure
> doesn't prevent you from adding new color spaces, say,
> HSV, CMYK and so on. On the other hand using true
> polymorphism is not preferable because of lots of
> virtual calls, and sometimes simply not possible, for
> example, for different color spaces. Afterall, there's
> a keyword "typedef" :-) See examples/pixel_formats.h
Well, I'll have a look at how the new API works out...
>> Oh, and please fix
>> the homepage, I am even ready to help you with that
> Yeah. Shame on me. I'm thinking about TeX to write the
> docs and generate HTML.
Right. The idea to use doxygen for automatic docs for the API was
a good idea, but for that to work there has to be documentation
in the headers in the first place ;-)
I have a hard time from looking at webcvs view at the filter code how
it works, but I hope after running the examples and experimenting with
them I have a better feel of them...
BTW I like how the marker code turned out! Very readable. Also many
calculate() functions are very clear, as I said only trouble is finding
out how they get called ;)