AW: [AD] Paletted Bitmap Grabber PlugIn & Allegro Extension

[ Thread Index | Date Index | More lists.liballeg.org/allegro-developers Archives ]


Ok, I see your point. I tried to implement it as grabber-plugin-only without
altering allegro.h. I put the PAL_BITMAP struct into the OBS code and
everything is fine. BUT: The grabber now knows how to grab and save this
file. But when I load an already stored DATAFILE which contains such an
object, the grabber doesn't know how to handle this and treats it as binary!
I also could simply import my paletted bitmaps as BIN objets and read them
in the game, but then I can't view them in the grabber. In order to let the
grabber load it correctly, I need to either modify allegro in the core
sources, or I need a way to register some proper loading routines to the dat
utility, which is not possible, if I haven't missed anything. Any solutions?
What advantages brings the plugin-system to me, when I am not able to write
proper plugins without altering Allegro in it's base?

Jörg

------------------------------
joerg@xxxxxxxxxx
home: http://www.sharky-x.de
music: http://mp3.sharky-x.de
-----------------(SHX '00)----

*> -----Ursprüngliche Nachricht-----
*> Von: conductors-owner@xxxxxxxxxx
*> [mailto:conductors-owner@xxxxxxxxxx Auftrag von Peter Wang
*> Gesendet: Dienstag, 29. August 2000 07:49
*> An: conductors@xxxxxxxxxx
*> Betreff: Re: [AD] Paletted Bitmap Grabber PlugIn & Allegro Extension
*>
*>
*> Jörg Rüppel <sharky-x@xxxxxxxxxx> wrote:
*> >
*> > Please tell me what you think and please apply this patch since I
*> > don't have CVS access.
*>
*> I don't know about everyone else, but I think this is too specific
*> to be part of the standard API.  I have a feeling this would work
*> just as well purely as a grabber plugin.
*>
*> Your concern is that images take up too much space on disk.  But
*> once a image is loaded into memory, it doesn't require its own
*> palette, correct?  If so, `PAL_BITMAP' is not needed.
*>
*> If absolutely necessary, it'd be preferable to extend the plugin
*> system to be more flexible rather than putting in a one-off feature
*> like this.  For example, we could allow linking the datafile
*> utilities with external libraries so you could keep such code
*> separate.  Bonus: addons like loadpng which require external
*> libraries could build with grabber plugins much more easily.
*>
*> --
*> tjaden@xxxxxxxxxx - http://www.psynet.net/tjaden/
*> You can't judge software by its default configuration.
*>



Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/