Ticket #608 (Open)Sat Jul 22 14:05:02 UTC 2023
Include JPEGMsgs and JPEGRender in the PlingSystem archives
| Reported by: | Cameron Cawley (3514) | Severity: | Enhancement |
| Part: | RISC OS: Module | Release: | |
| Milestone: | Status | Open |
Details by Cameron Cawley (3514):
The !Run file for Browse attempts to load the JPEGMsgs and JPEGRender modules if SpriteExtend 0.99 or later isn’t loaded, which apparently provide “JPEG support for OS versions without this in SpriteExtend”. It would be nice to have these as part of the HardDisc4 or PlingSystem archives if it’s still possible to build these.
Changelog:
Modified by Sprow (202) Sun, August 06 2023 - 07:26:47 GMT
- Summary changed from Include JPEGMsgs and JPEGRender in the HardDisc4 or PlingSystem archives to Include JPEGMsgs and JPEGRender in the PlingSystem archives
- Severity changed from Normal to Enhancement
A nosey in the binary suggests it’s probably a derivative of SprExtend (the messages file also has high similarity), but nothing in the history of SprExtend as far back as CVS goes (RISC OS 3.60) suggests how it was produced. The main stumbling block will be that the JPEG workspace and transcoding buffers are held in dynamic areas which don’t exist on 3.10.
The JPEGMsgs module could be absorbed as all it does is register the file with ResourceFS. I think it’s from a time before resgen existed as several disc based components had a matching Msgs module.
Mildly noteworthy is that the RMEnsures in Browse’s !Run file are unnecessary. Browse uses ImageLib for JPEG rendering (ie. it’s not calling the JPEG_ SWIs itself) and the init function within ImageLib does the RMEnsures too.
Short answer: no, it’s not still possible to build these.
