[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Saturday 21 September 2002 16:11, Eric Botcazou wrote:
[snip]
> I don't see it as a problem. The plugin/script mecanism is powerful
> enough to support new object types (although the script mecanism is
> broken for Mingw32 for the time being).
I just don't like it that you have to recompile the tools, that's all.
It's very annoying when you have your own modifications to the library,
because every time you reinstall Allegro (which is quite often, if you
like to work on the CVS version) you have to remember to put all your
modifications back in.
> I think that's not enough: we shouldn't create a discrepancy between
> what dat2c/s supports and what load_datafile() supports. In other
> words, every datafile that can be attached to an executable by
> dat2c/s should be loadable via load_datafile() too. It is not the
> case currently for custom fonts.
[snip]
> I think we should try to go further: we should try to plugin-ize
> dat2s/c.
I think we have a minor misunderstanding here; I want to simply drop a
text file into some directory and have dat2c be able to export my font
structure. That way I can distribute such a text file with my library
and it requires no source code changes to Allegro.
Plugins are more powerful but on the other hand require a recompile.
Suggestions welcome, code will probably follow them :-)
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)
iD8DBQE9jJKnUdhclgSmRuoRAsXvAJ4x34mzX7ccjsiYZgkwtDbbPOC6PgCfTQk4
vrs+19MRbeVEQG94ZellQhs=
=oPAT
-----END PGP SIGNATURE-----