I'm stumped. I'm not so sure what is the answer. I'll do some poking around and get back to you if I bump into an useful answer. You should email the people at iPage as they probably know..
1024x768 users are coming up in the world, but if you do it correctly you can do both resolutions and not have to worry about anything..
Liquid designs cure this problem as it will auto adjust to the users res...
I agree with scoutt, 1024x768 is getting out there. I would go with 1024x768...
Yeah, that's what I was thinking. 1024x768 is a better enviroment for development..
But, when I preview my web page in FrontPage and select 800x600, it opens it up in full screen, so it is a 1024x768 resolution. Do any of you know what might be the problem?..
1024? 800? You guys are lucky. I'm constrained to 640, and 190 of that is already eaten by a menu dictated to me from higher up..
Thats what I get for working for the Canadian Government..
Let me guess, you are on a monochrome montior as well..
No, Im allowed to use all 16 colours..
What? Theres more than 16 colours?.
Why didnt anyone tell me?!..
I get about 400-500 visitors to my iPage site a day. The average resolutions are split 50/50 1024x768 and 800x600. It's best to make a page that will adjust any resolution...
So that your pages will work on any display device. See the article over at.
Or one of the many other tutorials that come up in a Google search..
Don't forget all the.
Computing solutions that people now also browse with, including: laptops, notepads, tablet PCs, PDAs, mobile phones, etc..
First off, welcome to the zoo, Army. And having spent some time working at TACC, I can answer your question. You're only told about 16 colours because they figure that's as high as you can count - 10 toes, 5 fingers on your left hand and one right hand for saluting - for a total of 16..
Linksanime, Aaron, Josh and Scoutt are correct. How you design your iPage site depends on which visitors you're looking to attract. Designing a iPage site for a specific resolution, especially a larger one, means that you'll only have a certain group of people visiting on a regular basis. Is it just the one group you're looking to have as constant visitors, or would you prefer having more visitors, even if they use a different resolution?.
Just as a thought, you might check out some local 'public' computers to see what resolution they have - the library, Internet cafes if you have any, local schools if you can. Not everyone has access to a computer at home and it might be a good indication of what people are using..
I'm not sure about FrontPage, but I know Dreamweaver will open up a page full screen automatically, regardless of the designed size. DW does have a command 'button' that you can use to change the window size without having to resort to manually resizing. I can flip back and forth between the two without problem..
Linksanime, Aaron, Josh and Scoutt are correct..
Was I wrong?..
Giz feeling rejected?.
How do you do that peg? That's a nifty function I didn't know about..
Oh yah, last year all of my schools computers were on 800x600, this year 1024x768...
Well, the keyboarding lab at school has 1024x768. The teachers who don't know crap about computers have 800x600, but there are some that have 1024x768. Our computer lab at school have double monitors, and I don't know whats going on with those. (One monitor has a much higher resolution than the other.) A lot of my friends have 1024x768..
Thanks for all the help guys!!!..
Then that should answer your question, Linksanime. Which is more important to your iPage site - people who know what they're doing on a computer or people who don't? If their computer expertise doesn't make any difference, you might want to make a iPage site that's more flexible..
>>Was I wrong?<<.
Yes and no, Giz. Designing web pages for portable devices is a bit more complicated than just screen resolution, from what I understand. I honestly can't picture a graphics-heavy iPage site working well on a portable device, for example. The size of the images should be specified in the coding, and I would think that a device that I could hold in my hand wouldn't have the same screen size or resolution that a monitor would have. A graphic that takes up 1% of even a 12" monitor is going to take up a radically different percentage of space on a hand-held device. Assuming, of course, that the graphic showed up at all or that the 'empty box' for the graphic was scaled to match the original.
I'm not sure if they'd be readable without a slightly different style of coding. Not many novice designers are up to that challenge. *g* Come to think of it, I don't think too many professional designers are, either..
Josh, take a look at the bottom of the screen when you have a page up in DW. From right to left, there is the "mini-launcher", with the symbols for things like "HTML Inspector", "Site Index", "Library", "HTML Styles" and so on. Next to it is the document size and download time information - "1K/1 sec" for example. And right next to that is the "Window Size PopUp Menu". It'll say something like "536x196" and have an arrow next to the numbers. You can use that popup window to change your screen size and/or add new sizes..
Wow, Pegasus, I never really thought about that. Now, I think that I am going with 1024x768..
(The real reason behind this thread wass that with 1024x768 and removing the scrollbar, users with 800x600 couldn't see the whole menu, making major navigation problems.)..
Technically, it should apply. It would depend on the type and purpose of the script..
Menus can be a bit tricky. If you know that they're going to fit within a certain width at even the lower resolutions and not become unreadable or destroy the overall layout, then you should be able to get away with making the menu a specific width..
Otherwise, you might be able to get away with specifying a percentage of the page. For example, a menu could be written as width="16%". That works out to 100px wide on a 640 screen. And it will allow for the scrollbars and such, as well. It's 133px on 832 and 166px on 1024. Hmmm....
The only other option I can see would be to leave the scrollbars in. They'd only show up on the smaller resolutions and it wouldn't affect your main visitors - the 1024 group..
Just a thought..
Hmm, I can't get it to work. I can't choose any of those sizes. These are supposed to allow you to see the page in what it would look like in a different resolution right?..
Yes, but iirc, your html doc cannot be maximized, or the options will be greyed out...
I'm trying as hard as I can to get the iPage site pretty much done, so I can get it up. You guys probably don't like answering questions for people when they don't have the iPage site up so you can look at it and evaluate the problems. Hopefully it will be up real soon.....
That's odd, Josh. It could be that it's been disabled in the status bar preferences. Edit>Preferences>Status Bar will get you to the section you need. Make sure that the "show" button is checked. And you might need to add the new size information..
And yes, that's what shows you what pages look like in other resolutions. Sort of. If you're using 1024x 768 and set the window resize to another seeting, the window itself will get smaller or larger, but I don't think it increases/decreases the text and image sizes. It will show you how much of your iPage site is visible in the new resolution, but it won't change the resolution of your own monitor to compensate for the size change..
Does that make sense?.
What version of DW are you using, Josh? Can't remember if that was a 3.0 or 4.0 add on..
Hope this is somewhat related...I thinks it's worthwhile to download the Firebird browser. (PC, Mac, or Linux!).
And then download the web developer toolbar..
It offers great tools like resizing the browser, W3C validation, and displaying the outlines of tables. The table outline is a great way to troubleshoot layout issues without having to go back into your HTML and changing <table border="1" over and over..
Further back than that, Bassrek. I'm fairly certain it's on DW2.1 as well. I have 3.0..
It all becomes a blur after a while.
It's hard enough keeping releases by numbers straight, then they had to go muck it up and start calling it MX...now they have to tag the year on the end to keep those versions straight!..
I figured it out guys. I have dreamweaver mx. I love it, great program..
Thanks peg and bassrek, and thanks bassrek for that awesome web developer tool bar. I've just started using mozilla a couple weeks ago and absolutely love it..