It sure could. Try modifying the selector of your style. (Copy and
paste the following, it’s a lot to type and have it come out perfect.)
Paste this into your Tag field for that style.
J
On Mar 3, 2011, at 6:03 PM, Walter Lee Davis wrote:
This is the correct way to create the style. Next step is to select
the link text of the “here” option in your menu, and open the
Hyperlink dialog. Press Extended, then New, then add the classname
thus: http://scripty.walterdavisstudio.com/class.jpg (you can’t see
it, but the link for Products was selected before that stack of
dialogs was raised above the screen).
Walter
On Mar 3, 2011, at 5:48 PM, Julie Maxwell Allen wrote:
I then highlighted the link word (welcome for instance) on the
equal page and then did extended, new, class / here
It seems not to be working.
May I please get a bit of direction on what is going wrong.
thanks
J
On Mar 3, 2011, at 5:12 PM, waltd wrote:
The colon signifies what’s called a pseudo-selector. a:link,
a:hover, etc. are examples of these. They relate to user
interaction. Another example is a checkbox or radio button –
they have the :checked pseudo-selector, which gets applied to the
field when it’s in its checked state.
So these attributes can change after the page has loaded, because
the user interacts with the page and causes them to be modified
on screen – but not in source code. This is why they are called
pseudo-selectors; they differ from a normal selector because they
can change after the page has loaded.
Contrast that with say a classname, signified by the dot in a CSS
selector. That attribute is set by the HTML, and doesn’t change.
Other types of selectors include the tag name (here, that’s an
‘a’ for anchor tag) or the ID, signified in a selector by the #
octothorp symbol.
CSS Selector
HTML Code
a.foo
<a class="foo" ...>
#bar
<div id="bar">
div.sidebar h3
<div class="sidebar"><h3>
Building up combinations of these attributes make CSS selectors
very precise, capable of reaching in with tweezers and adding the
fo’castle to the rigging of your pirate ship in a bottle. Careful
use of parent tags to set attributes that you want to “cascade”
throughout part or all of the page structure allow you to
instantly paint all the type a single color, or all the type in a
sidebar a different color, without going through and adjusting
the same attribute in dozens of individual styles.
Thank you. I will. Should I change the ones in the inspector back to default or leave them as is?
J
Sent from my iPhone
On Mar 3, 2011, at 10:34 PM, Walter Lee Davis email@hidden wrote:
It sure could. Try modifying the selector of your style. (Copy and paste the following, it’s a lot to type and have it come out perfect.) Paste this into your Tag field for that style.
J
On Mar 3, 2011, at 6:03 PM, Walter Lee Davis wrote:
This is the correct way to create the style. Next step is to select the link text of the “here” option in your menu, and open the Hyperlink dialog. Press Extended, then New, then add the classname thus: http://scripty.walterdavisstudio.com/class.jpg (you can’t see it, but the link for Products was selected before that stack of dialogs was raised above the screen).
Walter
On Mar 3, 2011, at 5:48 PM, Julie Maxwell Allen wrote:
I then highlighted the link word (welcome for instance) on the equal page and then did extended, new, class / here
It seems not to be working.
May I please get a bit of direction on what is going wrong.
thanks
J
On Mar 3, 2011, at 5:12 PM, waltd wrote:
The colon signifies what’s called a pseudo-selector. a:link, a:hover, etc. are examples of these. They relate to user interaction. Another example is a checkbox or radio button – they have the :checked pseudo-selector, which gets applied to the field when it’s in its checked state.
So these attributes can change after the page has loaded, because the user interacts with the page and causes them to be modified on screen – but not in source code. This is why they are called pseudo-selectors; they differ from a normal selector because they can change after the page has loaded.
Contrast that with say a classname, signified by the dot in a CSS selector. That attribute is set by the HTML, and doesn’t change. Other types of selectors include the tag name (here, that’s an ‘a’ for anchor tag) or the ID, signified in a selector by the # octothorp symbol.
CSS Selector
HTML Code
a.foo
<a class="foo" ...>
#bar
<div id="bar">
div.sidebar h3
<div class="sidebar"><h3>
Building up combinations of these attributes make CSS selectors very precise, capable of reaching in with tweezers and adding the fo’castle to the rigging of your pirate ship in a bottle. Careful use of parent tags to set attributes that you want to “cascade” throughout part or all of the page structure allow you to instantly paint all the type a single color, or all the type in a sidebar a different color, without going through and adjusting the same attribute in dozens of individual styles.
OK, I pasted that into the tag field for the style that I had made for the a.here
I left the inspector link settings as is.
I left the extended alone also.
I am still just getting the bold. I am unsure what I am doing wrong.
At least I know its 1/2 working and I am on the right track. LOL
j
On Mar 3, 2011, at 10:56 PM, Julie Maxwell Allen wrote:
Thank you. I will. Should I change the ones in the inspector back to default or leave them as is?
J
Sent from my iPhone
On Mar 3, 2011, at 10:34 PM, Walter Lee Davis email@hidden wrote:
It sure could. Try modifying the selector of your style. (Copy and paste the following, it’s a lot to type and have it come out perfect.) Paste this into your Tag field for that style.
J
On Mar 3, 2011, at 6:03 PM, Walter Lee Davis wrote:
This is the correct way to create the style. Next step is to select the link text of the “here” option in your menu, and open the Hyperlink dialog. Press Extended, then New, then add the classname thus: http://scripty.walterdavisstudio.com/class.jpg (you can’t see it, but the link for Products was selected before that stack of dialogs was raised above the screen).
Walter
On Mar 3, 2011, at 5:48 PM, Julie Maxwell Allen wrote:
I then highlighted the link word (welcome for instance) on the equal page and then did extended, new, class / here
It seems not to be working.
May I please get a bit of direction on what is going wrong.
thanks
J
On Mar 3, 2011, at 5:12 PM, waltd wrote:
The colon signifies what’s called a pseudo-selector. a:link, a:hover, etc. are examples of these. They relate to user interaction. Another example is a checkbox or radio button – they have the :checked pseudo-selector, which gets applied to the field when it’s in its checked state.
So these attributes can change after the page has loaded, because the user interacts with the page and causes them to be modified on screen – but not in source code. This is why they are called pseudo-selectors; they differ from a normal selector because they can change after the page has loaded.
Contrast that with say a classname, signified by the dot in a CSS selector. That attribute is set by the HTML, and doesn’t change. Other types of selectors include the tag name (here, that’s an ‘a’ for anchor tag) or the ID, signified in a selector by the # octothorp symbol.
CSS Selector
HTML Code
a.foo
<a class="foo" ...>
#bar
<div id="bar">
div.sidebar h3
<div class="sidebar"><h3>
Building up combinations of these attributes make CSS selectors very precise, capable of reaching in with tweezers and adding the fo’castle to the rigging of your pirate ship in a bottle. Careful use of parent tags to set attributes that you want to “cascade” throughout part or all of the page structure allow you to instantly paint all the type a single color, or all the type in a sidebar a different color, without going through and adjusting the same attribute in dozens of individual styles.
I see the problem. Your link styles for that HTML box have higher
precedence than the generic .here styles, because they are preceded by
the ID #menu. So they out-vote the class-based style. Here’s my final
offer, which should probably kill it dead:
PS: I used to use a fascinating program to visualize this called Xyle
scope. They used the following math: an ID was worth 100 points, a
class was worth 10 points, and a tag was worth 1 point. If you
combined these elements in a selector, you would either add these
values to come up with the resulting weight of the total selector. A
heavier selector would have more oomph and could override a lower
weight selector. The reason why your font-weight worked, while the
color did not, is because the more specific ID-based rule didn’t have
anything to say about weight. This is where CSS can get really
complicated – it’s not just the things you declare in which rule, but
the things you omit, that can influence how something will eventually
appear on the screen.
On Mar 4, 2011, at 9:24 AM, Julie Maxwell Allen wrote:
OK, I pasted that into the tag field for the style that I had made
for the a.here
I left the inspector link settings as is.
I left the extended alone also.
I am still just getting the bold. I am unsure what I am doing wrong.
At least I know its 1/2 working and I am on the right track. LOL
Julie
On Mar 4, 2011, at 10:48 AM, Walter Lee Davis wrote:
I see the problem. Your link styles for that HTML box have higher precedence than the generic .here styles, because they are preceded by the ID #menu. So they out-vote the class-based style. Here’s my final offer, which should probably kill it dead:
PS: I used to use a fascinating program to visualize this called Xyle scope. They used the following math: an ID was worth 100 points, a class was worth 10 points, and a tag was worth 1 point. If you combined these elements in a selector, you would either add these values to come up with the resulting weight of the total selector. A heavier selector would have more oomph and could override a lower weight selector. The reason why your font-weight worked, while the color did not, is because the more specific ID-based rule didn’t have anything to say about weight. This is where CSS can get really complicated – it’s not just the things you declare in which rule, but the things you omit, that can influence how something will eventually appear on the screen.
On Mar 4, 2011, at 9:24 AM, Julie Maxwell Allen wrote:
OK, I pasted that into the tag field for the style that I had made for the a.here
I left the inspector link settings as is.
I left the extended alone also.
I am still just getting the bold. I am unsure what I am doing wrong.
At least I know its 1/2 working and I am on the right track. LOL
and thank you for that program info. I have downloaded to start exploring and learning.
Walter you are really a gentlemen and thank you for all you do!
Julie
On Mar 4, 2011, at 10:48 AM, Walter Lee Davis wrote:
I see the problem. Your link styles for that HTML box have higher precedence than the generic .here styles, because they are preceded by the ID #menu. So they out-vote the class-based style. Here’s my final offer, which should probably kill it dead:
PS: I used to use a fascinating program to visualize this called Xyle scope. They used the following math: an ID was worth 100 points, a class was worth 10 points, and a tag was worth 1 point. If you combined these elements in a selector, you would either add these values to come up with the resulting weight of the total selector. A heavier selector would have more oomph and could override a lower weight selector. The reason why your font-weight worked, while the color did not, is because the more specific ID-based rule didn’t have anything to say about weight. This is where CSS can get really complicated – it’s not just the things you declare in which rule, but the things you omit, that can influence how something will eventually appear on the screen.
On Mar 4, 2011, at 9:24 AM, Julie Maxwell Allen wrote:
OK, I pasted that into the tag field for the style that I had made for the a.here
I left the inspector link settings as is.
I left the extended alone also.
I am still just getting the bold. I am unsure what I am doing wrong.
At least I know its 1/2 working and I am on the right track. LOL
BTW - I dont think you need it Bold as well as Yellow
Also the Yellow ‘Down To Earth’ in the page header is difficult to read for me and the brown Marketing etc isn’t much better… This may be down to the size of the text.
I am trying to use colors used other places in the site to tie it all together.
J
On Mar 4, 2011, at 2:58 PM, DeltaDave wrote:
BTW - I dont think you need it Bold as well as Yellow
Also the Yellow ‘Down To Earth’ in the page header is difficult to read for me and the brown Marketing etc isn’t much better… This may be down to the size of the text.
