Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
HTML to CSS converter?
- Thread starter amnost
- Start date
- Sort by reaction score
Besides, this might not even be the best forum for it. This is Community Discussion.
But to explain it further, you have several HTML pages looking the same, because one or more CSS file control the appearance.
I hope that helps.
You can write a few HTML pages and give them a unified and visually pleasing look with a CSS code, filled with numbers, pixels, lines and all sorts of stuff that you might easily learn.
Apparently you can. I would use this one: http://andylangton.co.uk/stuff/css-html-converter
But, I can't get it to work on my iPhone. It might work on my computer at home, though. Does it work for you on your computer?
I have no idea what that is.
HTML is a coding language. CSS is a styling language. No way to convert between the two.
HTML and CSS work together. You can't just switch them out.
Cascading style sheets are used to style the content generated with HTML. The only thing that CSS can replace from HTML is deprecated attributes (like backgrounds font sizes).
That tool is very old and doesn't work on the both browsers I tried. The author even says on the page it barely works.
What exactly are you trying to do?
No it doesn't work on a computer either. I was curious enough to see what it does, and it doesn't do anything. The author even notes at the bottom of the page:
(He really should stay that it doesn't work at all.)
HTML converted to CSS? That just makes no sense at all.
What he said.
Here is an analogy that may help -- HTML is like the building materials and structure, and the CSS is the blueprint to dictate how it all come together and is displayed.
Just as it would be silly to ask a builder to convert lumber, etc, to a blueprint, you can't convert HTML to CSS.
I think that "tool" you found is suppose to extract "inline CSS" to a cleaner CSS integration. But that is just a guess!
What are you trying to accomplish here?
HTH!
~ Jeremy
I think what the tool was supposed to do was take html, and then convert what is there to css and html code, there is alot over overlap on features between html and css
now i really recommend just learning how to use css and html properly
now i really recommend just learning how to use css and html properly
I think what everyone is trying to tell the OP, is that there is no commercial call for such a product, let alone having the market flooded with so many first rate products of this nature, that there are free, online alternatives.
But, I can see your point of view, you would like something that would "reverse-engineer" HTML code, perhaps pulling ALL styling information out of the HTML code, collating it and producing some sort of CSS.
Of course, any CSS produced would be awful to read and maintain, and wouldn't follow any desired pattern. It would also miss most of the functionality offered in CSS2.
In short, it would be easier, quicker and more desirable to plan and build most of your CSS first and only then go back in and rebuild your HTML pages by hand.
But, I can see your point of view, you would like something that would "reverse-engineer" HTML code, perhaps pulling ALL styling information out of the HTML code, collating it and producing some sort of CSS.
Of course, any CSS produced would be awful to read and maintain, and wouldn't follow any desired pattern. It would also miss most of the functionality offered in CSS2.
In short, it would be easier, quicker and more desirable to plan and build most of your CSS first and only then go back in and rebuild your HTML pages by hand.
I think you are correct. Most people in this forum are probably up to date with HTML5 and CSS3 and look scornfully at (or don't remember) the old specifications that didn't have separate styling and content layers.
When dealing with an old site, I normally take a screenshot and recode from scratch everytime. That way you don't have to work around what another coder thought was relevant at the time. Hell, most of the time I STILL see spans nested inside divs for styling, and half of the people I work with don't know how to style elements unless you explicitly give that item a class (and one intern here still throws everything into tables).