![]() | |
![]() |
| | Thread Tools | Display Modes |
#11
| |||
| |||
|
|
URI : http://www.fotch.org.uk/css/fotch.css Line: 11 Context : body |
#12
| |||
| |||
|
|
Please clear up validation issues before posting: URI : http://www.fotch.org.uk/css/fotch.css Line: 11 Context : body I'll bet you didn't know this NG is monitored by the Validation Police.. |
#13
| |||
| |||
|
|
BruceB wrote: Please clear up validation issues before posting: URI : http://www.fotch.org.uk/css/fotch.css Line: 11 Context : body I'll bet you didn't know this NG is monitored by the Validation Police.. ...got our own gulag, bubba. Now, where DID I put that battery lead? |
#14
| |||
| |||
|
|
People with a browser of less than 750px wide will have to scroll, but who does? I can only imagine purists who insist on having the browser in one eighth of their screen. |
#15
| |||
| |||
|
|
Ben Measures wrote: Paul Dean wrote: No need for sarcasm. If you look at the image on the front page, it's a portrait of 30+ people; if I resize it so a 640x480 screen won't need a scrollbar it would be ridiculous. Why don't you make it a reasonably-sized thumbnail linking to a larger version? An idea like that isn't exactly new, and for good reason. Well, I think that would be appropriate if the photo was something the user is likely to want to see in detail. |
|
Its purpose however is to help the overall first impression - the happy team - without looking as if their attention is being unduly pointed to the team. |
#16
| |||
| |||
|
|
Paul Dean wrote: Its purpose however is to help the overall first impression - the happy team - without looking as if their attention is being unduly pointed to the team. Now we see the conflict of interest. You suggest detail is unimportant, and then go on to say that you want to see the individual facial expressions of a crowd of almost 40. |
|
Clearly you're looking for some detail from this large photograph, and the best way to provide this inline is to use a smaller image linked to a larger one. |
#17
| |||
| |||
|
|
Ben Measures wrote: Now we see the conflict of interest. You suggest detail is unimportant, and then go on to say that you want to see the individual facial expressions of a crowd of almost 40. I didn't say that. |
|
it looks silly to have an image where people's faces are the size of a pinhead. Users don't need to see detail, but they do need to get a certain impression. |
#18
| |||
| |||
|
|
Paul Dean wrote: Ben Measures wrote: Now we see the conflict of interest. You suggest detail is unimportant, and then go on to say that you want to see the individual facial expressions of a crowd of almost 40. I didn't say that. You may not realise it but you've been saying it all along, even now: |
|
it looks silly to have an image where people's faces are the size of a pinhead. Users don't need to see detail, but they do need to get a certain impression. Clearly you're looking for some detail from this large photograph, and the best way to provide this inline is to use a smaller image linked to a larger one. |
#19
| |||
| |||
|
|
No need for sarcasm. If you look at the image on the front page, it's a portrait of 30+ people; if I resize it so a 640x480 screen won't need a scrollbar it would be ridiculous. |
|
I can't really see the problem with that image - my browser takes up half my screen and the table is entirely in the browser. People with a browser of less than 750px wide will have to scroll, but who does? |
#20
| |||
| |||
|
|
Imagine if the image was so blurred (in an artistic way) that no detail was discernable, and yet to have an overall desired design effect it had to be within a range of particular sizes, then you'll see what I mean by the size being important. It's /not/ to see detail, it's for the overall effect of the page - to stop people thinking, "that looks silly" and/or "why do they think I'd want to see a blown up picture of their faces?" |
![]() |
| Thread Tools | |
| Display Modes | |
| |