Jump to content

Recommended Posts

That completely depends on what you are coding for.  If it's web facing then I would say that what is more important is that, regardless of how you do it, you need to be able to provide a site that will be fully functional regardless of display size.  This can either be done by a percentage sized container and adaptive child objects, or by having a series of fixed pixel views and an adaptive presentation based on viewport.  

 

it is becoming more common to use the latter option, creating a set of display templates at fixed width and presenting the content dynamically using the appropriate template based on a series of checks on viewport and browser.  This gives more control over content like images and menus so that the layout is tailored specifically for the size of screen it is being viewed on.

 

A similar process can be achieved using a percentage container and dynamically rendering the child elements using css values, this impacts page load time however, as the initial container has to be rendered first in order to get the values for the conditional rendering of the children.

This thread is more than a year old. Please don't revive it unless you have something important to add.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.