What’s the best way to handle pages that vary in height? In other words, is there a way to have the page height adjust with the content?
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Any CSS button on constructed page will always show all content.
An inline construction will ensure that each element ‘pushes’ the one below to grow the height of the page without overlap.
And disabling the height box of a div will allow the box to grow to accomodate content added dynamically.
David
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
What’s an inline construction?
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
What’s an inline construction?
It’s a technique whereby divs are inserted into other divs so the entire page can flex vertically as a whole unit without worries of content overlapping other content. It can also be made to expand horizontally as well as vertically to fill the browser window. There are numerous threads on FWTalk about it and much more online. Time to hit the books.
Todd
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
So you’re referring to nested HTML items? Wouldn’t tables work just as well and be a little cleaner?
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
So you’re referring to nested HTML items? Wouldn’t tables work just as well and be a little cleaner?
Yes, tables function in a similar way but it’s most definitely not cleaner in terms of code (think bloated). Tables are ideal for tabular data but are not good for page layout. Nor are they good semantically or for search engines or accessibility.
If you want to become a skilled designer then you really do need to learn how to build an inline layout. It is the de facto standard for constructing pages.
Todd
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Thanks for your help Todd. I just tried integrating Perch served data using an inline layout and I simply couldn’t get the items positioned properly. I instinctively went to tables and everything is fine now.
I also referenced the FWP manual and in it they suggest the Relative Page Action, which I need to read up on as well. Where is the best place to lean about inline layouts?
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Thanks for your help Todd. I just tried integrating Perch served data using an inline layout and I simply couldn’t get the items positioned properly. I instinctively went to tables and everything is fine now.
I also referenced the FWP manual and in it they suggest the Relative Page Action, which I need to read up on as well. Where is the best place to lean about inline layouts?
There’s definitely a learning curve, it’s not quite as simple as putting a box within a box. The RPL action can help with this but it’s important to understand what’s happening and not rely entirely on the action to think for you because the action creates an inline layout the FW way, not the way it’s typically constructed.
Search FWTalk for threads relating to inline construction. Also, Google’s your friend. I’m sure others around here have specific tutorials they can point you towards.
Todd
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Thanks Todd. Unfortunately, as a Freeway Pro user, I find that some of the information is a little harder to grasp. Kind of like retrofitting a Freeway Pro page with Perch. You not only need to understand the code, but how it integrates into Freeway Pro. I’m getting there though. 
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Thanks Todd. Unfortunately, as a Freeway Pro user, I find that some of the information is a little harder to grasp. Kind of like retrofitting a Freeway Pro page with Perch. You not only need to understand the code, but how it integrates into Freeway Pro. I’m getting there though.
It does take time but it’s certainly possible to grasp so keep chipping away at it. None of us was born knowing all this stuff. Except perhaps Walter. This is all stuff we all have to deal with as designers. FW can only “protect” you so much, often times you need to poke your head out of the FW Bubble and get hands-on with your work. It really does make you a better more knowledgeable designer.
Todd
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
I think the whole point about being a ’ Pro ’ user is to have some idea
what is happening. Web design is as much or more about the mechanics of
things as it is ‘how it looks’.
I believe it is an absolute myth that getting friendly with a bit of
HTML/CSS causes people’s brains to catch fire and explode… it just feels
that way at first. Later on, you realize that its just the neurons firing
up.
–
Ernie Simpson
On Sat, Jun 9, 2012 at 5:50 PM, RavenManiac email@hidden wrote:
Thanks Todd. Unfortunately, as a Freeway Pro user, I find that some of the
information is a little harder to grasp. Kind of like retrofitting a
Freeway Pro page with Perch. You not only need to understand the code, but
how it integrates into Freeway Pro. I’m getting there though.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options