We did define a BODY STYLE, as advised by our friends on the list to get global style definitions;
but this style does not want to apply itself for a few inline DIV-boxes, which instead got empty style - definitions such as:
with class=“f-x2” undefined: " .f-x2 { } "
What did I do wrong - any ideas please?
BW Omar KN
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Sometime around 22/12/08 (at 17:08 -0500) OmarKN said:
We did define a BODY STYLE, as advised by our friends on the list to
get global style definitions;
but this style does not want to apply itself for a few inline DIV-boxes
Tag-based styles such as “body”, “p”, and so on are not supposed to
be applied to anything. Instead, they are applied automatically by
the browser to whatever items lie within those tags.
It may be worth deleting the style you made and then making it from
scratch. (Partly because I can’t tell how you’ve done this, precisely
what it is called, and so on.)
Type “body” (without the quotes) into the Tag field in the Edit
Styles dialog, remove anything from the Name field, and add the style
settings that you want.
That’s it - don’t try to apply it to anything!
k
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Hi Keith,
…Instead, they (“body”, “p”) are applied automatically by >the browser to whatever items lie within those tags.
It’s works fine for the main content, but BODY-styles are not inherited to the right column, as I expected & wished for, and the right column is of course within the body-tag.
…deleting the style you made and then making it from >scratch.
did that ok, it took away another old style-item which was stuck there.
… how you’ve done this …
I pasted the font-def into the “extended” :
90%/1.7 Verdana, Arial, Lucida Grande, sans-serif;
this did the job, but back to my question,
Was it not the basic idea - to define the body-tag - that should (force to) inherit those styles to other parts of the page?!
BW; Omar K N
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
I’m thinking your nested div is the issue. It’s id (name) is probably different from the div it’s in. To target a style to it, create a style with the name of the div as the tag name and don’t put anything in the name field. Example: #div-inline
The number symbol is important. Once you have that just add style elements as needed and it will be applied to only the div named “div-inline” automatically.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Hi Chuck,
To target a style to it, create a style with the name of the div as the tag name and don’t put anything in the name field.
Yes, did that:
#right-col { color:#00c; font-size:small }
.f-x2 { }
and
If you look in your CSS code you’ll see that the .f-## styles actually have attributes and properties with them. They’re never just blank styles.
Perhaps a link to a test site to see what’s going on would help out if possible.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Well, here is the prototype:
http://mac.abc.se/home/onesr/frw/2/
You see the right-col: this font did not inherit from BODY,
(bec it’s a nested DIV?) so I created a new ID:
#right-col { color:#00c; font-size:small }
→ which however does not do what it is supposed to do anyway !??
Also - on a related issue -
I inserted line 2: (This article is edited …
and
FRW produces an unwarrented new style class (“style3”) :
(This article is edited
So you see FRW is still not under “my command” , it’s still a wild horse, and I’m not a professional Rodeo rider!
BW, Omar KN
(who wishes for more control over output)
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Wrong:
(This article is edited
correct:
(This article is edited
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
This FRW-talk interprets my span examples in its own way:
So now I try to write them with round ( ) brackets:
(p class=“style1”)(span class=“style3”) (This article is edited c
To repeat FRW creates a new class (“style3”) when I insert a new line into content, this was unwarrented.
How can this be avoided,
do I have to redefine styles for each box and line when already defined in BODY { … } ?
BW, Omar K N
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Well, you’ve got a mess of styles here. Some aren’t you’re fault and other’s need to be adjusted. First off, do you have to use % for your font-size? Perhaps you could set it to 12px or 14px for the general body size. It’s also easy enough to change the leading from 1.7 em to the PX equivalent. The browser age is not that dated and most browsers can read pixel measurements just fine.
For #nav2 ul item make sure you put in a right margin as well so in your extended palette you’d adjust it so it reads:
#nav2 ul { margin: 0 0 0.1px 0px; }
and the same with the li item it should read:
#nav2 ul li { padding: 5px 0; }
Now for the extra styles Freeway has a bad habit of creating new random styles starting with 1,2,3,4…etc and so on. To alleviate that problem you’ll have to double check which style is attached to what item. I’ll help with this part, style3 is attached to your article text in the middle. You could just drop that since your body tag could be changed to match that style of text. Style1 is attached oddly enough in a paragraph style that should have been adjusted by setting the default P tag in Freeway’s CSS palette to:
p { text-align: left; }
You could then make the color of the article text the default color in your body tag
body { color: #00009b; }
Style4 is attached to your footer on the bottom. That could be renamed as a class name of “footer” and left with just the white color and text align set to center.
So here’s the updated CSS look:
body { color: #00c; font: 12px/1.7em Verdana, Arial, "Lucida Grande", sans-serif; margin: 0; height: 100%; }
#nav2 ul { list-style-type: none; padding: 0; border-top: 2px solid grey; margin: 0 0 0.1px 0px; }
#nav2 ul li { padding: 5px 0; border-bottom: 2px solid grey }
#nav2 ul li a, #nav2 ul li a:visited { color: #f00; font-weight: bold; text-decoration: none }
#nav2 ul li a:hover, #nav2 ul li a:active { color: #0f0; font-weight: bold; text-decoration: none }
.footer { color:#fff; font-size:11px; text-align:center }
Remember also that if you want to style a specific DIV ID…say for instance “#right-col” to target the paragraph try writing the ID as:
#right-col p { }
That may help targeting those paragraph items more directly.
Hopefully that helped out, you just have mis-mashing styles but the good news is the changes are easy and you’re close to bringing it under control.
Good luck.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
but the good news is the changes are easy and
you’re close to bringing it under control.
Thank you, Dan; I can now see some light at the (web-design) horizon!
& you won’t believe how closely I’ll follow your advice!
i.e. 100% )
And thank God FRW is not only an item of technology!
BW & happy days !
Omar KN
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Good, besides a few spelling errors on my sleepy eyes that should be what you need to get things going.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options