Re: [Plib-devel] Exposed bitmap loaders in SSG?
Brought to you by:
sjbaker
From: Jan R. <slo...@gm...> - 2007-01-06 19:53:34
|
Am Sat, 06 Jan 2007 09:03:55 -0600 schrieb steve <sjb...@ai...>: > If you want to take on this task, I think you should start a new > PLIB library component (plibImage with a 'pi' prefix or something) > - get it all up and working as a stand-alone thing (probably > copying/stealing code from SSG to do that). When it's all running > and reliable, we could just switch SSG over to using it. This would > mean zero changes to SSG until we are ready to do the switch. Steve, if I want to - read: if my limited spare time allows me to - take on this task or not depends on how much extra work is involved to do this. Let's think about a least-effort-approach to get "plibImage" started: - copy the raw image loader code to new "PI" files - define a unified API for the raw loaders, maybe using some kind of piImage object to store the raw image data and some additional information (width, height, pixel format) - write some central functions like piInit() and piLoadImage() (or piImageFactory() or whatever) - write piHaveLoaderFor() which, at the moment, does not try to dynamically load any additional libraries and only returns "true" for the PLIB-internal loaders Kind regards, Jan R. -- Jan Reucker email: jan dot reucker at web dot de web: http://www.reucker-online.de |