PNG-TRANS analysis

[abl]

PNG-TRANS resources (as opposed to PNG resources) appear to be slightly different (at the very least, they have different magic) and should be analyzed - if nothing else, the assertion error raised by the different magic needs to be accommodated.

[abl]

Right off the bat, it appears each png-trans gets two entries in the resource table but only one entry in the manifest.

[southwolf]

I assume it might be PNG with TRANSparent layer?

[abl]

I PNG and PNG-TRANS describe the input (I imagine) more than anything else - the actual resource format is a simple monochrome bitmap.

PNG-TRANS resources have the image (just like PNG resources) and also have a second mask image - so you've got one bit of "color" and one bit of "alpha" - the current scripts can show these acceptably but the experience could be improved.

[southwolf]

Actually PNG-TRANS resources are, as I said, PNG with TRANSparent layer.
Here's PNG-TRANS in firmware 1.9.1
https://github.com/southwolf/pepple_pngtrans

[southwolf]

https://docs.google.com/spreadsheet/ccc?key=0An4xLEVum2FldFE3NWFsYVctclRPMnpZbzR0M0Z2LWc&usp=sharing

Resources in firmware