I have incorporated a ‘twitter’ box (as a css html item) into a column on my website which displays my most recent tweets. The box expands as necessary, depending on the length of the tweets. However, it can impinge on the items below it.
Is there a way to make the position of one css item fixed relative to another rather than specifically pinning it to a place on the page, e.g. the item below my tweeter item set at 10px below said tweeter item?
Basically, you are talking about having nested html boxes inside of a parent. With careful planning (and experimentation to some degree) you can make the left column separate from the right and still have the contents expand. They must all be “in-line” boxes.
I’ll try and describe the layout in as little text as I can:
a) There will be one main html box.
b) Inside this main box will be two column boxes, one on the left and one on the right. The left one floats left, the right one floats right
c) Inside the left box will be your twitter box set to float left, and below it your second box that will float left and clear left. The twitter box can also have a margin on the bottom to keep a respectful distance from the box below it. Both boxes should have a fixed width, but not a fixed height so they can both grow.
d) The right box can be setup similar depending on how much you want in it.
Yes, essentially. In Freeway speak an In-line html box means that it has been “inserted” into another html box. The way to do that is to get a flashing cursor inside an html box as if you were going to start typing, then going to the Insert menu and selecting Html.
Remember the “box model” ramblings around here a while ago David, I think you had inquired about it at one time. Same thing as Chuckamuck is describing. It’s like wrapping Christmas presents, box in a box, in a box, in a box, in a box.
That wasn’t me Dan, but I’ll look it up. It was you that put me right about CSS and since then I’ve been using that with abandon, freed from the shackles of tables!
As a recent convert, I can only enthuse about the box model method. At first it seems counter-intuitive, if not a little arcane - “this is like tables and working out how to split them…”. Yes it is a bit, but far more flexible, and pages load at light speed in comparison. Once you get your head around it, you’re hooked. Big thanks to Dan J for getting me started!
