Parsing/extracting non-script resources

[luxaritas]

Continued from ProjectorRays/ProjectorRays#3 since it's more relevant here

It would be great to get all the non-script assets pulled from namely cct and dcr files. In the previous issue mentioned, you said you'd look into image and sound files - any idea how much of a stretch it would be to get everything else? I have a director trial atm, and I'm seeing the following:

There's also all the controls, but not sure how you'd go about handling exporting something like that (as with sprites/frames/etc)

[Brian151]

@lfp6
@PaulusParssinen

ProjectorRays is supposed to be our decompiler (or was) , and was started pretty much with the intention of getting at scripts.

Why the focus became so bytecode/script-oriented, I'm not sure...
It is possible I had something to do with that, because I have a certain set of priorities

The Earthquake project, or as it started, "OpenShockwave" is primarily focused on decompilation and format documentation. However, we've become busy with life or there have been interest shifts.

To be perfectly honest, we are operating fairly independent of each other. That's why we have a few versions of a parsing library, a decompiler, a graphics viewer, etc... It's not the best for productivity or collaboration. There also have been some disagreements about things like XTRAs, especially those adding entire file formats

I can say that W3D will probably be fairly difficult

I was working on a reader for fonts... They're just not fun to parse
I somewhat doubt my abilities both to display and to convert them, I've never tried font rendering, but I understand it has some caveats
I could read/export them, at least

I actually have resumed work on the web/JS build of Earthquake, including re-make it yet AGAIN... Trying to be more methodical and careful about HOW I do things this time. And, I am currently implementing DCR/CCT. But, this will take some time, and I'm having to fill information gaps. I think I definitely can get Earthquake to disassembling Lingo (or at least, facilitating that), but no idea when. Compiled JavaScript is not something we've yet found how to deal with, but looks like you have @PaulusParssinen

As for format support We started with DIR/DXR,CST/CXT because they're the easiest to handle. Shockwave/Afterburner does some not nice things, and I can say those varints caused me some major byte-alignment issues trying to read the chunks correctly

I've currently gotten as far as to decompress the ILS
Now I have to read it.