This is Interesting: Free Magazines for Graphics designers and webmasters  


Home > Archive > Dreamweaver > January 2005 > Understanding CSS





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Understanding CSS
UltraTch

2005-01-30, 4:14 am

first of all, would this be the correct place to post discussions on CSS? if
not, any suggestions for a forum offering CSS help? ok my CSS question is: why
is it necessary to add 2 menu DIV commands (menu and menu2) in order for both
seperate DIVs (index and archives) to be properly nested within the 'menu'?
Thanks Tekture

<div id="menu">
<div id="menu2">
<div id="index">
<div id="menuHeader">Index:</div>
<ul>
<li>option
<li>option
<li>option
<li>option
</ul>
</div>
</div>
<div id="archives">
<div id="menuHeader">Archives:</div>
<ul>
<li>option
<li>option
<li>option
<li>option
</ul>
</div>

</div>

David Stiller

2005-01-30, 4:14 am

UltraTch,

> first of all, would this be the correct place to post
> discussions on CSS?


Ehh, who knows? It's a Dreamweaver forum, but plenty of people ask HTML
questions. 6 of one, half a dozen of the other.

> why is it necessary to add 2 menu DIV commands
> (menu and menu2) in order for both seperate DIVs
> (index and archives) to be properly nested within the
> 'menu'?


It probably isn't necessary to use two DIVs. (These would be tags, by
the way, not commands.) It all depends on the structure of your CSS
document. If the CSS is *expecting* to see two nested DIVs with ids of menu
and menu2, then two more with ids of index and menuHeader, then of course
they would have to be there in the HTML. This is a question of design.

If the CSS was only expecting to see a DIV with an id of nav, then the
HTML might be ...

<div id="nav">
<ul>
<li>option</li>

.... and so on.

Does that help? Your question is a bit like asking, "Why is it
necessary to use three nested tables to make this image center itself on the
page?" -- and the answer can only be, "Well, it might not be necessary. It
depends on a number of factors, etc., etc."

A good basic starter for CSS is available at w3schools.com


David
stiller (at) quip (dot) net
"Luck is the residue of good design."


David B

2005-01-30, 4:14 am

UltraTch wrote:
> first of all, would this be the correct place to post discussions on CSS? if
> not, any suggestions for a forum offering CSS help? ok my CSS question is: why
> is it necessary to add 2 menu DIV commands (menu and menu2) in order for both
> seperate DIVs (index and archives) to be properly nested within the 'menu'?
> Thanks Tekture
>
> <div id="menu">
> <div id="menu2">
> <div id="index">
> <div id="menuHeader">Index:</div>
> <ul>
> <li>option
> <li>option
> <li>option
> <li>option
> </ul>
> </div>
> </div>
> <div id="archives">
> <div id="menuHeader">Archives:</div>
> <ul>
> <li>option
> <li>option
> <li>option
> <li>option
> </ul>
> </div>
>
> </div>
>


I'm sure someone here can answer that, but there's a CSS forum at
www.projectseven.com. You could probably find other CSS forums through
Google as well.
Jeff North

2005-01-30, 7:14 am

On Sun, 30 Jan 2005 03:37:55 +0000 (UTC), in macromedia.dreamweaver
"UltraTch" <webforumsuser@macromedia.com> wrote:

>| first of all, would this be the correct place to post discussions on CSS?


try:
comp.infosystems.www.authoring.stylesheets or (ciwas)

>| if not, any suggestions for a forum offering CSS help? ok my CSS question is: why
>| is it necessary to add 2 menu DIV commands (menu and menu2) in order for both
>| seperate DIVs (index and archives) to be properly nested within the 'menu'?
>| Thanks Tekture
>|
>| <div id="menu">
>| <div id="menu2">
>| <div id="index">
>| <div id="menuHeader">Index:</div>
>| <ul>
>| <li>option
>| <li>option
>| <li>option
>| <li>option
>| </ul>
>| </div>
>| </div>
>| <div id="archives">
>| <div id="menuHeader">Archives:</div>
>| <ul>
>| <li>option
>| <li>option
>| <li>option
>| <li>option
>| </ul>
>| </div>
>| </div>


Difficult to tell without seeing the CSS code.
---------------------------------------------------------------
jnorthau@yourpantsyahoo.com.au : Remove your pants to reply
---------------------------------------------------------------
Murray *TMM*

2005-01-30, 12:19 pm

http://www.projectseven.com/tutoria...acfly/index.htm


--
Murray --- ICQ 71997575
Team Macromedia Volunteer for Dreamweaver
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com - Template Triage!
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs, Tutorials & Resources
http://www.macromedia.com/support/search/ - Macromedia (MM) Technotes
==================

"David Stiller" <stiller@quip.net> wrote in message
news:cthlki$onl$1@forums.macromedia.com...
> UltraTch,
>
>
> Ehh, who knows? It's a Dreamweaver forum, but plenty of people ask
> HTML questions. 6 of one, half a dozen of the other.
>
>
> It probably isn't necessary to use two DIVs. (These would be tags, by
> the way, not commands.) It all depends on the structure of your CSS
> document. If the CSS is *expecting* to see two nested DIVs with ids of
> menu and menu2, then two more with ids of index and menuHeader, then of
> course they would have to be there in the HTML. This is a question of
> design.
>
> If the CSS was only expecting to see a DIV with an id of nav, then the
> HTML might be ...
>
> <div id="nav">
> <ul>
> <li>option</li>
>
> ... and so on.
>
> Does that help? Your question is a bit like asking, "Why is it
> necessary to use three nested tables to make this image center itself on
> the page?" -- and the answer can only be, "Well, it might not be
> necessary. It depends on a number of factors, etc., etc."
>
> A good basic starter for CSS is available at w3schools.com
>
>
> David
> stiller (at) quip (dot) net
> "Luck is the residue of good design."
>



Sponsored Links


Copyright 2003 - 2008 forum4designers.com  Software forum  Computer Hardware reviews