Re:Almost perfect: the rise and fall of WordPerfect Corporat...
by e12e on Monday August 11, 2014 @10:04PM
(#8166320)
Somewhat related, I remember typesetting some project/essays in junior high-school on some DTP software on the Amiga. I can't recall the name now, but I don't think it was PageStream that seems to be most popular google hit (and is apparently still available both for Amiga OS, Windows and Linux): http://www.pagestream.org/?id=1663
Whatever software it was, the printer driver managed to output quite readable black text on our 9-pin dot-matrix printer (at an excruciatingly slow rate -- I remember pulling an all-nighter -- having finished a 10-20 page report on, I think nuclear weapons/the attacks on Japan -- at around 06:00 in the morning -- and the printout taking close to three hours making me late for school ...).
What was great about that pice, was that it followed the pattern of most modern DTP packages, with content-boxes that allowed you to flow text through them. And let you write your actual text in a plain ("distraction free") editor. Much better than the "rich" word processors at the time.
I still think Adobe's CSS region proposal[1] sounds pretty good -- not really as an addition to traditional CSS (a language suitable for styling, but unsuitable for layout) -- but as a way to augment CSS and HTML to become a language more-suited to layout (not good, not great, just not horribly bad). Lie[2], doesn't think so, but I think his perspective is inaccurate on this one. His points are valid, but I don't think he's really addressing the correct issue. CSS columns is a technical way to break up text. Allowing text to flow into boxes allows keeping the text plain and simple (think a classic html3 document with only text) and the layout separate (the divs/boxes). Lie appears to think in terms of a object/hypertext/rich document -- but that kind of thinking leads to single page apps where you can't read a blog article with js disabled.
Whatever software it was, the printer driver managed to output quite readable black text on our 9-pin dot-matrix printer (at an excruciatingly slow rate -- I remember pulling an all-nighter -- having finished a 10-20 page report on, I think nuclear weapons/the attacks on Japan -- at around 06:00 in the morning -- and the printout taking close to three hours making me late for school ...).
What was great about that pice, was that it followed the pattern of most modern DTP packages, with content-boxes that allowed you to flow text through them. And let you write your actual text in a plain ("distraction free") editor. Much better than the "rich" word processors at the time.
I still think Adobe's CSS region proposal[1] sounds pretty good -- not really as an addition to traditional CSS (a language suitable for styling, but unsuitable for layout) -- but as a way to augment CSS and HTML to become a language more-suited to layout (not good, not great, just not horribly bad). Lie[2], doesn't think so, but I think his perspective is inaccurate on this one. His points are valid, but I don't think he's really addressing the correct issue. CSS columns is a technical way to break up text. Allowing text to flow into boxes allows keeping the text plain and simple (think a classic html3 document with only text) and the layout separate (the divs/boxes). Lie appears to think in terms of a object/hypertext/rich document -- but that kind of thinking leads to single page apps where you can't read a blog article with js disabled.
[1] http://www.w3.org/TR/css3-regions/
[2] http://alistapart.com/blog/post/css-regions-considered-harmf...