Hello, Robert is my name.
I am a junior designer and I am learning as I go, as most people do.
I have used only tables because they seem to render not so differently cross-browser like the div's do.
I have the example below, which shows of the kind of layout I am working with. I tried to make a div based layout like that one, but with little success. I am a total beginner with Divs and the way they are positioned, so please, if you take on this quest, give me some guidelines.
I would also be pleased to be guided into making this layout tableless, I am not trying to make anyone do my work. I am just overwhelmed of the way the divs are positioned.
So here goes, this is what I want to achieve using Doctype and ONLY Divs:
*, BODY, HTML { margin:0;padding:0;border:0 }
table {border:1px solid black;}
Footer Text
I am grateful to you already, for you have read so far
Thanks,
Robert.
http://www.google.co.uk/searc
http://www.google.co.uk/search?q=divs+do+not+replace+tables
but I'll have a look at your code
On second thoughts, your
On second thoughts, your page looks very pretty, but has zero content.
What exactly do you envisage using this type of layout for?
What could be the point in
What could be the point in including content? I want to stick to positioning, I don't want to clutter the page, I just want to point out easier what I am trying to achieve.
This is just a sketch of a page
Nemuro wrote:What could be
What could be the point in including content? I want to stick to positioning, I don't want to clutter the page, I just want to point out easier what I am trying to achieve.
This is just a sketch of a page
Without knowing what the page is going to contain it's impossible to lay it out properly.
All we'd do is replicate the entire page using hundreds of divs, which is not the point of CSS.
If you have content, eg a navigation bar, a page title, a footer, etc, and you want it to look like your example, we can do that.
Just imagine it has   ;
Just imagine it has   ; all over it.
Nemuro wrote:Just imagine it
Just imagine it has   ; all over it.
Thank you for playing. We have some consolation prizes backstage on your way out.
I was talking about the
I was talking about the positioning of the containers, why won't anyone understand?
More to the point, why don't
More to the point, why don't you understand? Don't you suppose we know pretty much what we're talking about?
The way things work is that you have content that is well structured and marked up with semantic (meaningful) html tags. The content may be dummy text, eg. lorem ipsum, and dummy images of appropriate size.
Only after you have content with valid markup is the css written to create the layout.
Remember, done correctly, the css is layered on top of the html, so you must have something to begin with. This is not some PhotoShop or GoLive slice and dice exercise.
cheers,
gary
Nemuro wrote:I was talking
I was talking about the positioning of the containers, why won't anyone understand?
if all you want is a page full of coloured boxes then use tables.
If you actually have a point to the design (eg each box will contain something) then we'll help you do it properly in CSS.
It's like asking us how to build a house out of trifle. Unless you have a reason for it there's no point.
In best Homer Simpson
In best Homer Simpson voice.
'Mmmmm house made of trifle.'
solution here
This demo hangs together with divs and no tables. inline styles (shudder) but he's not paying me so ....
The class=table / row / cell are there to help someone used to tables to see how to convert over to DIV
It'll get a newbie off the ground quick and thats what the gentleman ordered. Some of the other posts were somewhat less than gracious; please accept my apologies for my fellow team members; they have lofty ideals.
*, BODY, HTML { margin:0;padding:0;border:0 }
.row, .table {clear:left;} /* class that starts another row */
.cell {float:left;} /* line them up one after another */
jinoturistica wrote:Some of
Some of the other posts were somewhat less than gracious; please accept my apologies for my fellow team members; they have lofty ideals.
Please don't apologise for us Most of us are at the stage that rather than waste our time giving somebody code, we ask why they want to do something, what they're trying to achieve, then we educate them on the best way to do it.
inoturistica I would rather
inoturistica I would rather that you didn't applogise on behalf of other 'fellow' team members, maybe wait a while until you've built up a few posts for that
'Getting a newbie off the ground quickly' is seldom the best approach and most of us have spent a while trying to instill good practices based on our collective experience with standards based CSS/HTML coding.
As for 'Lofty Ideals' if that is what you think of our approach to coding and web development then I'm afraid your wrong, these are not 'Lofty Ideals' they are the necessary standards that we appreciate and follow and which the forum is based around.
I would like to thank you
I would like to thank you all for your help,but mostly jinoturistica, the code he/she supplied helped me alot.
Sorry for those who have been disturbed by me.
horses for courses
You have a job and keep busy. I am retired with all the time in the world. You know a lot about CSS, I do not and take every opportunity to accept a new learning challenge. I don't have a manager to give me impossible tasks so I subscribe to forums and see what I can get involved with.
OTOH, I've been programming for 40 years so perhaps I don't know how CSS would do something but back in the days of Rexx and PL/1, I might have seen something similar.
As for asking people what they are trying to do then trying to educate them, WOW! thats a pair of serious challenges. Even 40 years of programming for big corporations doesn't prepare me for those 2.
I'll eat some humble pie now. Does Birds custard still exist?
Quote:I would like to thank
I would like to thank you all for your help,but mostly jinoturistica, the code he/she supplied helped me alot.
S'pose it's more than the folks who answered your post at Sitepoint got anywho.
Robert - as someone myself
Robert - as someone myself starting out w/ css (not that recently, but still learning because I'm juggling lots) - reading this post kinda made me think: Have you read posts where everyone here, especially those much more experienced, helped ALOT of people out and in a way where you actually get to learn the language and the integration with X/HTML AND help w/ the problem at hand? I read the above post at Sitepoint as well. Lotsa help around. Just have to read and do the common sense things here that I learned here: doctype/layouts/semantics. There's ALOT here - and ALOT of good practices and advice.
Should thank the people at sitepoint BTW.
Just my take at the whole thread. :shrug: