Gå til innhold

Hardware.no: Hardware.no og dynamisk bredde og høy DPI


Anbefalte innlegg

Hei!

 

Hva med å gjøre at hardware.no websidene er litt dynamiske i bredden? Selv om man har en 24" 1920 skjerm så er det ikke sikkert at man vil browse i "fullskjerm." Men er ikke skjermene store nok nå for at de fleste hjemmesider ikke scroller sidelengs selv om vinduet ikke er maksimert? Ikke på min 15" 1280 bærbare.

 

hardware.no_opera_horizontal_scrolling.png

 

 

 

 

Opera har en "fit to width" funksjon men den virker dårlig på hardware.no:

 

hardware.no_opera_fit_to_width.png

 

 

 

Det er veldig irriterende, og skulle ikke væreså vanskelig å gjøre hovedkolonnen på hardware.no dynamisk. Det er også irriterende at denne "posting new topic" siden scroller vertikalt to steder :D

 

diskusjon.no_double_scroll.png

 

5.5. For what screen size should I write?

 

HTML does not depend on screen size. Normally, the text will be wrapped by the browser when the end of its display area is encountered. (Note that graphical browsers are often used with windows that are smaller than the full area of the screen.)

 

Preformatted lines (text within <PRE> elements) should only ever exceed 70 characters if the nature of the content makes it unavoidable. Longer lines will cause ugly line breaks on text-mode browsers, and will force horizontal scrolling on graphical browsers. Readers strongly dislike horizontal scrolling, except where they can realise that the nature of the content made it inevitable.

 

Images cannot be wrapped, so you have to be careful with them. It seems that 400 or 500 pixels is a reasonable width; anything above 600 will mean a certain percentage of users will have to scroll to see the rightmost bit. This percentage increases with your image width. Keep in mind that not everyone runs his browser at full screen!

 

(WebTV users have no ability to scroll horizontally, so anything beyond 544 pixels will be compressed by their browser. Some other devices may be even more limited.)

 

The use of tables for layout, especially when fixed-width cells are used, is the most usual single factor that prevents pages from adapting to various window widths.

 

http://www.htmlhelp.com/faq/html/design.html#screen-size

 

 

 

 

Neste stopp er DPI uavhengige hjemmesider :O (hva diskusjon.no gjør med vedlagte bilder er bra!

 

Consider a Web page that is designed for an 800×600 resolution. Let’s say we render this Web page such that the pixels specified in CSS (and in img tags and such on the page) map to one pixel on your screen.

 

On a screen with 1920×1200 resolution the Web site is going to be tiny, taking up < 50% of the screen's width and half the screen's height. In terms of absolute size, the text will be much smaller and harder to read.

 

Now this may not be a huge problem yet, but as displays cram more and more pixels into the same amount of space, if a Web browser (or any other application for that matter) naively continues to say that one pixel according to the app’s concept of pixels is the same as one pixel on the screen, then eventually you have text and images so small that they’re impossible to view easily.

 

http://webkit.org/blog/55/high-dpi-web-sites/

 

 

 

Kort og godt; ikke bruk fixed-width web design!

Endret av Gambler FEX online
Lenke til kommentar
Videoannonse
Annonse

Opprett en konto eller logg inn for å kommentere

Du må være et medlem for å kunne skrive en kommentar

Opprett konto

Det er enkelt å melde seg inn for å starte en ny konto!

Start en konto

Logg inn

Har du allerede en konto? Logg inn her.

Logg inn nå
×
×
  • Opprett ny...