What is your screen resolution?
- Thread starter Fatbat
- Start date
- Status
i design everything for 1024. all my sites are set at 960px width. that leaves about 10 or so pixels on the sides after subtracting the scroll bar width.
i would suggest following the standard instead of making an assumption. maybe those web professionals you're targeting are using dual monitors with one set at a lower resolution. no guarantee your site is going to be loaded on the high res one...
i would suggest following the standard instead of making an assumption. maybe those web professionals you're targeting are using dual monitors with one set at a lower resolution. no guarantee your site is going to be loaded on the high res one...
Haven't missed any responses, reading everything and taking it all in. When I said 960px I meant width not height. A bit surprising the number of peeps in 768 and 800 height. That would drive me nuts. I've got the site working in 800 nicely, 768 is a bit tight but everything can be seen, so I think that should be good.
Here's a great site for everyone doing layout and design, browsersize.com will set your browser window to specific sizes to see how your designs look on smaller monitors.
Thanks to everyone for your input thus far, much appreciated!
This will tell you what res your user has. Write it to a db or text file. I found my site that I checked by far most people were on 1024x768.
<?
if(isset($HTTP_COOKIE_VARS["users_resolution"]))
$screen_resolution = $HTTP_COOKIE_VARS["users_resolution"];
else //means cookie is not found set it using Javascript
{
?>
<script language="javascript">
<!--
writeCookie();
function writeCookie()
{
var today = new Date();
var the_date = new Date("December 31, 2010");
var the_cookie_date = the_date.toGMTString();
var the_cookie = "users_resolution="+ screen.width +"x"+ screen.height;
var the_cookie = the_cookie + ";expires=" + the_cookie_date;
document.cookie=the_cookie
}
//-->
</script>
<?
}
?>
You could use something like this to write to a text file. This wouldn't prevent the many duplicates you would get and a db would be better.
$REMOTE_ADDR = getenv('REMOTE_ADDR');
$date = date('m-d-Y, H:i',mktime());
$fp = fopen ("screenres.txt","a");
$screen_size = $REMOTE_ADDR."\t".$date."\t".$screen_resolution."\n";
fwrite ($fp, $screen_size);
fclose ($fp);
<?
if(isset($HTTP_COOKIE_VARS["users_resolution"]))
$screen_resolution = $HTTP_COOKIE_VARS["users_resolution"];
else //means cookie is not found set it using Javascript
{
?>
<script language="javascript">
<!--
writeCookie();
function writeCookie()
{
var today = new Date();
var the_date = new Date("December 31, 2010");
var the_cookie_date = the_date.toGMTString();
var the_cookie = "users_resolution="+ screen.width +"x"+ screen.height;
var the_cookie = the_cookie + ";expires=" + the_cookie_date;
document.cookie=the_cookie
}
//-->
</script>
<?
}
?>
You could use something like this to write to a text file. This wouldn't prevent the many duplicates you would get and a db would be better.
$REMOTE_ADDR = getenv('REMOTE_ADDR');
$date = date('m-d-Y, H:i',mktime());
$fp = fopen ("screenres.txt","a");
$screen_size = $REMOTE_ADDR."\t".$date."\t".$screen_resolution."\n";
fwrite ($fp, $screen_size);
fclose ($fp);
- Status