Listing entries tagged with design_curmudgeonry

1 | 2 | 3

serial killer   03.15.2006, 6:30 PM

Alex Lencicki is a blogger with experience serializing novels online. Today, in a comment to my Slate networked book post, he links to a wonderful diatribe on his site deconstructing the myriad ways in which Slate's web novel experiment is so bad and so self-defeating -- a pretty comprehensive list of dos and don'ts that Slate would do well to heed in the future. In a nutshell, Slate has taken a novel by a popular writer and apparently done everything within its power to make it hard to read and hard to find. Why exactly they did this is hard to figure out.

Summing up, Lencicki puts things nicely in context within the history of serial fiction:

The original 19 th century serials worked because they were optimized for newsprint, 21st century serials should be optimized for the way people use the web. People check blogs daily, they download pages to their phones, they print them out at work and take them downstairs on a smoke break. There's plenty of room in all that activity to read a serial novel - in fact, that activity is well suited to the mode. But instead of issuing press releases and promising to revolutionize literature, publishers should focus on releasing the books so that people can read them online. It's easy to get lost in a good book when the book adapts to you.

Posted by ben vershbow at 6:30 PM | Comments (1) | TrackBack
tags: books , design , design_curmudgeonry , fiction , magazine , novel , publishing , serial , slate , the_networked_book , walter_kirn

who really needs to turn the pages?   02.15.2006, 6:16 PM

The following post comes from my friend Sally Northmore, a writer and designer based in New York who lately has been interested in things like animation, video game theory, and (right up our alley) the materiality of books and their transition to a virtual environment. A couple of weeks ago we were talking about the British Library's rare manuscript digitization project, "Turning the Pages" -- something I'd been meaning to discuss here but never gotten around to doing. It turns out Sally had some interesting thoughts about this so I persuaded her to do a brief write-up of the project for if:book. Which is what follows below. Come to think of it, this is especially interesting when juxtaposed with Bob's post earlier this week on Jefferson Han's amazing gestural interface design. Here's Sally... - Ben

The British Library's collaboration with multimedia impresarios at Armadillo Systems has led to an impressive publishing enterprise, making available electronic 3-D facsimiles of their rare manuscript collection.

"Turning the Pages", available in CD-ROM, online, and kiosk format, presents the digital incarnation of these treasured texts, allowing the reader to virtually "turn" the pages with a touch and drag function, "pore over" texts with a magnification function, and in some cases, access extras such as supplementary notes, textual secrets, and audio accompaniment.

Pages from Mozart's thematic catalogue -- a composition notebook from the last seven years of his life. Allows the reader to listen to works being discussed.

The designers ambitiously mimicked various characteristics of each work in their 3-D computer models. For instance, the shape of a page of velum turning differs from the shape of a page of paper. It falls at a unique speed according to its weight; it casts a unique shadow. The simulation even allows for a discrepancy in how a page would turn depending on what corner of the page you decide to peel from.

Online visitors can download a library of manuscripts in Shockwave although these versions are a bit clunkier and don't provide the flashier thrills of the enormous touch screen kiosks the British Library now houses.

Mercator's first atlas of Europe - 1570s

Online, the "Turning the Pages" application forces you to adapt to the nature of its embodiment--to physically re-learn how to use a book. A hand cursor invites the reader to turn each page with a click-and-drag maneuver of the mouse. Sounds simple enough, but I struggled to get the momentum of the drag just right so that the page actually turned. In a few failed attempts, the page lifted just so... only to fall back into place again. Apparently, if you can master the Carpal Tunnel-inducing rhythm, you can learn to manipulate the page-turning function even further, grabbing multiple of pages at once for a faster, abridged read.

The value of providing high resolution scans of rare editions of texts for the general public to experience, a public that otherwise wouldn't necessarily ever "touch" say, the Lindisfarne Gospels, doesn't go without kudos. Hey, democratic right? Armadillo Systems provides a list of compelling raisons d'être on their site to this effect. But the content of these texts is already available in reprintable (democratic!) form. Is the virtual page-turning function really necessary for greater understanding of these works, or a game of academic scratch-n-sniff?

The "enlarge" function even allows readers to reverse the famous mirror writing in Leonardo da Vinci's notebooks

At the MLA conference in D.C. this past December, where the British Library had set up a demonstration of "Turning the Pages", this was the question most frequently asked of the BL's representative. Who really needs to turn the pages? I learned from the rep's response that, well, nobody does! Scholars are typically more interested studying the page, and the turning function hasn't proven to enhance or revive scholarly exploration. And surely, the Library enjoyed plenty of biblio-clout and tourist traffic before this program?

But the lure of new, sexy technology can't be underestimated. From what I understood, the techno-factor is an excellent beacon for attracting investors and funding in multimedia technology. Armadillo's web site provides an interesting sales pitch:

By converting your manuscripts to "Turning the Pages" applications you can attract visitors, increase website traffic and add a revenue stream - at the same time as broadening access to your collection and informing and entertaining your audience.

The program reveals itself to be a peculiar exercise, tangled in its insistence on fetishizing aspects of the material body of the text--the weight of velum, the karat of gold used to illuminate, the shape of the binding. Such detail and love for each material manuscript went into this project to recreate, as best possible, the "feel" of handling these manuscripts.

Under ideal circumstances, what would the minds behind "Turning the Pages" prefer to create? The original form of the text--the "alpha" manuscript--or the virtual incarnation? Does technological advancement seduce us into valuing the near-perfect simulation over the original? Are we more impressed by the clone, the "Dolly" of hoary manuscripts? And, would one argue that "Turning the Pages" is the best proxy for the real thing, or, another "thing" entirely?

Posted by sally northmore at 6:16 PM | Comments (6)
tags: Libraries, Search and the Web , book_craft , books , design , design_curmudgeonry , digitization , interface , library , manuscript , museum , preservation , reading , turning_the_pages , user_interface

harper-collins half-heartedly puts a book online   02.07.2006, 8:09 AM

As noted in The New York Times, Harper-Collins has put the text of Bruce Judson's Go It Alone: The Secret to Building a Successful Business on Your Own online; ostensibly this is a pilot for more books to come.

Harper-Collins isn't doing this out of the goodness of their hearts: it's an ad-supported project. Every page of the book (it's paginated in exactly the same way as the print edition) bears five Google ads, a banner ad, and a prominent link to buy the book at Amazon. Visiting Amazon suggests other motives for Harper-Collins's experiment: new copies are selling for $5.95 and there are no reader reviews of the book, suggesting that, despite what the press would have you believe, Judson's book hasn't attracted much attention in print format. Putting it online might not be so much of a brave pilot program as an attempt to staunch the losses for a failed book.

Certainly H-C hasn't gone to a great deal of trouble to make the project look nice. As mentioned, the pagination is exactly the same as the print version; that means that you get pages like this, which start mid-sentence and end mid-sentence. While this is exactly what print books do, it's more of a problem on the web: with so much extraneous material around it, it's more difficult for the reader to remember where they were. It wouldn't have been that hard to rebreak the book: on page 8, they could have left the first line on the previous page with the paragraph it belongs too while moving the last line to the next page.

It is useful to have a book that can be searched by Google. One suspects, however, that Google would have done a better job with this.

Posted by dan visel at 8:09 AM | Comments (6)
tags: Publishing, Broadcast, and the Press , ads , design_curmudgeonry , ebooks , harper-collins , judson , publishing

two newspapers   01.04.2006, 11:21 AM

I picked up The New York Times from outside my door this morning knowing that the lead headline was going to be wrong. I still read the print paper every morning – I do read the electronic version, but I find that my reading there tends to be more self-selecting than I'd like it to be – but lately I find myself checking the Web before settling down to the paper and a cup of coffee. On the Web, I'd already seen the predictable gloating and hand-wringing in evidence there. Because of some communication mixup, the papers went to press with the information that the trapped West Virginia coal miners were mostly alive; a few hours later it turned out that they were, in fact, mostly dead. A scrutiny of the front pages of the New York dailies at the bodega this morning revealed that just about all had the wrong news – only Hoy, a Spanish-language daily didn't have the story, presumably because it went to press a bit earlier. At right is the front page of today's USA Today, the nation's most popular newspaper; click on the thumbnail for a more legible version. See also the gallery at their "newseum". (Note that this link won't show today's papers tomorrow – my apologies, readers of the future, there doesn't seem to be anything that can be done for you, copyright and all that.)

At left is another front page of a newspaper, The New York Times from April 20, 1950 (again, click to see a legible version). I found it last night at the start of Marshall McLuhan's The Mechanical Bride: Folklore of Industrial Man. Published in 1951, The Mechanical Bride is one of McLuhan's earliest works; in it, he primarily looks at the then-current world of print advertising, starting with the front page shown here. To my jaundiced eye, most of the book hasn't stood up that well; while it was undoubtedly very interesting at the time – being one of the first attempts to seriously deal with how people interact with advertisements from a critical perspective – fifty years, and billions and billions of advertisements later, it doesn't stand up as well as, say, Judith Williamson's Decoding Advertisements manages to. But bits of it are still interesting: McLuhan presents this front page to talk about how Stephane Mallarmé and the Symbolists found the newspaper to be the modern symbol of their day, with the different stories all jostling each other for prominence on the page.

But you don't – at least, I don't – immediately see that when you look at the front page that McLuhan exhibits. This was presumably an extremely ordinary front page when he was exhibiting it, just as the USA Today up top might be representative today. Looked at today, though, it's something else entirely, especially when you what newspapers look like now. You can notice this even in my thumbnails: when both papers are normalized to 200 pixels wide, you can't read anything in the old one, besides that it says "The New York Times" as the top, whereas you can make out the headlines to four stories in the USA Today. Newspapers have changed, not just from black & white to color, but in the way the present text and images. In the old paper there are only two photos, headshots of white men in the news – one a politician who's just given a speech, the other a doctor who's had his license revoked. The USA Today has perhaps an analogue to that photo in Jack Abramoff's perp walk; it also has five other photos, one of the miners' deluded family members (along with Abramoff, the only news photos), two sports-related photos – one of which seems to be stock footage of the Rose Bowl sign, a photo advertising television coverage inside, and a photo of two students for a human interest story. This being the USA Today, there's also a silly graph in the bottom left; the green strip across the bottom is an ad. Photos and graphics take up more than a third of the front page of today's paper.

What's overwhelming to me about the old Times cover is how much text there is. This was not a newspaper that was meant to be read at a glance – as you can do with the thumbnail of the USA Today. If you look at the Times more closely it looks like everything on the front page is serious news. You could make an argument here about the decline of journalism, but I'm not that interested in that. More interesting is how visual print culture has become. Technology has enabled this – a reasonably intelligent high-schooler could, I think, create a layout like the USA Today. But having this possibility available would also seem to have had an impact on the content – and whether McLuhan would have predicted that, I can't say.

Posted by dan visel at 11:21 AM | Comments (0)
tags: Publishing, Broadcast, and the Press , culture , design , design_curmudgeonry , layout , mcluhan , news , newspaper

ted nelson & the ideologies of documents   10.31.2005, 4:59 PM

I. Nelson's criticism

Ted Nelson (introduced last week by Ben) is a lonely revolutionary marching a lonely march, and whenever he's in the news mockery is heard. Some of this is with good reason: nobody's willing to dismantle the Internet we have for his improved version of the Internet (which doesn't quite work yet). You don't have to poke around too long on his website to find things that reek of crackpottery. But the problems that Nelson has identified in the electronic world are real, even if the solutions he's proposing prove to be untenable. I'd like to expand on on one particular aspect of Nelson's thought prominent in his latest missive: his ideas about the inherent ideologies of document formats. While this sounds very blue sky, I think his ideas do have some repercussions for what we're doing at the Institute, and it's worth investigating them, if not necessarily buying off on Xanadu.

Nelson starts from the position that attempting to simulate paper with computers is a mistaken idea. (He's not talking about e-ink & the idea of electronic paper, though a related criticism could be made of that: e-ink by itself won't solve the problem of reading on screens.) This is correct: we could do many more things with virtual space than we can with a static page. Look at this Flash demonstration of Jef Raskin's proposed zooming interface (previously discussed here), for example. But we don't usually go that far because we tend to think of electronic space in terms of the technology that preceded it – paper space. This has carried over into the way in which we structure documents for online reading.

There are two major types of electronic documents online. In one, the debt to paper space is explicit: PDFs, one of the major formats currently used for electronic books, are a compressed version of Postscript, a specification designed to tell a printer exactly what should be on a printed page. While a PDF has more functionality than a printed page – you can search it, for example, and if you're tricky you can embed hyperlinks and tables of content in them – it's built on the same paradigm. A PDF is also like a printed page in that it's a finalized product: while content in a PDF can be written over with annotations, it's difficult to make substantial changes to it. A PDF is designed to be an electronic reproduction of the printed page. More functionality has been welded on to it by Adobe, who created the format, but it is, at its heart attempting to maintain fidelity to the printed page.

The other dominant paradigm is that of the markup language. A quick, not too technical introduction: a markup language is a way of encoding instructions for how a text is to be structured and formatted in the text. HTML is a markup language; so is XML. This web page is created in a markup language; if you look at it with the "View Source" option on your browser, you'll see that it's a text file divided up by a lot of HTML tags, which are specially designed to format web pages: putting <i> and </i> around a word, for example, makes it italic. XML is a broader concept than HTML: it's a specification that allows people to create their own tags to do other things: some people are using their own version of XML to represent ebooks.

There's a lot of excitement about XML – it's a technology that can be (and is)bent to many different uses. A huge percentage of the system files on your computer, for example, probably use some flavor of XML, even if you've never thought of composing an XML documents. Nelson's point, however, is that there's a central premise to all XML: that all information can be divided up into a logical hierarchy – an outline, if you will. A lot of documents do work this way: book is divided into chapters; a chapter is divided into paragraphs; paragraphs are divided into words. A newspaper is divided into stories; each story has a headline and body copy; the body copy is divided into paragraphs; a paragraph is divided into sentences; a sentence is divided into words; and words are divided into letters, the atom of the markup universe.

II. A Victorian example

But while this is the dominant way we arrange information, this isn't necessarily a natural way to arrange things, Nelson points out, or the only way. It's one way of many possible ones. Consider this spread of pages (double-click to enlarge them):

This is a title page from a book printed by William Morris, another self-identified humanist. We mostly think of William Morris (when we're not confusing him with the talent agency) as a source of wallpaper, but his work as a book designer can't be overvalued. The book was printed in 1893; it's entitled The Tale of King Florus and the Fair Jehane. Like all of Morris's books, it's sumptuous to the point of being unreadable: Morris was dead set on bringing beauty back into design's balance of aesthetics & utility, and maybe over-corrected to offset the Victorian fixation on the latter.

I offer this spread of pages as an example because the elements that make up the page don't break down easily into hierarchical units. Let's imagine that we wanted to come up with an outline for what's on these pages – let's consider how we would structure them if we wanted to represent them in XML. I'm not interested in how we could represent this on the Web or somewhere else – it's easy enough to do that as an image. I'm more interested in how we would make something like this if we were starting from scratch & wanted to emulate Morris's type and woodcuts – a more theoretical proposition.

First, we can look at the elements that comprise the page. We can tell each page is individually important. Each page has a text box, with decorative grapevines around the text box; inside the text box, the title gets its own page; on the second page, there's the title repeated, followed by two body paragraphs, separated by a fleuron. The first paragraph gets an illustrated dropcap. Each word, if you want to go down that far, is composed of letters.

But if you look closer, you'll find that the elements on the page don't decompose into categories quite so neatly. If you look at the left-hand page, you can see that the title's not all there – this is the second title page in the book. The title isn't part of the page – as would almost certainly be assumed under XML – rather, they're overlapping units. And the page backgrounds aren't mirror images of each other: each has been created uniquely. Look at the title at the top of the right-hand page: it's followed by seven fleurons because it takes seven of them to nicely fill the space. Everything here's been minutely adjusted by hand. Notice the characters in the title on the right and how they interact with the flourishes around them: the two A's are different, as are the two F's, the two N's, the two R's, the two E's. You couldn't replicate this lettering with a font. You can't really build a schema to represent what's on these two pages. A further argument: to make this spread of pages rigorous, as you'd have to to represent it in XML, would be to ruin them aesthetically. The vines are the way they are because the letters are the way they are: they've been created together.

The inability of XML to adequately handle what's shown on these pages isn't a function of the screen environment. It's a function of the way we build electronic documents right now. Morris could build pages this way because he didn't have to answer to the particular restraints we do now.

III. The ideologies of documents

Let's go back to Ted:

Nearly every form of electronic document- Word, Acrobat, HTML, XML- represents some business or ideological agenda. Many believe Word and Acrobat are out to entrap users; HTML and XML enact a very limited kind of hypertext with great internal complexity. All imitate paper and (internally) hierarchy.

For years, hierarchy simulation and paper simulation have been imposed throughout the computer world and the world of electronic documents. Falsely portrayed as necessitated by "technology," these are really just the world-view of those who build software. I believe that for representing human documents and thought, which are parallel and interpenetrating– some like to say "intertwingled"– hierarchy and paper simulation are all wrong.

It's possible to imagine software that would let us follow our fancy and create on the screen pages that look like William Morris's – a tool that would let a designer make an electronic woodcut with ease. Certainly there are approximations. But the sort of tool I imagine doesn't exist right now. This is the sort of tool we should have – there's no reason not to have it already. Ted again:

I propose a different document agenda: I believe we need new electronic documents which are transparent, public, principled, and freed from the traditions of hierarchy and paper. In that case they can be far more powerful, with deep and rich new interconnections and properties- able to quote dynamically from other documents and buckle sideways to other documents, such as comments or successive versions; able to present third-party links; and much more.

Most urgently: if we have different document structures we can build a new copyright realm, where everything can be freely and legally quoted and remixed in any amount without negotiation.

Ben does a fine job of going into the ramifications of Nelson's ideas about transclusion, which he proposes as a solution. I think it's an interesting idea which will probably never be implemented on a grand scale because there's not enough of an impetus to do so. But again: just because Nelson's work is unpragmatic doesn't mean that his critique is baseless.

I feel there's something similar in the grandiosity of Nelson's ideas and Morris's beautiful but unreadable pages. William Morris wasn't just a designer: he saw his program of arts and crafts (of which his books were a part) as a way to emphasize the beauty of individual creation as a course correction to the increasingly mechanized & dehumanized Victorian world. Walter Benjamin declares (in "The Author as Producer") that there is "a difference between merely supplying a production apparatus and trying to change the production apparatus". You don't have to make books exactly like William Morris's or implement Ted Nelson's particular production apparatus to have your thinking changed by them. Morris, like Nelson, was trying to change the production apparatus because he saw that another world was possible.

And a postscript: as mentioned around here occasionally, the Institute's in the process of creating new tools for electronic book-making. I'm in the process of writing up an introduction to Sophie (which will be posted soon) which does its best to justify the need for something new in an overcrowded world: Nelson's statement neatly dovetailed with my own thinking on the subject on why we need something new: so that we have the opportunity to make things in other ways. Sophie won't be quite as radical as Nelson's vision, but we will have something out next year. It would be nice if Nelson could do the same.

Posted by dan visel at 4:59 PM | Comments (7)
tags: design_curmudgeonry , markup , pdf , tednelson , transclusion , transiterature , walterbenjamin , williammorris , xml

premature burial, or, the electronic word in time and space   10.06.2005, 2:09 PM

We were talking yesterday (and Bob earlier) about how to better organize content on if:book - how to highlight active discussion threads, or draw attention to our various categories. Something more dynamic than a list of links on the sidebar, or a bunch of hot threads advertised at the top. A significant problem with blogs is the tyranny of the vertical column, where new entries call out for attention on a stack of rapidly forgotten material, much of which might still be worth reading even though it was posted back in the dark ages (i.e. three days ago). Some of the posts that get buried still have active discussions stemming from them. Just today, "ways of seeing, ways of writing" - posted nearly two weeks ago - received another comment. The conversation is still going. (See also Dan's "blog reading: what's left behind".)

This points to another thorny problem, still unsolved nearly 15 years into the world wide web, and several years into the blogging craze: how to visualize asynchronous conversations - that is, conversations in which time lapses between remarks. If the conversation is between only two people, a simple chronological column works fine - it's a basic back-and-forth. But consider the place where some of the most dynamic multi-person asynchronous conversations are going on: in the comment streams of blog entries. Here you have multiple forking paths, hopping back and forth between earlier and later remarks, people sticking close to the thread, people dropping in and out. But again, you have the tyranny of the vertical column.

We're using an open source platform called Drupal for our Next\Text project, which has a blog as its central element but can be expanded with modular units to do much more than we're able to do here. The way Drupal handles comments is nice. You have the usual column arranged chronologically, with comments streaming downward, but readers have the option of replying to specific comments, not just to the parent post. Replies to specific comments are indented slightly, creating a sort of sub-stream, and the the fork can keep on going indefinitely, indenting rightward.

This handles forks and leaps fairly well, but offers at best only a partial solution. We're still working with a print paradigm: the outline. Headers, sub-headers, bullet points. These distinguish areas in a linear stream, but they don't handle the non-linear character of complex conversations. There is always the linear element of time, but this is extremely limiting as an organizing principle. Interesting conversations make loops. They tangle. They soar. They sag. They connect to other conversations.

But the web has so far been dominated by time as an organizing principle, new at the top and old at the bottom (or vice versa), and this is one the most-repeated complaints people have about it. The web favors the new, the hot, the immediate. But we're dealing with a medium than can also handle space, or at least the perception of space. We need not be bound to lists and outlines, we need not plod along in chronological order. We could be looking at conversations as terrains, as topographies.

The electronic word finds itself in an increasingly social context. We need to design a better way to capture this - something that gives the sense of the whole (the big picture), but allows one to dive directly into the details. This would be a great challenge to drop into a design class. Warren Sack developed a "conversation map" for news groups in the late 90s. From what I can tell, it's a little overwhelming. I'm talking about something that draws people right in and gets them talking. Let's look around.

Posted by ben vershbow at 2:09 PM | Comments (4)
tags: Online , blog , blogging , blogs , comment , comments , content , conversation , design , design_curmudgeonry , dialogue , display , drupal , flow , graphical , graphics , infoviz , internet , layout , metadata , movable_type , platform , publishing , software , space , time , visualization , viz , web

blogs -- trying to fit round pegs into square holes   10.04.2005, 9:56 AM

i've been without an internet connection for a few days. was catching up on if:book posts and finding myself delighted by the wonderful range of interesting posts my colleagues had managed in just a few days. which made me want to send a note to lots of friends and acquaintances urging them to check out our blog. but then my more nervous, modest side took over and convinced me that urging people to sample a blog as wide-ranging as if:book is a dicey proposition since sampling one day's posts doesn't necessarily indicate the extent of our interests. the structure of blogs favors the chronology of entry; thematic categories are listed on the side but without much fanfare. wonder if we could re-arrange the "front page" to be more magazine like, where for example "recent posts" would be one feature among many.

Posted by bob stein at 9:56 AM | Comments (1)
tags: blog , blogger , blogging , blogs , design , design_curmudgeonry , interesting , layout , magazine , publishing