[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Saturday 21 September 2002 10:13, Eric Botcazou wrote:
[snip]
> The load_custom_font() function is by design font add-on territory.
I didn't know that function existed :-) Is it documented anywhere?
> Yes, a mecanism to handle sub-(object type) plugins is missing.
The real problem is that to support a new object type, you need to
recompile the grabber. This seems unavoidable, unfortunately.
> Nice mecanism. But how do you put your fonts in datafiles in the
> first place ? Does the font creator directly output datafiles ?
Good question; I hadn't really thought of that. Yes, probably the
creator can add the font to an already-existing datafile, or output a
new one. It will be able to "import" fonts from an existing datafile
already.
> I agree to make changes to the library datafile support and related
> tools. But the whole picture should be coherent: for example, if we
> enhance dat2s/c to support your object type, load_datafile() should
> support it too.
Great! But there is no change needed to the library; the only thing that
will be changed is to allow dat2c (and eventually dat2s?) to output any
sort of object based on a text file description. I'll start working on
it, since the changes won't mess anything up. One question, though:
where should the text description files go?
> Ok, but this is a custom engine working on a custom format so I don't
> see why it should be merged into the core library. AllegTTF also has
> a custom anti-aliasing engine and it works nicely though the Allegro
> textout() functions.
Fair enough. So does mine, by the way; it's just a new type of
FONT_VTABLE you can use. It uses the normal FONT structure and
everything.
Bye for now,
- --
Laurence Withers, lwithers@xxxxxxxxxx
(GnuPG 04A646EA) http://www.lwithers.demon.co.uk/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE9jF9rUdhclgSmRuoRAgLVAJ9+zpoG7zB7Krn+4wU2g8c2bFC23QCeOoDC
AR1qgJnvfGqNeVZsilJwPWQ=
=D1ef
-----END PGP SIGNATURE-----