#67 No, the effort is not abandoned. But I wanted to review a plan of implementation with fresh eyes.
Originally, I envisioned having an uncompressed specification that the user could select from. I also want to eventually add JPEG 2000 & HT-J2K. Following this pattern, the user would have to know which specification to select in order to test their file.
It would be nice is the Compliance Warden determine compliance without this spec parameter. Could this be done by parsing the ftyp box and then running the appropriate specs?
I still haven't studied the code very much yet, but these are some of my initial thoughts. Just thinking out loud.
#67 No, the effort is not abandoned. But I wanted to review a plan of implementation with fresh eyes.
Originally, I envisioned having an uncompressed specification that the user could select from. I also want to eventually add JPEG 2000 & HT-J2K. Following this pattern, the user would have to know which specification to select in order to test their file.
It would be nice is the Compliance Warden determine compliance without this spec parameter. Could this be done by parsing the ftyp box and then running the appropriate specs?
I still haven't studied the code very much yet, but these are some of my initial thoughts. Just thinking out loud.