Maybe this is crazy talk, but it would be awfully nice for browsers to be able to resolve resource paths in archives like Java does in JAR files. For instance, I could create a presentation with something like S5 and zip up its directory structure into a single file -- 'mypresentation.zip'. That file would have all the HTML, CSS, JavaScript, images and whatever else I need to persuade someone that Triscuits are much better than Wheat Thins. (Or whatever.)
Then I could send 'mypresentation.zip' to my Wheat-Thin-eating buddy Clyde who can open his browser, choose, 'File | Open...' and pick my file. (Or right-click, choose 'Open with...' and pick the browser, whatever.) And he'd be able to see my presentation no matter how many graphics, CSS files, JavaScript files it referenced. And Clyde wouldn't even know or care about all that; he'd just have an overwhelming urge for baked, whole-wheat crackers.
So the browser would be responsible for:
AFAIK it already knows how to do the first and third, and the second is just a matter of using what 99% of people already use today. Some judicious use of temp directories (which they're already doing, right?) and you're set.
This doesn't seem very difficult and I'm sure I'm not the first to think of it. Is there something like this now? (Besides PDF or PowerPoint...)
Posted from cwinters.com; read original
Re:Mmm...
lachoy on 2005-04-20T04:01:19
1 down, 300 million to go...
Re:mhtml?
lachoy on 2005-04-20T04:00:24
As some people on my website noted, IE uses MHT files for this. And -- surprise! -- it's an RFC (2557) as well. From a quick glance it seems to be MIME + internal URL munging.
And apparently MAF (Mozilla Archive Format) allows Moz/Firefox to read this format as well.
Another surprise: there's no CPAN module for reading/writing such files...