Resolution question

[Ifalldown]

My question revolves around visitor experience when handling the various amount of screen sizes these days. Is it better to design several sites to meet the demand, full screen flash or use coding. This is what I did.

screenWide = System.capabilities.screenResolutionX;
screenTall = System.capabilities.screenResolutionY;

if(screenWide==800 && screenTall==600) {
getURL("http://xxx/zzz.htm","_self");   



if(screenWide==1024 && screenTall==768) {
   getURL("http://xxx/zzz.htm","_self");
}

and so on. I thought this way would best maintain the integrity of the design while providing the visitor with a quality experience. Do any of you have some thoughts or experiences with the best way to handle this?

Thank you
 

[Jorge Solis]

Yours is probably the safest approach since it delivers a version for each resolution, but probably works multiply. Another choice is to use a liquid layout to match different sizes, that means use the Stage.onResize listener to allocate your stuff around the screen. If you design with this in mind probably you can achieve the same goals with less effort

Another thing: use Stage.widyh or height instead of screenResolutionY and screenResolutionX, since the browser can not be in full size (but usually does) Also don't check for exactly sizes but for ranges, since lately there are a lot of new devices with less standard screen sizes. My laptop right now has 1366 x 768

Jorge

[Ifalldown]

Hey Jorge,

Got ya on the stage. width but I'm not sure on the AS with the screen ranges. Would I do a math.randomRange min:600?. The liquid layouts are nice but I ran into some communication issues with the MC's. You probably wouldn't have a problem but I fall down alot with AS. I have an AS dictionary full of script that don't work.   

Thanks

[Jorge Solis]

The real dimension of your movie could be checked against this 2 properties:

Stage.width
Stage.height

So based on this, redirect to the one that match close

Jorge