3 ms·
This isn't going to happen unless you implement your webpages in SVG. (Not a particularly bad idea, considering today's commercial webpages.) SGML, and therefo
by yason 16y ago
This isn't going to happen unless you implement your webpages in SVG. (Not a particularly bad idea, considering today's commercial webpages.)
SGML, and therefore HTML, were designed for a completely different purpose, and are based on the decades-old recognition of the need for separation of content and presentation. While HTML contains much more visual elements than most other SGML languages, complete with CSS it's still all optimized for two particular use cases:
- you have content and want to publish it some way, style being a secondary question, or
- you have lots of one kind of content and you conclude that it's worthwhile to hone a nice presentation for that one kind.
Photoshopping websites just isn't supported by the philosophy of document markup languages, even if you can actually make the first 50% happen with the current HTML/CSS/JS.
- Keyframe 16y agoI don't see why not. For example current workflow is rather similar among designers I saw. You whip out a layout+design. There are designated areas in layout. For example this is where main content goes, this is a navigation area, this is a subnav area and so on. You slice it up, you code html+css for each - this one is stretchy, this one has borders like that from css or from photoshop, background this like that... I'm doing it all now without SVG. In fact I could do it with PS->slice html output, but I don't because fixing html+css output is more work than straight coding from scratch and fetching/cropping images out from PS as I need them. Thus, system obviously works. Problem is that it is manual, since tool available for it is not reliable.