I apologise that I have not had the time to properly address this issue as I have been busy attending our local group's annual seminar, writing my next article plus family life. phew. That said, I noticed a minor error that I had in my code left over from before adding a css, so I have just removed the bgcolor from the body tag of both mather_01.html and mather_15.html from my site letting the css display the code itself.
You will now find in my css file:
BODY {
<!-- ... a lot of code removed...-->
background-color: #6f8c8f;
}and this alone displays the correct color for those pages.
You may be interested to know (if you don't already) that your web browser doesn't automatically display the web page when you put in the address. All web browser are parsers and in turn have to be able to read the information in a forward motion, so in order to do this, the web page code is downloaded onto your computer, then reads linearly from begining to end, then display the final output. Because *most css* code can be imported from an external file, this too must be downloaded then read before being displayed. If there are any in-line styles included in the <body></body> of your web page, it will override your css file. In-line styles can be avoided by creating class styles and including them in your css file then adding the relevant class name to the tag such <td class="blue"> and where there will be the appropriate code in the css file:
td.blue {
background-color: #0000ff;
}Therefore, because I have background-color in the body section of my css file, there is no need to have in the <body> tag of my html file. I will eventually get around to moving the remainder styles into my css file.
Firstly a correction, I have found a "blockquote" on the Pedigree contents page but as no parameters are given one can do what one wants with it from a css.
I too have noticed the blockquote in the legacy written code, along with many other obvious errors. I have been also cleaning up the Legacy code of all these errors which are quite numerous. I have been able toi eliminate a lot of the errors by slowly going through the generated code and physically recoding so there are no errors. I have just 3 minor errors I have left in from the 38 obvious errors picked up by a w3c validator, plus many others that I was able to pick up personally. I will be submitting these findings to the programmers so we can clean up the code if possible.
I have been unable to eliminate all the Legacy headers from the output as it insists on putting the specification and a few "meta" tags in. Hence the "/head" and "body" tags from Legacy cannot be eliminated. I cannot find a way of overcoming this. Whilst it is not a big problem per se, as far as I can see it can only be cut on a page by page basis.
I would like to be able to alter the colour of the windows. I see, Mark, that you have done this but cannot see how this can be done other than by changing the individual lines on each page (which is what I do by changing to a css class).
Yes, making the changes in a css file is quicker than making the individual changes for all pages. If you make a change, you only have to do it once, and it is instantly reflected in all the web pages.
Additionally, I would like to be able to change the background and "Family Links" colour on their heading but cannot see how to do this except page by page.
You should be able to do this in the css file as well, I have.
There are other things I like to change but I know that this is an "all purpose" generator so some work can be expected. I would have thought, however, that to place all the backgrounds borders and fonts in a css at the start of the "body" would not present a large problem.
Mark Legacy User Group Etiquette guidelines can be found at: http://www.LegacyFamilyTree.com/Etiquette.asp
To find past messages, please go to our searchable archives at: http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/
To unsubscribe please visit: http://www.legacyfamilytree.com/LegacyLists.asp
