in reply to How would I write a CSS generator script?

Are you rich?

Here's strategy, build a tree using TreeBuilder, yank out all the unique font tag combinations, make each a classid, make the appropriate substituions, and you're done.

Then do the same for other tags, such as P or Table , Td ... you get the picture. The big problem curious bit as I see it is generating meaningful names for the class id's, especially if humans are gonna be looking after this later.

update: CountZero interesting, but font tags are <font> tags, not h2 or h1 or whatever. One thing he needs for sure is to identify similar markup(whatever that may mean) and translate that into a css equivalent. However exactly he decides that is up to him (he has the tree so he can go buck wild).


MJD says you can't just make shit up and expect the computer to know what you mean, retardo!
I run a Win32 PPM repository for perl 5.6x+5.8x. I take requests.
** The Third rule of perl club is a statement of fact: pod is sexy.

Replies are listed 'Best First'.
Re: Re: How would I write a CSS generator script?
by CountZero (Bishop) on Jun 03, 2003 at 05:59 UTC

    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