4 ms·
Agree that emulating browser type rendering isn't necessarily good in the long term, but why not build in support for a variety of different type rendering engi
by blehn 16y ago
Agree that emulating browser type rendering isn't necessarily good in the long term, but why not build in support for a variety of different type rendering engines? Adobe is halfway there with Smooth, Strong, Crisp, etc... they could simply add options for WebKit, Firefox, IE...
Also, a web-focused app may not be necessary, but I think a digital-focused app is (well, I guess that would be Fireworks). Photoshop and Illustrator really are terrible tools for designing digital applications, for the simple fact that working with pixel-level detail is a pain in the ass (e.g. try making a 92px by 147px rectangle with no sub-pixel edges in one of those applications). Fireworks actually comes pretty darn close to what Jason is asking for, but Adobe seems to neglect its core functionality in favor of expanding on useless export options and plugins.
- bobbygrace 16y agoI would love to see additional type rendering options, but this would have to account for the OS as well and Adobe tools would have to accept WOFF and EOT files, which counters FontFont's point of offering web fonts DRM-free. And I still don't think there will be a tool that makes code better than a hand, not that such a tool couldn't assist in a great way. TextMate snippets and CSS preprocessors maybe, but that's not exactly WYSIWYG to HTML.