> Before I can start setting up the API for libblt, I need an _exact_
> definition of what a BOB (= Blitting-Object) is.
A bob in the usual sense is an just something you can "blit" to the screen
in some accelerated way.
It is used for emulating sprites on hardware that does not have enough
or too limited hardware sprites. For example the players and enemies
in 2D-arcade games are usually BOBs.
Basically the idea is that you define a BOB and ask libblit to cache it for
you in some way so that it can be blitted as fast as possible later on
Basically Libblit should facilitate ways to define such objects and to put
the on screen, eventually using some ROPs or other manipulations to combine
it with the screen.
> Is it a kind of a Buffer? If yes, which one? Texture-Buffer,
> Raw-Buffer or whatever else?
It is up to the individual target how to implement it. It should just fall
back to allocating main memory and using the usual LibGGI drawing fuctions
if nothing better is found, but for example on fbcon it should try to
allocate offscreen memory and hardware-blit from there or for X it should
allocate Pixmaps and let the X Server blit.
While you are at it, Libblit should also contain visual->visual blits, to
avoid having "libblitbobs" and "libblitvis" ...
CU, Andy
--
= Andreas Beck | Email : <[EMAIL PROTECTED]> =
