/*Y08oct12tkb.css... my second "serious" external CSS!
(First "non- serious" was same week, and just a brief stepping stone.)

CSS for Pascal tutorial pages, with different styles for...

General text (default)
Pascalite-only text
FPC-only       text
Arduino-only   text

General pre-formatted material- code and terminal o/p (default)
Pascalite-only pre-formatted material- code and terminal o/p
FPC-only       pre-formatted material- code and terminal o/p
Arduino-only   pre-formatted material- code and terminal o/p


Some pages need re-writing...

Use, e.g., pre.tkbCodeArdu, NOT (deprecated, even though it "worked") this approach....

<div class=tkbCodeArdu>
<pre>
stuff...
</pre>
</div>

For the "div" based CSS, link to Y08oct12tkb.css
Keep Y08...12 and ...13 in step... if, say, TxtPLite is changed in one, change it also in the other

Tinker with the following (Code/Text.. Ardu/Pascalite/FPC) at your peril!! (Use Y08oct12tkbTEST.htm) Note that the colors are "tuned"... the text and code colors are NOT the same.. but tweaked to appear the same in the bold and non-bold versions. Also, arial used to distinguish language-specific text from other text.


The FPC/PLite distingishing was the main point. The Ardu stuff may be an unnecessary distraction... but Ardu pages will have to be dealth with, if that stuff (re-)moved.*/

/*Use default "body" for text relating to either compiler*/

/*Not sure why I did body {font-size:1em;}... perhaps scrap from
pages capable of multiple text types, for multiple
compilers?*/

/*body {font-size:1em;}*/

/*ONCE UPON A TIME, I did this (redefine basic "pre").
Doing it now...
wrecks the old "div" style coding,
isn't necessary- leaving it out doesn't hurt the <pre class= style coding.

Redefine the "plain" pre... */
/*pre {color:#33CC00; font-weight:bold; font-family:"courier new",monospace;}
*/
/*THE FOLLOWING NEED CHANGING FROM THE div. MODEL TO THE
PRE.tkbCodeFPC (ETC) and P.tkbTxtPLite (ETC) MODEL... as do the pages driven by this code... ARGH...

AS A TRANSITIONAL STEP..... KEEP both div. and p. / pre. styles in the sheets. When all dependent pages have had div. stuff written out, the div. styles can be removed from the stylesheet.*/

/*___________*/
/*for some reason the following was once necessary... remming it out mades div.tkbCodeFPC, etc, not work as intended.
N.B.: "pre" is given a redefinition a few lines above here....*/

/*  pre {font-family:"courier new",monospace;}*/
/*-------------*/



/*CODE styles.... Use for code, and terminal i/o depictions.*/
/*Use for code that relates just to FPC/ Borland TP */
pre.tkbCodeFPC {color:#339900;font-size:large; font-weight:bold;}

/*Use for code that relates just to Pascalite */
pre.tkbCodePLite {color:#9999ff;font-size:large; font-weight:bold;}

/*Use for code that relates to either FPC/ Borland TP */
pre.tkbCodeEither {color:#996633;font-size:large; font-weight:bold;}

/*Use for code that relates just to Arduino.*/
pre.tkbCodeArdu {color:#0080ff;font-size:large; font-weight:bold;}

/*TEXT styles...*/
/*Use for text that relates just to FPC/Borland TP*/
p.tkbTxtFPC {color:#339900;font-size:medium;font-family:"arial";}

/*Use for text that relates just to Pascalite*/
p.tkbTxtPLite {color:#3366cc;font-size:medium;font-family:"arial"}

/*Use for text that relates just to Arduino*/
p.tkbTxtArdu {color:#9980ff;font-size:medium;font-family:"arial"}

/*(There is no TxtEither style)*/


/*====*/


/*<<SCRAP???>>>>> for some reason the following <WHAT??>>is necessary?
Remming it out makes div.tkbCodeFPC, etc, not work as intended... but changed since that rem written, so maybe messed up anyway.

CSS in original plt1a, from which this is a clone of a clone, was my second page with my "own style" in a form that passed validation. Furthermore, I extended to FOUR own styles in plt1a. 

Developed plt1a CSS 22 June 07
http://www.alistapart.com/articles/practicalcss/ and
http://www.w3.org/QA/Tips/font-size and
http://www.w3.org/TR/REC-CSS2/fonts.html
were very helpful.


** DERIVES FROM**: My first "own style". SUCCESSFUL!!! 4 June 2007 4:34 pm (on ele9ppp): My 1st "Own style". Done with "class". Had tried various things... for hours. Gave problem a rest. Came back to it after nice w/e with Chris and Ruth, 1-3 June 07, during which I blew tyre. Searched Waterstone's shelves while waiting for tyre repair.... and hints there led me to http://www.alistapart.com/articles/practicalcss/ which provided the last link!!
Try to expand understanding of the following: in this, we're setting the "basis". Once that's done, then, to quote 1st cited page: "use absolute size ([ xx-small | x-small | small | medium | large | x-large | xx-large ]) or relative size ([ larger | smaller ]) when defining the font size for a particular element within the document."*/