Kindle Content Trumps eReader April 30th, 2009
Patrick Stein

Until the most recent releases of eReader, content was a close call between the Kindle app and eReader on the iPhone. Now, eReader dropped the ball, and Kindle scored on them.

What eReader Botched

Until the most recent release, eReader let you add books to your bookshelf from places like that provide free books in eReader format. I am hoping it was just an oversight when they wove in their own site a bit tighter. We shall see. It is obvious from the app reviews that the customers are annoyed.

The Kindle Advantage

You can download the free books mentioned above for the Kindle as well. You just have to jump through some hoops and re-upload them to Amazon before you can get them onto the Kindle app.

In addition to this, the new content available on Amazon is newer and cheaper than the content on the eReader site. It has always seemed wrong to pay full paperback prices for a book at eReader. eBooks for the Kindle seem to run between half and two thirds of the paperback prices.

Where To Go From Here

At the moment, I am stuck using both apps. I bought and got quite a few books in my eReader bookshelf, and it’s a better app anyway. But, there’s some newer, cheaper content at Amazon. And, now, if I want Project Gutenberg books or other free books, I’m going to have jump through Amazon’s hoops.


Four Ways eReader Beats Kindle on the iPhone April 29th, 2009
Patrick Stein

Reading electronic books on the iPhone may not be as easy on the eyes as reading it on a dedicated eBook or reading a paper book. But, c’mon. The iPhone fits in your pocket. Plus, you were already going to be carrying it anyway, right? The iPhone and eBooks were made for each other.

Here’s what eReader (v2.0.2) has over the Kindle app (v1.0).

Options, options, options

ereader-optionsIn eReader, you can tweak your font, your font size, your line spacing, your margins, and your justification. On the Kindle app, you can pick your font size, but you are stuck with their font, their line spacing, their margins, and their justification. Even worse, the insets and tables in the text will only display completely when you use the Kindle app’s smallest font size.

In eReader, you can lock the display in Portrait mode, Upside-down Portrait mode, Landscape mode with up on the left, or Landscape mode with up on the right. You can even let it track your orientation if you prefer. On the Kindle app, you’re in Portrait mode.

In eReader, you can choose to turn pages by swiping them horizontally, swiping them vertically, tapping left or right, or tapping high or low. In the Kindle app, you have to swipe horizontally to change pages. eReader’s tapping modes let you read easily with one hand. Trying to swipe pages with the thumb of the hand holding the iPhone is fraught with misfires—accidentally not turning the page, accidentally turning back a page instead of forward, dropping the phone, etc.

eReader also lets you choose your color scheme. The Kindle app locks you into black text on a white background. Actually, I feel like I once found an option to switch the Kindle app to white text on a black background, but I can’t find it today.


What’s the biggest advantage of eBooks over paper? They are electronic. Because they are electronic, you can fit two thousand of them in your pocket, you don’t have to kill any trees, and you can search for text in them. The Kindle app forgot about that last bit. I am sure there are indexes in the print versions of the Kindle books that I own. But, in the Kindle versions, there is no index and no way to search. The only navigation is page at a time or table of contents.

I have the King James Bible and the Constitution of the United States in eReader. Because of that, I can always zoom right to the spot someone’s talking about. When I’m trying to refer to something in one of the Kindle books, I end up guessing by chapter title, swiping, swiping, swiping, and scanning with my eyes to find the data I seek. Seriously?


I am reading along, reading along, reading along. All of the sudden, in the middle of the text, there it is: soliped. What is that? How did it get into this book?

In eReader, I tap on the word and it looks it up in my Pocket Oxford English Dictionary. The Kindle app makes me fumble for a paper dictionary, go search an online dictionary, or pretend I never saw the word.

Thumbed Bookshelf

ereader-bookshelfI have 42 eBooks in eReader. I have 3 eBooks in the Kindle app. In either app, I can sort by title or author. eReader adds separators in the display to mark off each starting letter. With that, I can find one of my 42 eReader titles as easily as I can find one of my 3 Kindle selections.

Hopefully the next version of the Kindle app will address some of these things.


Can We Refluidize CSS? April 28th, 2009
Patrick Stein

I mentioned earlier that CSS makes each object responsible for how it flows in the layout rather than making the container responsible. So, what can be done?

Take a look at this very site. All of the widgets on the left are floating over there. If you narrow your browser window (or bump up your text size), they will eventually fall into a single column. Narrow further and they will fall below this text.

That’s 80% of what I wanted out them. There are weird artifacts though caused by the different widget sizes. To accomplish this, I not only had to float each widget, but I had to float the main column as well.

What I really wanted was a container that would flow things for me instead making me flow each item (poorly). It seems I should be able to specify a container that adds objects top-to-bottom-then-left-to-right keeping the minimum needed height for any addition. So, in adding a <div> to this container it would:

  • insert it below the last inserted item if it need not lengthen itself to do so
  • otherwise, insert it to the right of the last items as high up as it will go if it need not widen itself to do so
  • otherwise, lengthen itself enough to place it below the rest of the contents

It may be as simple as preferred-width and -height attributes on the container, a flow-order: top-bottom-left-right;, and judicious use of maximum-width and -height.

Nobody’s Perfect

This wouldn’t solve every fluidity problem one might like to tackle. But, it would make many of them much simpler. No one would ever switch apartments if each piece of furniture got to say where it belongs on the moving truck.

New nklein Website April 28th, 2009
Patrick Stein

nklein software is launching a new website. This new website will allow for much more dynamic content.

I am currently transitioning old content over to the new framework. In the meantime, if you are having trouble finding something, you can poke around

The Fluidity-Thwarting Flaw in CSS April 28th, 2009
Patrick Stein

I am the one who decides how big to make my browser window. Web sites have a hard time coming to grips with that. There is a mythical minimum browser size.

When I am browsing, I don’t want to have to care.

When I am designing a site, I don’t want the user to have to care.

CSS is my enemy

All of the trouble using floats for columns all spring from a fundamental flaw in CSS:

How items flow with CSS is a property of the object instead of its container.

Now, maybe I am being a bit harsh in calling it a fundamental flaw. For all I know, it was a conscious choice. My guess though is that it seemed natural to people who wrote browsers in the early 90’s (<blink> tags and all).