"Roy Tremblay" <
rmbla...@nlnet.nl> wrote
| Thanks Paul for finding out that FTP doesn't allow .thumbnails to be
| viewed, but, let's remember it's Windows File Explorer which is viewing
the
| the files, so, doesn't Windows File Explorer have the capability to
| understand its own thumbnail views?
|
It's not so much an FTP problem per se. Paul's
quoted snippet explained it pretty well. To generate
a thumbnail, something has to load the whole image
and create a resized version. It's very work-intensive.
And it can't be done without loading the original,
whether that's 50 KB or 20 MB.
The convenience is deceptive. What you're viewing
is simply a file list, perhaps rendered to look like a
Windows folder. Explorer doesn't "see" any of those
images.
If thumbnail generation is done by Windows Explorer
then Windows has to have the original images. As Paul
noted, it would be a bit silly to import the whole data
load in order to create thumbnails, in order to see if
you want to import any data. You might just as well
copy all the images over to begin with.
You have to remember that all of this is just data
transfer. Likewise with a webpage: We talk about
visiting a website, but really it's nothing like that.
The browser calls an IP address and says, "Please
give me your index.html." The server sends that. The
browser then parses it and calls again to get the files
that make up the webpage: "Please give me pic.gif,
pic2.gif and styles.css." The server sends those.
Eventually the browser has the whole thing and puts
it together, following the instructions in the HTML
and CSS, to show you a "homepage".
In theory you could have thumbnails in http, using
script to call the server. Server-side software could
then generate the thumbnails and write their links
to a webpage dynamically. But that's not a protocol
issue. The only difference is that you can run script, and
webpages are very flexible, while FTP is simpler. But
http does not "enable thumbnails" by design. Explorer is
not accessing the image files either way. And it's not
generating thumbnails in the http example. In the http
example it's just receiving a webpage full of thumbnails,
sent by the server.
There's often similar confusion when people access
ZIP files. Microsoft made it very convenient to see
the files as though they're in a folder. In their attempt
to make ZIPs easy to use they created massive confusion,
because the files are not in a folder, on disk. They're
still part of the ZIP, compressed.
It's *very* difficult to explain to people that the folder
they see is not really a folder. It's only a representation
of the embedded file list that's in a ZIP file. So people
open a file from a ZIP and try to email it or resave it,
then get confused when it doesn't work. Microsoft's
attempt to make the access transparent just made
things worse.
What you could possibly do would be to install
a thumbnail generator on Android and batch-convert
your images, maybe creating a folder in the same
location. Then you could copy over only the thumbnails
for viewing. (Explorer still won't be able to render them
on Android because that would still mean copying over
the files themselves first.) You might even find a program
that will act as a "super Exporer" and show you thumbnails,
but again, all the images have to be loaded in order to
achieve that, so they all have to be copied over, so why
not just copy them over in the first place?