> Thanks for the link. I didn't look at it yet, because your explanation
> and tips were perfect for me. I think I sorta get it now.
>> Thanks for the link. I didn't look at it yet, because your explanation
>> and tips were perfect for me. I think I sorta get it now.
[quoted text clipped - 3 lines]
>you don't read this (or another) tutorial or a book on CSS-P then you
>will most likely not get much further next time around.
Sorry, I meant your explanation helped me to understand the meaning of
"absolute". Once I see it explained like that, it seems so simple. It
did not, however, help me to "program" positioning.
>> Having said that, I am re-writing my site using "em" instead of "px"
>> and "pt", etc. and would really like to implement that into this
[quoted text clipped - 3 lines]
>don't at least read the first chapter of any CSS book or the most basic
>of articles on CSS.
OK. I guess I thought that was more advanced.
>> Since it is a relative
>> term, I don't think you can just translate pixels into "em" (I don't
[quoted text clipped - 4 lines]
>have no clue about this then you are definitely wasting the time of
>others who may be reading this post.
Maybe stupid is the wrong word, but I have troubles grasping certain
concepts that introduce many new elements (especially new meanings for
old words) all at once. I wasn't pretending to be ignorant. I really
don't know what it means. Obviously, that is not "endearing" and I see
now, thanks to you and Stan, that I have been using this group as a
shortcut to actually learning a few things first.
For that I am truly sorry, to you and Stan and anybody else who
bothered to read my posts.
>> but if I could approximate it on my screen, I would be confident it
>> would display appropriately for others. Is there a tool or is this
>> sort of thing covered in that tutorial?
>
>You got to be kidding. Where are you getting this junk from -
? Out of my head.... Is that an incredibly stupid question? I don't
know....
>>>BTW the learning curve for positioning is somewhat steep as it takes a
>>>while to get the hang of things. Read the tutorial that I mentioned and
[quoted text clipped - 4 lines]
>Right, BUT not today. Maybe tomorrow and most likely never. Stan was
>right this attitude is tiresome....
Actually, I read it about half an hour after I posted my message. I
also read the CSS tutorial on the same site, though it pretty much
covered stuff I already knew. I have looked at other sites and will
continue to do so.
>> I'm gonna go look at that link now, check out their CSS tutorial and
>> see if I can figure out how to replace a table with css....
>
>Do yourself (and everyone else here) a favor - before jumping into CSS-P
>read a couple tutorials and maybe even a book on CSS.
OK, I will. Thank you for your help and thanks to everyone else who
was helpful. I have bookmarked a number of the sites suggested and I
see that I need to go read those now instead of posting more stupid /
ignorant / obvious questions here.
I will continue to read others' posts here and maybe I will find some
interesting ideas. But until I am truly stumped and cannot find my
question already answered elsewhere, I will not post here.
Thanks.
Nikolaos Giannopoulos - 30 Aug 2003 16:43 GMT
> Sorry, I meant your explanation helped me to understand the meaning of
> "absolute". Once I see it explained like that, it seems so simple. It
> did not, however, help me to "program" positioning.
Right. And that's why I recommended the tutorial. But you said that
you would read it later.
The problem is in your attitude not the content of your posts:
+ You asked an advanced question
+ You asked for a tutorial on an advanced topic to help you
+ I answered your question and I am glad the explanation was sufficient
+ I suggested an advanced tutorial that I found to be useful
+ I told you that this area is difficult to master but that you need to
read tutorials or a book and that it will eventually make sense
+ You solved *this* problem with the content of my reply
+ You ignored the suggestion to read the advanced tutorial
+ You suggested that you will probably forget everything tomorrow
+ You followed up with an an extremely rudimentary question on em's that
clearly shows that you have not read even the most basic of chapters on CSS
In summary: You asked for help and additional information; got the
help; got the additional information; said thank you and rejected the
additional information. In a nut shell, my time is worth wasting
helping you out but your time is not worth wasting helping yourself out.
Doesn't sound right does it.
>>>Having said that, I am re-writing my site using "em" instead of "px"
>>>and "pt", etc. and would really like to implement that into this
>>>style, but I am at a loss for how to do that.
>
> OK. I guess I thought that was more advanced.
em is a unit of measurement just like px (pixels), %, etc.... "In CSS,
1em is equivalent to the value of the elements font-size"[1]. if the
font-size is "equivalent" to 12px then 2em is "equivalent" to 24px. I
say equivalent since you may specify font-size of 100% instead of 12px
and as such you may not know the exact font-size factor that is used.
And that is the nice thing about this unit in that you don't have to
know what font-size is used - you just know that the value you specify
will be that value times the font-size. That's why it is called a
relative unit of measurement. If the font-size was changed to another
value then anything that specified em's would be adjusted accordingly.
However, IE 5.X Win has some issues with em units being used to specify
a margin (and possibly other bugs exist as well - I am not sure). In
general I just use % as the unit for everything except when it makes
sense to use px e.g. absolute positioning of a block.
>>>Since it is a relative
>>>term, I don't think you can just translate pixels into "em" (I don't
[quoted text clipped - 4 lines]
> old words) all at once. I wasn't pretending to be ignorant. I really
> don't know what it means.
Then that is your cue to look it up. The CSS specs can be found here:
http://www.w3.org/Style/CSS/
Specifically the CSS1 and CSS2 specs are (off the above links side bar):
http://www.w3.org/TR/CSS1
http://www.w3.org/TR/CSS2
And to read up on units see here:
http://www.w3.org/TR/CSS1#units
> Obviously, that is not "endearing" and I see
> now, thanks to you and Stan, that I have been using this group as a
> shortcut to actually learning a few things first.
> For that I am truly sorry, to you and Stan and anybody else who
> bothered to read my posts.
Nobody will or at least should fault you for not knowing about
something. Everyone has to ask basic questions at some point.
I think you need to realize the distinction of asking a basic question
and demonstrating no capacity to try yet wanting to be spoon fed
answers. Like I said its about attitude not content.
> Actually, I read it about half an hour after I posted my message. I
> also read the CSS tutorial on the same site, though it pretty much
> covered stuff I already knew.
Then I suggest you re-read the tutorial on "Using Style Sheets" (there
are only 2) and specifically re-read the section on "Lengths and Units" at:
http://brainjar.com/css/using/default5.asp
> OK, I will. Thank you for your help and thanks to everyone else who
> was helpful. I have bookmarked a number of the sites suggested and I
> see that I need to go read those now instead of posting more stupid /
> ignorant / obvious questions here.
Good idea ;-)
> I will continue to read others' posts here and maybe I will find some
> interesting ideas. But until I am truly stumped and cannot find my
> question already answered elsewhere, I will not post here.
> Thanks.
Reading other posts and following along is an excellent way to
complement reading on your own. No, you don't have to be truly stumped
to ask a question - but I have already made this point see above.
Good Luck,
--Nikolaos