Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl Monk, Perl Meditation
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??

yank out all the unique font tag combinations, make each a classid, make the appropriate substituions, and you're done

I think that strategy would defeat the background idea of CSS, which is to separate the visual format from the coding.

By listing all unique font tag combos, you drop the content-related bits. e.g. you might find a combination of Arial - Bold and 14 point in a "h2" header and in the top row of a table. By giving this combination a unique classid ("ArialBold14" ?) and putting this info in the CSS-file, you really make the problem worse, as now you cannot anymore change the appearance of the "h2" header without also changing the top row of the table.

At least you should also code into your "CSS-database" the "surroundings" of where the classid is to be put.

CSS-items should be "meaningful", i.e. something like "ColumnHeader" or "BodyText" or "Title" or ... and should not directly describe the form of these items as this will get you no benefit for using CSS.

Update: Podmaster I agree a H1-tag is not a font-tag, but you find the one contained within the other and similarity in (font)-formatting says nothing about the meaning this formatting wants to convey.

CountZero

"If you have four groups working on a compiler, you'll get a 4-pass compiler." - Conway's Law


In reply to Re: Re: How would I write a CSS generator script? by CountZero
in thread How would I write a CSS generator script? by LameNerd

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others taking refuge in the Monastery: (6)
As of 2024-03-29 05:33 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found