G
Greg N.
dorayme said:Where are all the photo links here?
Well I had foolishly expected you to go a bit further down into that
site. OK, Have a look at http://hothaus.de/greg-tour-2005/ro2.htm
dorayme said:Where are all the photo links here?
Greg N. said:Well I had foolishly expected you to go a bit further down into that
site. OK, Have a look at http://hothaus.de/greg-tour-2005/ro2.htm
Yes, call a different HTML page that displays the image and has the
button.
Yea, you might not want to use a pop up window for this.
I guess that there is no elegant way to code a link on a thumbnail to
display a pop up window with larger image and caption when activated.
Although no one said it couldn't be done, the consensus is that I should
stick to the tried and true no risk method, and create a separate html
page for each larger image, with the caption text.
Seems like a lot of wasted space to have a full screen window display a
4cm x 6cm large image with caption. Of course I could make the image
even larger now, if I didn't have to concern myself with the dial-up
download times of these images. (The images have been optimized to be 5
to 15 kb each).
In my mostly rural area, only about 30% have high-speed connections, and
my site is mainly for them. Download times do MATTER.
Thanks for all of your help.
gil said:I guess that there is no elegant way to code a link on a thumbnail to
display a pop up window with larger image and caption when activated.
I think that was what I essentially told him, complete with a basic roadGreg said:You seem to be mainly concerned with an "elegant way to code", but that
was not what most answers were referring to. People were trying to tell
you that pop ups are not a pleasant or "elegant" thing to deal with from
a user perspective.
And yes, there is no elegant (read: simple) way to code what you want,
other than creating an individual HTML file for each image or doing some
server side programming.
At approximately 2006/01/16 08:04, Travis Newbury typed these characters:
I guess that there is no elegant way to code a link on a thumbnail to
display a pop up window with larger image and caption when activated.
Although no one said it couldn't be done,
stick to the tried and true no risk method,
page for each larger image, with the caption text.
Seems like a lot of wasted space to have a full screen window display a
4cm x 6cm large image with caption.
even larger now, if I didn't have to concern myself with the dial-up
download times of these images. (The images have been optimized to be 5
to 15 kb each).
In my mostly rural area, only about 30% have high-speed connections, and
my site is mainly for them. Download times do MATTER.
Thanks for all of your help.
Gil
Gérard Talbot said:Nowhere
in your post did you indicate a preference for reusing and recycling a
single secondary window for your photo album purposes/goals.
-The [web]pagemaker.You can have as many popups open at the same time as you want, but they
all have to have different names.
... and who controls the names of the popup windows?
So, the original statement is false. I (the user) cannot have as many
popups open as I want. I can only have as many open as the page
designer will permit me to have.
However, I (the web page designer) can foist pages on the hapless user,
or can prevent him from being able to do what he wants (which is, for
example, to see four different hotel rooms at the same time) if I don't
want him to do that easily.
That turns the computer upside down.
For this reason, I would say that the goal of dictating how windows are
to be opened, used, and closed, is flawed. Let the user decide. Cue
the user as to how to do it, if necessary. And do provide at least a
"next/previous picture" button in the blowup.
But don't take over the
user's options.
I guess that there is no elegant way to code a link on a thumbnail to
display a pop up window with larger image and caption when activated.
Although no one said it couldn't be done, the consensus is that I should
stick to the tried and true no risk method, and create a separate html
page for each larger image, with the caption text.
Seems like a lot of wasted space to have a full screen window display a
4cm x 6cm large image with caption. Of course I could make the image
even larger now, if I didn't have to concern myself with the dial-up
download times of these images. (The images have been optimized to be 5
to 15 kb each).
In my mostly rural area, only about 30% have high-speed connections, and
my site is mainly for them. Download times do MATTER.
Why? What's wrong with the back button?
gil wrote :
Gil, read again your original post. You'll see that 9 lines out of 13
were about a close button. You got an answer on that, regarding that, etc..
Later, you explained more what you were looking to do. You failed to
give more details on the overall picture of what you wanted to do. You
put too much emphasis on that close button.
For your information, more and more browser manufacturers are
restricting more and more powers of script to play, to "toy with" the
window object. If a script shouldn't open automatically a window, then
why should it be able to close a window or bring it back on top, just
like that?
Mozilla 1.x, Firefox 1.x and Nestscape 7.x all allow users to neutralize
windowRef.close() calls :
dom.allow_scripts_to_close_windows
Also, nowhere your idea was to reuse such secondary window, to recycle
such secondary window into a customized resized window. In your own
words, the script you had in mind was to create 99 secondary window
which would have to be closed automatically if you had a 100 picture
photo album: that's abusing user system resources in many ways. Nowhere
in your post did you indicate a preference for reusing and recycling a
single secondary window for your photo album purposes/goals.
I say it can be done and I say I have done so *_many many months ago_*.
Create a sub-window and dynamically DOM-insert an image
http://www.gtalbot.org/DHTMLSection/DynamicInsertionDOMImageInPopup.html
(although that demo may not be exactly what you need or want)
Opening enlarged images of different dimensions into a single new
separate window only one at a time
http://www.gtalbot.org/DHTMLSection/EnlargeThumbnail.html
the consensus is that I should
For a photo album, a slideshow (like S5) is an acceptable solution as
long as you cater for accessibility guidelines.
and create a separate html
You did not fully explain what exactly you were looking for to begin
with: you did not at first give the overall picture of what you were
trying to do. You initially/originally focused on that close button and
then later brought up that blur, lost of focus trick to automatically
close the window. That trick is definitely not recommendable because
it's inflexible and it's not a logical response to what the user does. A
window response should be normally adequate (or proportional if you
want), appropriate to what the user's initial behavior, original action
was. The users always associate a browser window response to his own
behavior, action: losing/switching focus has nothing to do with closing
a window.
When you work on a document in a word/text application, switching to
another application should not provoke the closing of your word/text
application. That's true to any window/windowing environment and media
application. David Massy and more and more MS-Windows/MSIE engineers
agree and understand all this.
Closing a window should be in direct response to an user action
deliberately, specifically and explicitly in that sense.
Well, then a slideshow is a better alternative.
Of course I could make the image
Well that's good. Image quality, reducing number of colors without
reducing image quality and using .png (better compression) is the first
thing to do with all and every images put on a site.
"PNG also compresses better than GIF in almost every case (5% to 25% in
typical cases)."
GIF or PNG
http://www.w3.org/QA/Tips/png-gif
More and more countries are setting standards and guidelines for
reducing the size of webpages too, you know. On January 1st 2006, New
Zealand government has made an accessibility law mandatory to comply
with; one guideline/standard is to make webpage even accessible for
connections of 14.4Kb modem and 9.6Kb modem, exactly because there too
in rural areas there are people with slow connections.
Gérard
gil wrote :
Gil, read again your original post. You'll see that 9 lines out of 13
were about a close button. You got an answer on that, regarding that, etc..
Later, you explained more what you were looking to do. You failed to
give more details on the overall picture of what you wanted to do. You
put too much emphasis on that close button.
For your information, more and more browser manufacturers are
restricting more and more powers of script to play, to "toy with" the
window object. If a script shouldn't open automatically a window, then
why should it be able to close a window or bring it back on top, just
like that?
Mozilla 1.x, Firefox 1.x and Nestscape 7.x all allow users to neutralize
windowRef.close() calls :
dom.allow_scripts_to_close_windows
Also, nowhere your idea was to reuse such secondary window, to recycle
such secondary window into a customized resized window. In your own
words, the script you had in mind was to create 99 secondary window
which would have to be closed automatically if you had a 100 picture
photo album: that's abusing user system resources in many ways. Nowhere
in your post did you indicate a preference for reusing and recycling a
single secondary window for your photo album purposes/goals.
I say it can be done and I say I have done so *_many many months ago_*.
Create a sub-window and dynamically DOM-insert an image
http://www.gtalbot.org/DHTMLSection/DynamicInsertionDOMImageInPopup.html
(although that demo may not be exactly what you need or want)
Opening enlarged images of different dimensions into a single new
separate window only one at a time
http://www.gtalbot.org/DHTMLSection/EnlargeThumbnail.html
the consensus is that I should
For a photo album, a slideshow (like S5) is an acceptable solution as
long as you cater for accessibility guidelines.
and create a separate html
You did not fully explain what exactly you were looking for to begin
with: you did not at first give the overall picture of what you were
trying to do. You initially/originally focused on that close button and
then later brought up that blur, lost of focus trick to automatically
close the window. That trick is definitely not recommendable because
it's inflexible and it's not a logical response to what the user does. A
window response should be normally adequate (or proportional if you
want), appropriate to what the user's initial behavior, original action
was. The users always associate a browser window response to his own
behavior, action: losing/switching focus has nothing to do with closing
a window.
When you work on a document in a word/text application, switching to
another application should not provoke the closing of your word/text
application. That's true to any window/windowing environment and media
application. David Massy and more and more MS-Windows/MSIE engineers
agree and understand all this.
Closing a window should be in direct response to an user action
deliberately, specifically and explicitly in that sense.
Well, then a slideshow is a better alternative.
Of course I could make the image
Well that's good. Image quality, reducing number of colors without
reducing image quality and using .png (better compression) is the first
thing to do with all and every images put on a site.
"PNG also compresses better than GIF in almost every case (5% to 25% in
typical cases)."
GIF or PNG
http://www.w3.org/QA/Tips/png-gif
More and more countries are setting standards and guidelines for
reducing the size of webpages too, you know. On January 1st 2006, New
Zealand government has made an accessibility law mandatory to comply
with; one guideline/standard is to make webpage even accessible for
connections of 14.4Kb modem and 9.6Kb modem, exactly because there too
in rural areas there are people with slow connections.
Gérard
Jose said:... nor do tabs
allow me to see four pages at the same time, side by side, for comparison.
The back button does not take one to the previous picture (in the
sequence), it takes one to the previous page viewed, which is likely the
photo index page. To have to keep going back (and loading, and
scrolling) to go to the next picture is a pain.
At approximately 2006/01/17 19:35, Gérard Talbot typed these characters:
Your ".../enlargethumbnail" is very close to what I wanted to do.
Presently, on my site, If the user clicked on another thumb, or anywhere
else in the main window, the pop up disappeared but did not close.
Instead it joined a growing number of relatives behind the main window.
and after a while there were quite a few open windows hidden there, if
I am not mistaken they consume resources.
With your method, a separate close button is not necessary to remind the
user to close the window as only one pop up window is open at any time.
Opening a 'second' window actually closes the first.
I can easily add the caption to the image with photo editing software
such as IrfanView.
Sorry I was not as clear as I could have been, I am still only a novice
and not familiar with the full range of options available within HTML, etc.
Is the javascript code free to use?
Gil
Not all users have browser with tabs. And tabs don't solve the problem
introduced by web pages that close themselves unbidden, nor do tabs
allow me to see four pages at the same time, side by side, for comparison.
The back button does not take one to the previous picture (in the
sequence), it takes one to the previous page viewed, which is likely the
photo index page. To have to keep going back (and loading, and
scrolling) to go to the next picture is a pain.
that and more.
A page with thumbs is a back-and-forth operation. If you return from a
pic, the _forward_ button is required to go "back" to it, but, of
course, this is valid for a single level only. If you "sequence" your
images as you suggest, you can indeed have the behavior _you_ want, but
who else wants it? I, for one, don't want to have to go back thru all
the pics I just viewed simply to return to the prior page.
5- If the url is different but the image size are the same, then the
window should not close and be re-created; it should load the new image
in the current window. The script currently does not do that: I just
realized this today.
Good question (I do not get this question asked enough/often). Yes, it's
free. Just mention my webpage and my name as contribution and author at
the beginning of the script.
It sounds to me like you're wanting javascript. Javascript can do all
that and more.
No, I'm not wanting javascript. I'm wanting ordinary HTML links that do
ordinary things, and let ME (the user) do what I want with those things.
A page with thumbs is a back-and-forth operation. If you return from a
pic, the _forward_ button is required to go "back" to it, but, of
course, this is valid for a single level only. If you "sequence" your
images as you suggest, you can indeed have the behavior _you_ want, but
who else wants it? I, for one, don't want to have to go back thru all
the pics I just viewed simply to return to the prior page.
On the thumbs page, I should be able to click on a pic and go to a pic
page. From there, BACK will take me back to the thumbs page, but there
is no browser function that will take me to the next pic. That's where
a button on the pic page [next-->] comes in handy. [<--prev] is equally
useful, and [^back to thumbs^], while redundant with the browser back
button, nicely completes the set.
Jose
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.