| Curious; what type of display were you reading on? How big is
it? What was its resolution? -------------------- Reading it on a 27" 2560x1440 display was really nice. Same in
vertical mode on a 9.7" iPad, but not so good in horizontal
mode; it felt constricted like watching a letter-boxed 16:9
movie on a 19" 4:3 TV screen. What I've found is that optimal text formatting varies greatly
across devices. This is very hard to design for due to the
variety of screens. From small screen devices like cell phones
and gray-scale Kindle's, through larger 24" - 30" monitors and
even larger HDTV's. On top of that there are DPI variances. I've always been a fan of MVC, separating the model (actual
document data/text/pictures) from the view (how it's
displayed), and using a controller (device/screen-specific
code) to display things optimally. It would be nice if there was a standard that existed
allowing authors to simply write documents, saving them as
models. Then, each device could read from a standard model
file and, using custom controller code, generate a view
displaying the text/images optimized for its display. Right now you see web developers creating multiple CSS
layouts for different screen layouts. This works for most
cases, but not edge scenarios. It feels very hacky, and I
can't foresee people building websites/content-delivery-mechanisms
like this 10 years into the future. There must be a better way. |
This standard is called "HTML". What you describe is the entire idea of HTML. Frankly, it's embarrassing that a web browser presented with a long stream of text won't keep the line lengths capped at a reasonable length.