Ideally, it would just be:

file:///some/path/to/some.zip/membername

But then you'd need to think about much more extensive reworking of how
Squeak handles directories and files.  In the above, you'd need the URI
object to access the objects in the path sequentially.  For example, it
first asks "some" to get member "path"; then it asks "path" to get
member "to"; then it asks "to" to get member "some.zip"; then it asks
"some.zip" to get member "membername".  Actually, you'd probably want to
pass the entire remaining portion of the path at each step...details.

It would certainly be nice...

- Stephen

> -----Original Message-----
> From: squeak-dev-admin at lists.squeakfoundation.org 
> [mailto:squeak-dev-admin at lists.squeakfoundation.org] On 
> Behalf Of Ned Konz
> Sent: Thursday, December 05, 2002 1:22 PM
> To: squeak-dev at lists.squeakfoundation.org
> Subject: Re: Another SAR/DVS feature request
> 
> 
> On Thursday 05 December 2002 10:03 am, Stephen Pair wrote:
> > Just like we now have ZipArchive and TarArchive, we could
> > add a DirectoryArchive or similar.  Then SARInstaller could 
> > automatically work with a zip, tar, or directory archive.
> 
> Though TarArchive remains to be written...
> 
> I've thought about referring to zips via URLs like some file managers 
> do, like file:// URLs with member names tacked on:
> 
> zip:///some/path/to/some.zip/membername
> 
> but it's hard to tell what the file name is, if you can't actually go 
> through directories and members. For instance, how would you ask a 
> user to insert a floppy containing:
> 
> zip:///some/path/to/some.zip/another.zip/name2/name3
> 
> Now is this:
> zip name: /some/path/to/some.zip/another.zip  member name: name2/name3
> or:
> zip name: /some/path/to/some.zip member name: 
> another.zip/name2/name3 or even: zip name: 
> /some/path/to/some.zip/another.zip/name2 member name: name3
> 
> -- 
> Ned Konz
> http://bike-nomad.com
> GPG key ID: BEEA7EFE
> 
> 
>