Categories
Art Books

The Art of Book, Volume One

A month or two ago, Steve at LanguageHat pointed out a New York show consisting of Art Deco book bindings by Pierre Legrain and Rose Adler. I was mesmerized at the beauty of the bindings, and the concept that book binding could actually be considered an art form.

I’m not an arts and crafts type of person. I don’t knit or sew, embroider, build things out of wood, make things out of straw or glass or sculpt out of clay or rock. I did try jewelry making in San Francisco, but unless I create a forge and build a press in my kitchen, it’s not necessarily the type of craft one can pursue in an apartment. Frankly, I have little patience for most crafts.

But the concept of bookbinding was different. I started researching it and found several books at the library on the subject, as well as resources online. The more I researched, the more fascinated I became.

For instance, pages in a book are not just stacked and glued at the end. They are usually folded into groupings called signatures and most hard cover books consist of several of these signatures sewed together, usually through the use of tapes. You can actually see these groupings if you look closely at the spine of most of your books. The term itself was from a time when a small signature was placed at the bottom of the first page of the grouping to assist in the collation of the book.

Single Sheet Tunnel Book

As for the binding itself, there are so many varieties, that I’m still researching some of the more esoteric, such as the dos a dos, and the complicated star tunnel book. The ‘book’ above is a training exercise in folding and cutting (decent folds, lousy cuts), and is a single page tunnel book. The ones most familiar to us, which is the stack of pages and a cover, usually with writing, are known as codex, a word from ancient Roman times used to describe tablets joined together on edge. This style is not to be confused with pamphlet binding or album binding, though all three look similar.

Bookbinding is now usually referred to as book art, and some universities, including Washington University here in Missouri offer Fine Arts degrees in the book arts. One of the more well known artists who specializes in bookbinding is Richard Minsky, one of the guiding lights behind the Center for Book Arts in New York. His Bill of Rights exhibition is both an inspiration and intimidation for a newly interested practitioner of this old, old art.

However, I think I will pass on incorporating live explosives in any of my work, though the use of book art as message has definite appeal.

I don’t think it’s surprising that many of those who practice book arts also like to write, which adds to the personal appeal of this beautiful craft. At this site that covers ancient Japanese bookbinding techniques, the artist, Graeme, recounts his early introduction to hand bookbinding:

One evening my father came home from work and held something out to me. It looked a little like a book. On closer inspection, it turned out to be a school geography text book, bound in green cloth and with erratic gold lettering on the spine. Perhaps it had been in a traffic accident at the mobile library.

‘Lionel at the office did it at his book binding evening class. It’s not bad is it?’
I said, ‘Wouldn’t it be kindest to take it to a qualified librarian? He could give it a lethal injection and put it out of its misery?’ No, I didn’t really say that, what I said was, ‘Mmmm, yes. Mmmm.’

It was important to sound neutral. My father could be unpredictable, and any trace of enthusiasm in my voice might encourage him to take up book binding himself. Without warning, all my school text books might suddenly be transformed into green-bound grotesques like the one in my father’s hand. I was responsible for those school books – I might still be in detention when I was thirty.

As said earlier, my libraries have several books on book arts and bookbindings and I’ve checked most of them out, including an old one from turn of the century, when bookbinding was considered a useful skill to teach in schools. Another of the books focuses on increasing your own self-sufficiency by creating your own paper and books, including excellent demonstrations of some of the equipment used by bookbinders, which I’ll get into more at a later time.

One can spend a lot of money starting this hobby, but you can also start small, with a minimum of equipment such as an awl for punching holes in paper, tapestry needles, linen thread, greyboard for covers, a bone folder, used for folding pages, and, of course paper. Luckily the art store near where I live not only has bookbinding supplies, but it usually runs a special on paper every week. I’ve spent three days there this week picking through the bins to match end papers to signature sheets to cover papers, and then on to the fabric store to get complementary thread. I never get tired of going through the papers and fabrics. Or the satisfaction of creating something unique with my hands–something that’s not wired to the Net, or plugged into the wall.

Books aren’t just thrown together. You have to have a basic idea in mind, and then you carefully find the material to create the book. I currently have five book projects in the works, including a codex, two Japanese stab binding books, and two star tunnel books, one of which is going to feature some interesting and perhaps even hauntingly familiar photographs.

I am now in the midst of finishing my first significant work, a journal bound using the Japanese stab binding technique, one of my favorites, and consisting of several sheets of handmade ‘weed’ paper printed with photos, with five sheets of bond paper in-between each to act as blank journal pages. The weed paper is a light golden green with flecks of plant material, which does an amazing job with the photographs. The cover is a rich tomato red, nicely textured on one side, and flecked with gold silk threads on the other. I’ll use the textured side as the outside cover, and the flecked side for the end papers. All I need to do is find the right combination of gold/green threads for the binding and I’ll be finished.

One thing that makes this journal stand out is the last page contains instructions on how to remove the binding, take out the white bond journal paper, use it as pulp for new homemade paper, and then put the book back together again with the homemade paper sheets in addition to the existing photographic sheets. A journal in perpetuity, unless one wants to keep the writing; a statement about the ecology of bookbinding in addition to the beauty. Every book tells a story, and it isn’t always to be found in the writing.

This book is a present for a dear friend, for his 60th birthday (there, the cat’s out of the bag). It’s not an expensive gift nor a glamorous one, and it probably won’t even be all that polished, I imagine–I am new at this. But it is a gift from my hands and my heart.

Makings for Japanese Stab binding journal

Categories
Writing

Grammar God

Recovered from the Wayback Machine.

Today it got close to 80 degrees (it’s still 70, at 9pm at night), and this is only the beginning of April. So many plants blooming that the air is perpetually perfumed.

I took the grammar test. I hate to break it to the neighborhood but…

You are a GRAMMAR GOD!

If your mission in life is not already to
preserve the English tongue, it should be.
Congratulations and thank you!

How grammatically sound are you?
brought to you by Quizilla

Me smart. Me talk good. Me rite gould, two.

Categories
Writing

Apps behaving badly

I have had a strong writer’s block this last month, which has manifested itself as writing to the weblog. As contrary as this seems, what this means is that instead of focusing on the writing I need to do to make a living, I’ve been puttering around here. Unless ya’ll decide to chip in and pay me a salary, I must be more disciplined with my time.

Luckily, reviewing the O’Reilly books helped me get a better understanding of both my audience and the writing style I want to follow, something I’ve been having some trouble with recently. They’ve also confirmed my impression that there is a good audience for books on technical topics that are not directed at geeks.

Clay Shirky’s new essay has also confirmed my preferred audience. He uses the term situation software to describe the quickly built, purposed, not meant to scale applications that power most small organizations Internet (and not) software needs. One aspect of this, and a growing aspect at that, is that programming is seen more as a secondary skill, rather than the primary skill:

So with programming; though all the attention is going to outsourcing, there’s also a lot of downsourcing going on, the movement of programming from a job description to a more widely practiced skill. If by programmer we mean “people who write code” instead of “people who are paid to write code”, the number of programmers is going to go up, way up, by 2015, even though many of the people using perl and JavaScript and Flash don’t think of themselves as programmers

In my opinion, this started in the days when professionals were scarce and we could command big bucks. Tools allowing smaller organizations to do their own development suddenly started to get more popular, and as they became more accessible, more and more people thought to themselves, “Hey! I can do this!”

Though the programmer-as-secondary-skill market has been around for some time, it has been powered primarily by Visual Basic, ASP, Java Applets, and Access in the past. Now, though, we’re seeing strong movement towards Flash/ActionScript, PHP, and MySQL, especially MySQL. On this database Clay writes:

You can of course build these kind of features in other ways, but MySQL makes the job much easier, so much easier in fact that after MySQL, it becomes a different kind of job. There are complicated technical arguments for and against using MySQL vs. other databases, but none of those arguments matter anymore. For whatever reason, MySQL seems to be a core tool for this particular crop of new applications.

I agree.

As for scripting, the use of JavaScript continues to be popular, but sites aren’t building in the dependency on it they used to. There is much less use of DHTML, but I think that’s due to the influence of Flash. Unfortunately both have been and are still used improperly at times, which I’ll demonstrate later.

Returning to Clay’s situated software, one challenge with these niche or communal applications, especially those created by non-traditional programmers, is that they they don’t always take advantage of existing components to do some functions that overlap between applications. The reason is either because they have someone who wants to ‘try it out’ themselves (and though that’s comendable, I’d rather incorporate code that’s been tested by hundreds of users), or they don’t know about the concepts of reusable components, and that these types of scripts exist.

The main reason I recommend PHP for most web sites is that there are thousands of pre-built and thoroughly tested open source PHP components (or codelets if you prefer) on the Internet just free for the download. Not only that but there are forms generators and various other tools that do three-quarters of whatever you need doing for a site–including interface with MySQL.

There is no need to code a mail handler application, or hand write a form that uploads data to a MySQL database. You don’t have to create your own user management system, or worry about how to upload photos. The only problem you might have is choosing among all the variations of any of these codelets that are online.

(To find, Google on “PHP scripts” and be prepared to be overwhelmed.)

In addition to not making use of existing code, inexperienced web site developers can also get caught up in the ‘cool stuff’, and make some serious mistakes in fundamental site design. A demonstration of how this can happen can be found in the web sites for the two library systems I use to get all my books and movies.

The first site is for the St. Louis Public Library. It’s not particularly polished looking, or pretty; however, it works, and it works rather well. Key elements in the design of this site are: good clean use of web forms for catalog searching; easy to read results pages from the searches; a front page that directs new users directly to the information they’re most likely to want; and good navigation between the site pages. The page that covers all the branches is based on a graphic, but the library also lists all of the branches below using plain hypertext links.

The only point I have to pick on the site is that they don’t have a direct link to a person’s account from the main page. You have to go into Catalog to find the link to “My Account”. What this does is make a person more apt to bookmark the Catalog page than the Main page and doing so they’re not as likely to see new events the library is promoting (which could be more prominantly displayed, themselves). Main pages aren’t just for newbies–they should have something for everyone.

(Under no circumstances should a main page have a Flash demonstration that has a “skip this” button to click. Not unless the site is selling Flash. )

The other library system I use is the St. Louis County Library, which looks more polished than the city library system, but right on the first page, it has a major strike against it: a Java applet based navigational menu.

Never, ever, under any circumstances, whatsoever, do you use anything other than a hypertext link to handle site navigation. You do not use DHTML. You do not use Flash. You do not use JavaScript in anyway. You do not use Java Applets. Slap, slap, slap! Bad!

(I once wrote a tutorial on this, writing that site developers should never make the navigation hard to find or use, forcing the reader to wave their mouse over the page like a magic wand, hoping to uncover an actual working link. To prove the point, I coded the tutorial to use graphical buttons for navigation, but when the person’s mouse was over the button, I would use DHTML to move it before they could click on it. They’d have to chase the navigation buttons around the page and hope they could click it faster than the DHTML could move it. It was fun.)

Chances are with the County library, you probably don’t even see the Applet menu (it doesn’t work with most of my browsers), and the site does provide a text-based menu, but that just forces a person to have to go to another page immediately. This doesn’t even mention the havoc that a bad Applet or DHTML menu can have on the many different browsers that people use. As for accessibility issues–forget it.

If you must have a pretty, pretty for your navigation, incorporate it as a secondary page. Or use CSS and set the hover value to change the hypertext link font.

The site also has some other errors, including the hated “You should be using…” specific browser notices. I used these once a long time ago before slapping myself upside the head, reminding myself that I want people to visit, not go away until they’re properly equipped.

Other than these issues, the County library’s main page does have nice features, including prominant mention of special events, and highlighting services the institution wants people notice. As for the secondary pages, the library does have some very fancy search engines, as well as other interesting tools. The search results are very comprehensive, including providing thumbnails of the book (or other object), and availability at each branch. It also provides one click requesting of the item, which I frequently use. Additionally, you can filter results based on age or year of publication or any of a number of factors–something you don’t think about until you have it and then you go, ‘Wow. This is handy.”

It is a feature like this, handy but not essental that can make niche or community software, or Clay’s situated software, grow and grow unless scope is set and ruthlessly enforced. In fact, the two major factors that lead to escalating costs on any software project, big or small, are analysis paralysis (trying to meet all needs for all people for all time), and scope creep (“Ooo. That’s nice. But can we make it also do this and this and this…”)

Categories
Writing

Unbelievable

Recovered from the Wayback Machine.

Today it got close to 80 degrees (it’s still 70, at 9pm at night), and this is only the beginning of April. So many plants blooming that the air is perpetually perfumed.

I took the grammar test. I hate to break it to the neighborhood but…

You are a GRAMMAR GOD!

If your mission in life is not already to
preserve the English tongue, it should be.
Congratulations and thank you!

How grammatically sound are you?
brought to you by Quizilla

Me smart. Me talk good. Me rite gould, two.

See purty flower. Purty flower is good smelling.

area449.jpg

Categories
Books

Extreme O’Reilly

Last of the O’Reilly book review, and I’m going to cover three different brands: the traditional ‘animal’ books, the Missing Manual series, and the Head First series.

The RELAX NG book from the animal series is what you’d expect for one of these books. It is a comprehensive coverage of the topic, with relevant examples, lots of text, and few graphics. Animal books get to the point and are, for the most part, geared to the geeks – or the geek at heart.

This isn’t to say that the coverage of the topic is cryptic or difficult to follow, or dry. After all, I’ve written a few animal books myself and I hope my books don’t fit that description. But they aren’t fluffy books, and make little use of graphics as an aid to understanding. The aid in these books tends to be the examples.

The Head First series is completely the opposite, and about as far as you can get from the animal books. There is still comprehensive coverage of the material, but how it’s covered is completely different. If the animal books are text, the Head First books rely on graphics. A great deal of graphics.

I’ve looked at both members of the series, Head First Java and Head First EJB, and my initial reaction to the Java book, was lukewarm. Part of that can be that I’m used to more traditional computer books to learn a programming language; part of it could be that, like many people, I prefer learning programming languages by example.

The Head First into EJB book, though was different. EJB – Enterprise Java Beans – is a framework and a set of related behaviors, and the graphic nature of the book captured this very nicely. In fact, it was the first time I’ve ever enjoyed reading a book on EJBs. I didn’t think it was possible to be entertained by a book on EJBs, but this book did.

(I think what won me over was the two page behind the EJB scenes graphics on pages 8 and 9. Any book that make me laugh about EJB is some kind of miracle.)

It could be me, but I see a Head First book being better suited toa framework than a programming language; the former is hard to get your head around sometimes, but the latter is easily broken into sample code and with some text to explain what’s happening, you get what’s going on without having to rely on the pictures.

However, if you’re a heavily visual person, you’re going to like this series.

missing.gifThe last book is the Mac OS X Missing Manual (Panther Edition), and this book fits about right in the middle between the animal books and the Head First series, in the ratio between use of graphics and text.

These purpose of this series is to provide more comprehensive information about a specific product than usually comes with the manuals (if any manuals are even provided). Visually, the Missing Manual makes more use of graphics and graphical breaks in the text than the animal series, but far, far less use of graphics than the Head First series. This makes for a book that’s less intense than the animal books, and more comfortable to read, especially if you don’t see yourself as particularly ‘geek like’. Additionally, it is more business like than the Head First series, though again, that doesn’t mean that the writing is dull or uninteresting – it’s just not quite as otherwordly.

I found the Mac OS X one to be very helpful, and I discovered all sorts of new and intersting things about the Mac OS X environment that I hadn’t taken the time, previously, to learn. And since Mac OS X manuals are not what one would call particularly helpful, I can definitely recommend this book for new or intermediate Mac OS X users.

Now the question: Would I write a book in these series

Well, I have written books in the animal series, and would do so again. However, my emphasis lately has been directed more to the non-geeks than the geeks, and that’s not necessarily a good fit for an animal book.

I would not do a Head First book. I wouldn’t know how to do a Head First book. Having to incorporate all those graphics in and around the text, and having to find the appropriate graphics – it would drive me nuts. It would take a special person to do a Head First book.

I would be comfortable doing a Missing Manual style of book. It fits the direction I’m going, which is more towards the interested or engaged or adventurous person rather than intensely directed towards the geek.

You know: someone who drinks lattes rather than Mountain Dew.