Ionize wrote: > I am back once more having done some reading on html and CSS and I am > looking for more information on containers and exactly what they > are. Are they comparable to layers, and when positioning text or > images are they placed within that container or are they on their own > seperate layers/containers.
> I am sorry to one and all for asking the most basic of questions, but > you can all be assured that once i get the theory down I'll be here > with the most awkward questions imaginable heehee Your basic question is awkward enough for most :-) The reason is that pretty much everything in HTML/CSS (and so on) must be included in order to give a complete answer. The following is an attempt to strip it all back to a very basic starting-point, because no relations will make much sense later on if the starting-point is wrong. HTML: Start with elements, since containers are what we get when using elements to contain "something", and that "something" is usually content. Look at source-code/markup, since that's the only level where you can see elements as containers in their basic form. Their purpose are to add semantics to content-parts. There is only one layer on this basic level, and the only separation is the semantic one - separating the meaning of one content-part from all the others. That's all there is to HTML. <http://www.w3.org/TR/1999/xhtml-modularization-19990406/xhtml_modules.html> --- CSS: Next step is the visual enhancement, and this is where HTML elements acts as style-targets. HTML browsers have a set of hard-coded style-defaults, but we can change or add pretty much whatever as we like through styling. That's where CSS (and scripting in one form or another) comes in. <http://www.w3.org/TR/2003/WD-CSS21-20030915/visuren.html> This is where the fun begins :-) , as content and/or elements themselves are separated, positioned, stacked and layered by the mentioned defaults and through our styling. Visually we may pretty much turn everything backwards and forwards as we like, thus affecting layering of content vs. element in many ways. This is also where we affect the visual layout of elements so they becomes visual containers - or not. Study all available information about block vs. inline elements, as most of the basics behind CSS are found there. --- So much for a start. Try to imagine the above before asking any of "the most awkward questions", as they may easily become too awkward even for the most imaginative of us unless there are at least some mutual understanding on the most basic level. If you want to go even further down, and strip out all HTML/CSS disturbance until you need it, then you may start learning XML. I started at that level, and it sure paid off... regards Georg -- http://www.gunlaug.no ______________________________________________________________________ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
