>I understand now. Thanks! Now the next question on the list: what
drawing
>functions do we have access to? Are we going to have to write our own
>replacements for the hook functions? We obviously need something to
draw
>with. :)
Well, the possible hooks that the driver can provide are:
define_cursor
move_cursor
show_cursor
dwar_lin_with_8_bit_depth
draw_line_with_32_bit_depth
draw_rect_with_8_bit_depth
draw_rect_with_32_bit_depth
blit
draw_array_with_8_bit_depth (indexed_color_line)
draw_array_with_32_bit_depth (rgb_color_line)
sync
invert_rect
draw_line_with_16_bit_depth
draw_rect_with_16_bit_depth
Any that aren't available for a given driver, we'll have to implement.
Since none of them are guaranteed to be provided by any driver, we'll
have to implement them all. =) In particular, the first three (the
cursor functions) are not available via BWindowScreen.
So the short answer is yes, we'll have to implement all the functions,
straight on the framebuffer, baby! ;) If we end up using Zodius or some
other library, it should take care of most of the work for us; we just
have to hack it up to use driver-provided functions where available and
appropriate.
e
Data is not information, and information is not knowledge: knowledge is
not understanding, and understanding is not wisdom.
- Philip Adams