I have just uploaded a new version of the gf9k library (version 0.004)

members.chello.nl/m.delorme/

New in this version:
- Font routines works okay now on turbo r
- Added multiple font support. Upto ~64KB data can be used for fonts. This makes it
possible to load about 16 fonts of 8*16 pixels or 32 fonts of 8*8 pixels.

I've just started on the cursor routines for the bitmap modes.. The v9990 has two hardware cursors, but they are both 1 bit. To make a good cursor you need them both. So I decided to make the set xy to controll them both at once. But what about the pattern data. Make a new file format for it, integrate it in G9B or no file support for it at all? any ideas?

Yesterday I successfully included bitbuster into the G9B format and these filles can be loaded into the GFX9000 with the same routines as for non compressed files. I hope to put the new version online soon.

Heyah MSD, any status updates on this project?

AFAIK, there's already a new version and some fixes in the tools, but he's prolly too lazy to release it

yes there a lot of updates. I already started on making a release version, but it's time to write a manual. :-(. Could just release it without a manual.

If you want to encourage people to develop for GFX9000, you should make a manual.

Well it does contain some documentation, every function has a summair description in the source file and it contains 2 example programms.

I think a before-documentation-release would be highly appreciated

I've just made a small update of te gfx9000 lib. I made a wrapper for the functions that enables you to create a jump table. An export file is generated with all the labels needed. These also are names without points in it. Since a lot of assembler out their can't handle for example G9k.SetScreen. The exported file can contain the direct addresses of the g9klib functies or the addresses of the jump table. In this way g9klib can be used more easily with other assemblers and c-compilers.

There isn't realy a manual needed, the code is very straight forward.

Very easy to understand.

Maybe adding some extra info in the source itself is sufficient. I've made some small updates so expect a new update soon

Currently I started on some work on the library again. Some small bugfixes and I've added font data support from ram. So even characters can be printed when there is no free vram. No I've to add a putchar or equivilent function. I can do it in two ways. Make a putchar and use the putchar for the
print string function or make two seperate functions. The first one has a favor for size and the second one for speed (well not much overhead but still). Any toughts on this matter?

speed

Sonic_aka_T: The overhead is one extra call and ret per character,however this will save about 50 bytes . Maybe I will go for sererate routines. They can use the same data structures, so only a little size overhead .