> On Feb 8, 2022, at 7:34 PM, Mark Olesen <[email protected]
> <mailto:[email protected]>> wrote:
>
> are you familiar with it?
I had heard of it. But, wasn’t familiar.
> The file can be embedded straight into C
> code. Once the xpm file is created you can translate it into other
> data structures of a specific language. Therefore, there is no need to
> support a variety of image formats. XPM externally -> transform bitmap
> internally to whatever
>
> Just an idea, not sure if that is exactly what you are looking for?
After looking into that format, I don’t think it is quite what I’m looking for.
XMP3 (the current version) would be easy to export and I may add it. However, I
think it requires a little to much overhead on the users side. Everything is
just a blob of text in a single structure that would possible require string
processing to interpret data like image width, height, etc.
However, XPM is based on XBM. That looks more like what I’m thinking. For that,
I could just include additional defines and potentially the additional
structures for the palette and RLE versions. That allows for extremely lite
weight end user code.
Thanks for pointing me towards these.
_______________________________________________
Freedos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-devel
