Designing for Various Resolutions

  • Thread starter Thread starter Art
  • Start date Start date
Murray said:
...I will continue to assert that resolution is not a critical factor, or
even the one to consider at all, in this issue.
Click to expand...

Ok. Can you clarify this for me? Say a layout is for an intranet where each
user has a a maximized browser window and a 1600 x 1200 resolution, you
wouldn't want to consider the resolution at all. The resolution would not be
pertinent or helpful in any way. You would build this layout the same way
you would build a layout for a similar population all with 640 x 480
resolution. Is that right? :-)
 
That's not at all what I'm saying. I would use the resolution to determine
what the width of the maximized browser viewport is (assuming I wanted to
build the page to consume the entire width). Being smart, I know that a
maximized (IE) browser viewport at 1600 x 1280 is about 1577px, but I want
to give a bit of slack, so I make the width of the page to be 1450px. At
this point, resolution has nothing more to do with anything.

I only use it to determine the maximum width of the potential browser
viewport. Period.

From this point, I can see how the page would look on any other smaller
screen without fiddling with resolution, just by decreasing the viewport's
width.

But, you have to admit, the example you have cooked up is rarely the case.
Most people ask about public websites where neither the browser nor its
potential width.
 
That's not at all what I'm saying. I would use the resolution to
determine what the width of the maximized browser viewport is
Click to expand...

Right. So resolution has something to do with it.
I only use it to determine the maximum width of the potential browser
viewport. Period.
Click to expand...

Right, that's about it. But that's not "nothing".
From this point, I can see how the page would look on any other smaller
screen without fiddling with resolution, just by decreasing the viewport's
width.
Click to expand...

Of course. I've been doing that about 30 times a day for the past 7 years.
:-)
But, you have to admit, the example you have cooked up is rarely the
case. Most people ask about public websites where neither the browser nor
its potential width. [..is known.]
Click to expand...

True, but some statistics about monitor resolution of the target population
are usually known, and they provide some useful information. For instance: I
know that the majority of the target population for some of my sites use
1024 x 768. I'm not going to have lines of text which stretch across 100% of
the page width, because in my opinion that produces unreadably-long lines at
that resolution. Resolution has something to do with it. :-)
 
Resolution has nothing to do with it.

--
Murray
--------------
MVP FrontPage


P@tty Ayers said:
That's not at all what I'm saying. I would use the resolution to
determine what the width of the maximized browser viewport is
Click to expand...

Right. So resolution has something to do with it.
I only use it to determine the maximum width of the potential browser
viewport. Period.
Click to expand...

Right, that's about it. But that's not "nothing".
From this point, I can see how the page would look on any other smaller
screen without fiddling with resolution, just by decreasing the
viewport's width.
Click to expand...

Of course. I've been doing that about 30 times a day for the past 7 years.
:-)
But, you have to admit, the example you have cooked up is rarely the
case. Most people ask about public websites where neither the browser nor
its potential width. [..is known.]
Click to expand...

True, but some statistics about monitor resolution of the target
population are usually known, and they provide some useful information.
For instance: I know that the majority of the target population for some
of my sites use 1024 x 768. I'm not going to have lines of text which
stretch across 100% of the page width, because in my opinion that produces
unreadably-long lines at that resolution. Resolution has something to do
with it. :-)
Click to expand...
 
That's your story and you're sticking with it, I see. :-)


--
Patty Ayers | www.WebDevBiz.com
Free Articles on the Business of Web Development
Web Design Contract, Estimate Request Form, Estimate Worksheet
--



Murray said:
Resolution has nothing to do with it.

--
Murray
--------------
MVP FrontPage


P@tty Ayers said:
That's not at all what I'm saying. I would use the resolution to
determine what the width of the maximized browser viewport is
Click to expand...

Right. So resolution has something to do with it.
I only use it to determine the maximum width of the potential browser
viewport. Period.
Click to expand...

Right, that's about it. But that's not "nothing".
From this point, I can see how the page would look on any other smaller
screen without fiddling with resolution, just by decreasing the
viewport's width.
Click to expand...

Of course. I've been doing that about 30 times a day for the past 7
years. :-)
But, you have to admit, the example you have cooked up is rarely the
case. Most people ask about public websites where neither the browser
nor its potential width. [..is known.]
Click to expand...

True, but some statistics about monitor resolution of the target
population are usually known, and they provide some useful information.
For instance: I know that the majority of the target population for some
of my sites use 1024 x 768. I'm not going to have lines of text which
stretch across 100% of the page width, because in my opinion that
produces unreadably-long lines at that resolution. Resolution has
something to do with it. :-)
Click to expand...
Click to expand...
 
Yep.

--
Murray
--------------
MVP FrontPage


P@tty Ayers said:
That's your story and you're sticking with it, I see. :-)


--
Patty Ayers | www.WebDevBiz.com
Free Articles on the Business of Web Development
Web Design Contract, Estimate Request Form, Estimate Worksheet
--



Murray said:
Resolution has nothing to do with it.

--
Murray
--------------
MVP FrontPage


P@tty Ayers said:
That's not at all what I'm saying. I would use the resolution to
determine what the width of the maximized browser viewport is

Right. So resolution has something to do with it.

I only use it to determine the maximum width of the potential browser
viewport. Period.

Right, that's about it. But that's not "nothing".

From this point, I can see how the page would look on any other smaller
screen without fiddling with resolution, just by decreasing the
viewport's width.

Of course. I've been doing that about 30 times a day for the past 7
years. :-)

But, you have to admit, the example you have cooked up is rarely the
case. Most people ask about public websites where neither the browser
nor its potential width. [..is known.]

True, but some statistics about monitor resolution of the target
population are usually known, and they provide some useful information.
For instance: I know that the majority of the target population for some
of my sites use 1024 x 768. I'm not going to have lines of text which
stretch across 100% of the page width, because in my opinion that
produces unreadably-long lines at that resolution. Resolution has
something to do with it. :-)
Click to expand...
Click to expand...
Click to expand...
 
| I know that a maximized (IE) browser viewport at 1600 x 1280 is about
1577px,

Things just got bigger! 2560x1600 (max) Dell's new 30" Monitor

You can have 6 windows open at the same time all at 800x600 without any
overlapping (and still have a margin)... WOW

Mine is at 1152x864 but 95% of the time my browser is at 800x600 so I can
see around it. (other Apps opened)

bob

| That's not at all what I'm saying. I would use the resolution to
determine
| what the width of the maximized browser viewport is (assuming I wanted to
| build the page to consume the entire width). Being smart, I know that a
| maximized (IE) browser viewport at 1600 x 1280 is about 1577px, but I want
| to give a bit of slack, so I make the width of the page to be 1450px. At
| this point, resolution has nothing more to do with anything.
|
| I only use it to determine the maximum width of the potential browser
| viewport. Period.
|
| From this point, I can see how the page would look on any other smaller
| screen without fiddling with resolution, just by decreasing the viewport's
| width.
|
| But, you have to admit, the example you have cooked up is rarely the
case.
| Most people ask about public websites where neither the browser nor its
| potential width.
|
| --
| Murray
| --------------
| MVP FrontPage
|
|
| | > | >> ...I will continue to assert that resolution is not a critical factor,
or
| >> even the one to consider at all, in this issue.
| >
| > Ok. Can you clarify this for me? Say a layout is for an intranet where
| > each user has a a maximized browser window and a 1600 x 1200 resolution,
| > you wouldn't want to consider the resolution at all. The resolution
would
| > not be pertinent or helpful in any way. You would build this layout the
| > same way you would build a layout for a similar population all with 640
x
| > 480 resolution. Is that right? :-)
| >
| >
| > --
| > Patty Ayers | www.WebDevBiz.com
| > Free Articles on the Business of Web Development
| > Web Design Contract, Estimate Request Form, Estimate Worksheet
| > --
| >
| >
| >
|
|
 
Resolution does have something to do with it.


--
Patty Ayers | www.WebDevBiz.com
Free Articles on the Business of Web Development
Web Design Contract, Estimate Request Form, Estimate Worksheet
--



Murray said:
Yep.

--
Murray
--------------
MVP FrontPage


P@tty Ayers said:
That's your story and you're sticking with it, I see. :-)


--
Patty Ayers | www.WebDevBiz.com
Free Articles on the Business of Web Development
Web Design Contract, Estimate Request Form, Estimate Worksheet
--



Murray said:
Resolution has nothing to do with it.

--
Murray
--------------
MVP FrontPage




That's not at all what I'm saying. I would use the resolution to
determine what the width of the maximized browser viewport is

Right. So resolution has something to do with it.

I only use it to determine the maximum width of the potential browser
viewport. Period.

Right, that's about it. But that's not "nothing".

From this point, I can see how the page would look on any other
smaller screen without fiddling with resolution, just by decreasing
the viewport's width.

Of course. I've been doing that about 30 times a day for the past 7
years. :-)

But, you have to admit, the example you have cooked up is rarely the
case. Most people ask about public websites where neither the browser
nor its potential width. [..is known.]

True, but some statistics about monitor resolution of the target
population are usually known, and they provide some useful information.
For instance: I know that the majority of the target population for
some of my sites use 1024 x 768. I'm not going to have lines of text
which stretch across 100% of the page width, because in my opinion that
produces unreadably-long lines at that resolution. Resolution has
something to do with it. :-)
Click to expand...
Click to expand...
Click to expand...
 
Sure it does!
I have a computer on the desk behind me that is only 640x480 and that is all
it can do....
It also has no idea what a browser is... Haha hahaha

bob
| Resolution does have something to do with it.
|
|
| --
| Patty Ayers | www.WebDevBiz.com
| Free Articles on the Business of Web Development
| Web Design Contract, Estimate Request Form, Estimate Worksheet
| --
|
|
|
| | > Yep.
| >
| > --
| > Murray
| > --------------
| > MVP FrontPage
| >
| >
| > | >> That's your story and you're sticking with it, I see. :-)
| >>
| >>
| >> --
| >> Patty Ayers | www.WebDevBiz.com
| >> Free Articles on the Business of Web Development
| >> Web Design Contract, Estimate Request Form, Estimate Worksheet
| >> --
| >>
| >>
| >>
| >> | >>> Resolution has nothing to do with it.
| >>>
| >>> --
| >>> Murray
| >>> --------------
| >>> MVP FrontPage
| >>>
| >>>
| >>> | >>>>
| >>>> | >>>>
| >>>>> That's not at all what I'm saying. I would use the resolution to
| >>>>> determine what the width of the maximized browser viewport is
| >>>>
| >>>> Right. So resolution has something to do with it.
| >>>>
| >>>>> I only use it to determine the maximum width of the potential
browser
| >>>>> viewport. Period.
| >>>>
| >>>> Right, that's about it. But that's not "nothing".
| >>>>
| >>>>> From this point, I can see how the page would look on any other
| >>>>> smaller screen without fiddling with resolution, just by decreasing
| >>>>> the viewport's width.
| >>>>
| >>>> Of course. I've been doing that about 30 times a day for the past 7
| >>>> years. :-)
| >>>>
| >>>>> But, you have to admit, the example you have cooked up is rarely
the
| >>>>> case. Most people ask about public websites where neither the
browser
| >>>>> nor its potential width. [..is known.]
| >>>>
| >>>> True, but some statistics about monitor resolution of the target
| >>>> population are usually known, and they provide some useful
information.
| >>>> For instance: I know that the majority of the target population for
| >>>> some of my sites use 1024 x 768. I'm not going to have lines of text
| >>>> which stretch across 100% of the page width, because in my opinion
that
| >>>> produces unreadably-long lines at that resolution. Resolution has
| >>>> something to do with it. :-)
| >>>>
| >>>> --
| >>>> Patty Ayers | www.WebDevBiz.com
| >>>> Free Articles on the Business of Web Development
| >>>> Web Design Contract, Estimate Request Form, Estimate Worksheet
| >>>> --
| >>>>
| >>>>
| >>>
| >>>
| >>
| >>
| >
| >
|
|
 
Back
Top