It was a short while since Chris Wiles mentioned...
> How would it cope with the links and images?
>
> ie. if an image, within the HTML source is linked to www.example.com/gfx/
> how does Voyager save the source tree to the hard drive, and allow a user to
> view the web page (with images and anims), later?
I'm sure some clever bod can sort it out. Neil B? It was done for
the CU CD and AF CDs for the local sites. So what if Voyager (or
the download program) does have to go through all the links - it would
at least work in the end?
> It's very hard. IE5 goes through the entire source code and changes
> everything, then saves all the images, anims etc into a folder called
> 'index_files'.
Hmmm... confusing.
> This is a very messy method though and people have complained that they
> don't like the way that IE5 changes the source code to achieve this.
So why don;t they complain about they way applications are installed
for Windows? Files get splattered all over the place - nightmare.
Dinky do,
Mike C.
--
.--------------------------------- ---- - -- --------.
| AMiGA 1200EZT 060/PPC@240Mhz,50Mb RAM __/\__ |
| 3 HDD,DD&HD FD,4 CD-ROMS, \ o0 / bUDDa/S^D|
| SCSI+IDE,56kModem,BVGfX,19"VDU /_ v_\ |
`------------------------------- --- - \/ -- ------'
http://fly.to/BuddasWurld ICQ: 29173597
_____________________________________________________________
NetConnect mailing list. To unsubscribe, send an 'unsubcribe'
message to <[EMAIL PROTECTED]>
