| Re: [AD] Allegro generalization/extension mechanism |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: Re: [AD] Allegro generalization/extension mechanism
- From: guilt <karthikkumar@xxxxxxxxxx>
- Date: Tue, 15 Mar 2005 14:46:01 +0530
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=pSq4vu0bFyhKBODUaW6d6hbbXYJt7mVSuSbsB8+0gCriQC9+REX3e96E4BqKJPLik2WX5UyikHpfIxeHDAc3VFgoBdN8mZInn0ImA+1EN10U+bqjygDfr8od8R8YrlTU1910ZkzRXcy2dLSkA6ho8blpzfyrtsy/f28qXAxYUN4=
> I'm not sure what you're getting at... updating image loading code doesn't
> affect anything but the image loading code currently either.
Ok.. only to this point, I am replying. The rest is agreed.
Right, Evert. Here's an example:
Let's say that 4.3 wants a PNG routine. The idea is just like: we'll
just be adding a function called BITMAP *loadPNG() into BITMAP
*(loader_functions[]) and thorugh another function called
register_PNG_handler() so that load_bitmap() (in the core) is aware of
the new format as is.. :) because the handler extension hook is now
registered into the allegro's core system .. :) and tomorrow a
load_bitmap() can be called as-is for any other file type i want to
register..
--
Karthik
http://guilt.bafsoft.net