recoil2png is awesome when combined with scripting, to process sets with large number of images.
It would be nice to have a --info parameter on recoil2png, to obtain information from the native file, in a format that can be easily parsed by scripts.
The default field separator would be <newline>, but could be changed with a --fs parameter</newline>
For example:
$ recoil2png --info ARMY.SCR
File:ARMY.SCR
Format:ZX-Spectrum screen
Platform:ZX-Spectrum
Native resolution:256x192
Colors:16
Used colors:6
PAR:1
$ recoil2png --info FUWA.PIC
File:FUWA.PIC
Format:X68000 picture file
Platform:X68000
Native resolution:512x512
Available Colors:32768
Used colors:153
PAR:1.33
$ recoil2png --info *.S* --fs,
File:DATA-7.SR7,Format:Graph Saurus screen-7,Platform: MSX2, Native resolution:512x212, Available Colors:16, Used colors:15, PAR:0.69
File:USAGIRL0.SCC,Format:MSX BLOAD screen-12,Platform:MSX2+,Native resolution:256x212, Available Colors:19268,Used colors:2237,PAR: 1.38
$ recoil2png --info FUWA.PIC
File:FUWA.PIC
Format:X68000 picture file
Platform:X68000
Native resolution:512x512
Available Colors:32768
Used colors:153
PAR:1.33
I would like to add that the video-mode of the platform is also an important info to be shown. I.e.:
1) on MSX
Video-mode: screen7i
2) On Amiga:
Video-mode: HAM6
3) On C64
Video-mode: multicolor
RECOIL can be used from many programming languages. Even in C it doesn't feel verbose: https://sourceforge.net/p/recoil/code/ci/master/tree/win32/by-platform.c
I don't feel that outputting all the metadata as non-standard plain text is justified.
Just to chime in and say something like this would be great (JSON output format perhaps).
However I realize it's a lot of new info to output, so I'd even love just a simple
--verbose
flag that would output which format it ended up converting as.