An Eclectic Mind

And why I might buy one anyway.

As an avid reader, I’ve been attracted to the idea of an ebook reader for years. But until this past autumn, I haven’t really found one I thought I’d actively use.

Before that were offerings from Sony, which seemed to fall far short of what I thought was a good design. The blinking page turns would drive me batty, since I knew I could go through an average page in 10-20 seconds. (Have I mentioned that I read very fast?)

Kindle came out and lots of people loved it, but I was turned off by Amazon.com’s aggressive marketing, limited format support, and high book prices. (Like many other book buyers, I don’t feel that an ebook’s cost should be anywhere near the cost of its printed version.) And when Amazon snatched purchased books off of Kindles without warning, I started wondering what other kind of access Amazon had and whether it would use it.

Enter, the Nook

Then Barnes and Noble introduced its Nook. Or at least it announced it. It seemed more in line with what I was looking for in size, cost (for the unit and books), features, and flexibility. I visited B&N stores regularly to get my hands on one and give it a try. No joy there. Even after November 30, when the units were supposed to be available for purchase, I could not seem to find one. And I certainly wasn’t going to buy one until I either read a lot of reviews about it or had some quality time with a demo unit. I did see a few reviews and they were, for the most part, positive. But I still wasn’t prepared to buy one until I could walk away from the store with it.

Christmas came. My husband decided to buy one for me. Of course, he couldn’t get his hands on one, either. But he ordered one online. They said it would ship in January. He asked for some kind of card he could give me on Christmas Day, in its place. They charged him $4 for a card that looked like a nook. And that’s what I opened on Christmas Day.

A few days later, he checked with B&N again to see when the Nook would arrive. They projected the end of January.

FAIL

An Apple Tablet?

This week, the Apple Tablet rumors have been in full swing. I’ve been wanting an Apple Tablet — or at least thinking I wanted an Apple Tablet; more on that in a moment — since last spring. I actually put off the purchase of a 13-inch MacBook Pro, hoping a Mac netbook would become available before then. Apple kept insisting they weren’t going to develop a netbook. I caved and bought the 13-inch MacBook Pro to replace a 15-inch MacBook Pro and the 12-inch PowerBook before it. (I still have both of those; anyone want to buy one?)

So here I sit, on January 6, expecting a Nook right around the same time that Apple might announce something infinitely better.

Or not.

The way I see it, Apple could do one of two things:

• It could announce an Apple Tablet that basically reinvents ebook readers and tablet computers at the same time. Kind of like what the iPod did for MP3 players years ago. Something that would blow all the existing options out of the water. Something not only I’d want, but everyone with a need (or desire) for mobile computing or an ebook reader would want.
• It could announce an Apple Tablet that, although attractive in its design and interface, falls short of what I need or want as an ebook reader or tablet computer. Or marry the device to a partner that I can’t do business with. This is what I thought about the iPhone and AT&T. I might have gone with the iPhone if I could choose my own carrier — without jailbreaking — but the AT&T partnership was a deal breaker for me.

An iPhone-like Situation

Indeed, my situation today has a lot in common with the iPhone announcement and release. Back then, I was in the market for my first smartphone. My Motorola flip phone was four years old (at least) and I wanted to tap into the basic computing power of a smart phone to store contact information, calendar events, and simple applications that would help me as a pilot (weather, flight planning, etc.). It was vital that the phone be able to communicate with my Macs to exchange information. When the iPhone came out, it looked like a dream come true.

Yet just days before people started lining up to buy iPhones, I bought my Palm Treo 700p. At the time, it was a better decision for me. Two years later, I updated to a Blackberry Storm. Again, it was better for me.

You see, unlike so many other people, I don’t buy the hot new gadget just because it’s a hot new gadget. I buy it because it meets my needs. The iPhone doesn’t meet my needs. I need a carrier with coverage in remote places. Verizon is that carrier. (Hell, AT&T can’t even get a good signal at my house.) I’m not interested in dropping $1.99 every few days or weeks on cool apps I don’t need or playing games on my phone. I’m not interested in being able to join wi-fi networks — in the very remote places I go, I consider myself lucky to have a cell signal at all. I need “tethering” to get my computer on the Internet via my cell phone’s Internet connection. The Treo and the Storm both support that through Verizon; I just learned that the iPhone still does not via AT&T. I’m not interested in jailbreaking a phone to add features that the maker and carrier don’t want me to have. I want a fully functioning, fully supported smartphone that does exactly what I need it to do, right out of the box. That’s why I don’t have an iPhone.

Now before you iPhone lovers get your panties in a bunch, just remember that I’m talking about my needs and wants. Not yours. Yes, your iPhone is very cool. Yes, I wish it met my needs. But although it might be perfect for you, it simply doesn’t meet my needs. I made my decision. Don’t waste your time and mine blasting me in Comments because I haven’t drunk the iPhone Kool-Aid and sacrificed my needs so I can be cool, too.

My Point

And that brings up one of two points in this post:

• Barnes & Noble failed when it introduced its Nook right before Christmas and didn’t have enough units on hand to sell to customers who wanted them. That failure was only made worse when the Apple Tablet rumors starting churning up again. Why would anyone buy now and wait until January month-end for a device when Apple, which is known for innovative, game-changing designs, could announce a competing product around the same time? Hell, if the Apple Tablet is the product I hope it is, I’d buy one even if I already had a Nook. But the Nook hasn’t arrived and B&N has just lost a sale.
• Although I’m huge Apple fan who has been using Macs since 1989, writing about them since 1990, and, indeed, earning a living as someone who teaches others about Apple products and software, I won’t buy an Apple Tablet if it doesn’t meet my needs. (Maybe it’s because I’d be buying it for me, and not to impress others with it. ) I’d like to think that there are other people like me who feel the same way. Don’t buy it just because it has an Apple logo on it. Buy it because it’s the best product to meet your needs.

It’s because I’m willing to wait and see what might be available soon that I’m in a good position to get what I want instead of compromising on features. I like immediate gratification as much as the next geek, but after buying so many gadgets over the years — heck, I still have a Newton MessagePad on the shelf! — I’ve learned not to rush out and buy what might be the next great thing. I’m willing to wait, at least until April or May, to make my ebook reader purchase.

Whether it’s an Apple Tablet or a Nook or something else that materializes between now and then remains to be seen.

But one thing’s for certain: it will be the right purchase decision for me.

Call Me a Geek, In Books books, computers, ebooks, iPad, iPhone, iPod, Mac OS, reading

Did you enjoy this post? If so, please comment on it or share a little link love:
 Add to Del.icio.us     Technorati This     Digg This     Stumble it!     Tweet This

One new photo a day.

About a year and a half ago, I discovered the Monotone theme for WordPress. Monotone is a unique theme in that it can “see” the colors in a photo, choose one, and use that color as a background. The results can be quite spectacular when used as a theme for a photo blog.

Indeed, the theme is designed for just that. It’s minimalistic and doesn’t even support WordPress widgets. It showcases the photo, which it protects from right-click saving, and offers room beneath it for a description. There’s also the usual post date, category, and tags, as well as big navigation buttons. Navigation can also be achieved by clicking the left or right side of the image.

Back in the summer of 2008, I put quite a few images online in a photo blog called Maria’s Pix that I created with Monotone. But then I discovered Zenfolio as a gallery/selling tool and simply stopped posting new photos. The site languished, unchanged, for over a year. It even became inaccessible as my ISP changed my DNS record and I didn’t update the subdomain to the new IP address.

But yesterday I decided to revive Maria’s Pix, partly as an experiment to see if I could do what so many photographers — amateur and professional — try to do: post a photo a day.

While updating the blog to prepare it for its re-unveiling, I discovered another theme by the same theme author, Duotone. Like Monotone, Duotone matches photo colors. But it goes a step further by taking a second color and using it as a page background, thus eliminating the unimpressive white background found in Monotone. I downloaded it, installed it, and activated it.

And found that it displayed PHP errors instead of photos.

Apparently there’s an incompatibility between Duotone and WordPress 2.9, which is the latest version (as I write this). While some folks more knowledgeable about PHP than I’ll ever be offered some hacks to fix the problem, the only thing the hacks did for me was remove the errors. The pictures did not appear.

I switched back to Monotone.

Eventually, Duotone will be fixed and I’ll begin using it. I like it because it supports widgets, so I can add a bit of other information under the photo. I believe it reads EXIF info, too, so I won’t have to manually insert photo info. We’ll see.

Until then, I hope you’ll visit Maria’s Pix — at least once in a while — to see a few of my better photos.

About the Photos, Call Me a Geek blogging, photography, WordPress

Did you enjoy this post? If so, please comment on it or share a little link love:
 Add to Del.icio.us     Technorati This     Digg This     Stumble it!     Tweet This

An overview of how I did it and the results.

This year, I decided that I needed an affordable yet memorable holiday gift to send out to all my customers and the folks I do business with. I wanted this gift to be an in-your-face-all-year-long item. That means it had to be something the recipients would want to keep and refer to.

A calendar seemed to fit the bill.

Now every year, I get sample calendars with my company name on it from various printers who print promotional items. They’re usually pretty boring; certainly not the kind of calendar you’d want to use all year long. Clearly, I had to do better than that.

The solution was a custom calendar using the photos I’ve taken over the years to show off the places I fly to and my helicopter. The challenge was to make a professional-looking, attractive calendar that was cost-effective to print.

iPhoto’s calendar printing option was the obvious choice for creating the calendar. It offers several different formats, many of which would meet my needs. What did not meet my needs, however, was the price: $19.99 per calendar. Since I figured I’d need at least 50 of them, that was far more than I wanted to spend.

My husband suggested MagCloud, which I’ve been using for other print-on-demand needs. At first, I didn’t think it would work out. After all, MagCloud produces stapled magazines sized just under 8-1/2 x 11. But then I held a sheet of paper up to the Robinson Helicopter calendar on my wall. And guess what? It was the same size.

So I decided to go with MagCloud for printing.

At that point, it looked as if I’d be creating a 28-page calendar from scratch. Not something I looked forward to. But I did a Google search for 2010 InDesign Calendar Template, which directed me to the 2010 InDesign Calendar Template by Juliana Halvorson on the Adobe Web site.

I downloaded it and discovered that it was almost what I needed. The template assumed a landscape orientation. I wasn’t sure if MagCloud would accept the document created that way. So I modified the template to make it portrait orientation and rotated all the calendar grids. A few adjustments to the margins and bleeds (which I initially got wrong) and it was a good starting point for my own project.

First up was reviewing the holidays. Juliana had included several extra religious and “Hallmark” holidays that just weren’t appropriate for a general use calendar. I removed them. I also changed the wording of some holidays — for example, changing Thanksgiving Day to just plain Thanksgiving.

Then I needed to redo the thumbnail calendars for the previous and next month that appear on each calendar page. The type was just too small. That turned out to be a time-consuming chore, as I had to basically reformat each little calendar individually. But it was worth the effort; the numbers are now far more readable.

Then the big task: finding the images I needed in my calendar — 12 full-page images and about 16 smaller ones — cropping them for the right proportions, saving them as TIFFs, and dragging them into my working file. It took me two full days to get the job done. In the end, it was very tedious and I just couldn’t wait to finish it.

Since the calendar’s pages had to be in multiples of 4, I had to stretch my 26 page document to 28 pages. That also meant filling in 2 more pages with something. I decided to put information about Flying M Air’s services, along with thumbnail images from the big pictures.

Once completed, I created the PDF MagCloud needed to print my calendar. The first upload (which took 4 tries on my miserably slow Internet connection here in Wickenburg) resulted in an error. I’d gotten the bleed measurements wrong. I fixed them and (fortunately) did not need to adjust the layout. Two hours later, after about 8 upload attempts, the file was online. The preview looked good.

I ordered the free proof and am now waiting for it to arrive. If it passes muster — and I’m about 95% sure it will — I’ll order about 50 copies to give as holiday gifts to clients and friends.

In the meantime, I’ve “published” the calendar so others can preview and (hopefully) buy their own copies. There is one caveat, however. Because MagCloud publishes magazines and not calendars, if you buy from MagCloud, you’ll have to punch your own hole in the top of the calendar.

I’ll be doing a lot of hole-punching next week.

About the Photos, Call Me a Geek, Flying business, helicopters, how to, photography, publishing

Did you enjoy this post? If so, please comment on it or share a little link love:
 Add to Del.icio.us     Technorati This     Digg This     Stumble it!     Tweet This

Reminding my brain not to block out the red underlines that indicate potential spelling problems.

Check Spelling as You Type has been a built-in feature of many word processors for years. It’s now in most applications I use — including my Web browsers, for Pete’s sake! — and the red squiggly or dotted underlines are an integral part of my writing life.

If you’re not sure what I’m talking about — do you live in a cave? — I’m referring to the feature that indicates when a word you’ve typed may have been spelled wrong. This is supposed to flag the word so you can check and, if necessary, correct it.

A Blessing…

I vaguely remember when this feature first appeared in Microsoft Word years ago. It was a blessing — and a curse.

I initially loved the feature because it often identified my typos. I’m a touch typist and can get up to 80 words per minute when I’m tuned in. But those aren’t always error-free words. Check Spelling as You Type was a great feature for finding typos as I worked, eliminating the need to run a spell check periodically or at the end of document creation.

As you might expect, it also found spelling errors. My spelling was always pretty good, so it usually found more typos than actual spelling mistakes. But that’s okay. An error is an error and I want to remove all of them from my work, whenever I can.

…and a Curse

But over the years, I’ve found some problems with the Check Spelling as You Type feature — and spelling checkers in general.

The feature does not identify all typos or spelling errors as errors. For example, suppose you type bit but you really meant but. A spelling checker doesn’t see any problem with that, so it won’t flag it. That means you can’t depend on a spelling checker to proofread your work. (And yes, in case you’re wondering, a grammar checker would likely identify this as a problem. As well as the sentence you’re reading right now, because it isn’t really a proper sentence. And this one, too.)

So you’ve got a feature that makes you lazy by doing about 90% of the proofreading work for you, as you type. If you neglect to do the other 10% of the proofreading work, you could be very embarrassed — especially if you write professionally and editors expect your work to be error-free.

The unflagged error that zaps me most often? Typing it’s instead of its. At least I know what it’s supposed to be.

It’s worse, however, for people who don’t know the correct word. How many times have you seen people use then instead of than? There instead of they’re or their?

The feature has degraded my spelling skills. In the old days, before spelling checkers, I simply knew how to spell. If I wasn’t sure of the spelling of a word I needed, I looked it up in — can you imagine? — a dictionary. It made it worthwhile for me to actually learn how to spell words. Knowing the proper spelling saved me time in the long run.

But now, I simply type the word as I think it might be spelled and wait to see if it’s flagged. If it is, I use a context menu — Control-click or right click the word — to choose the word I meant to type. Yes, it’s convenient. But I seem to be doing it an awful lot more than I used to use a dictionary.

(Perhaps it’s also expanding my vocabulary by making it easier to use words I’m not as familiar with? There’s something there.)

The feature identifies any word it does not know as a potential spelling error. That means that if your document is filled with jargon, technical terms, place names, or other words that do not appear in a dictionary, those words will be flagged as possible errors. The word unflagged, which appeared earlier in this post, was also flagged. Is it an error? Or does my spelling checker simply not recognize it? Seems like a word to me, so I let it go.

And herein lies my biggest problem: I’m so accustomed to seeing words flagged in my documents that I’ve managed to tune out the red underlines. (It’s kind of like the way we all tune out advertisements on Web pages these days.) This happened to me just the other day. I typed the word emmerse in a blog post. My offline editing tool flagged it with a red dotted underline — as it just did here. But for some reason, I didn’t see it. I published the post with the error in it. A friend of mine, who referred to himself as a “spelling Nazi,” e-mailed me to point out my error. I meant immerse, of course. He knew that. Readers likely knew that. But I got it wrong and I shouldn’t have. How embarrassing!

Here’s a look at the spelling check feature in ecto, my offline blog composition tool of choice. It works just like any other spelling checker. (And yes, I do compose in HTML mode.)

The correct way to go about this is to look for every single possible spelling error and resolve it so those red lines go away. That means learning or adding the unknown word so it’s never flagged again or ignoring it so it doesn’t bother you in this document. All of this should be done with the appropriate menu command. Simply telling your brain to ignore a problem just sets you up to be blind to it when it occurs. That’s not how the software was designed to work.

The Point

This post has a point — most of mine do — and here it is: spelling checkers, including any Check Spelling As You Type feature, are only as good as allow them to be. Use them, but don’t depend on them. Follow up on any flagged words and resolve them using the software so the red underlines go away.

Spelling checkers are just a tool. Like any other tool, it won’t help you if you don’t use it correctly.

Call Me a Geek, The Writing Life advice, editing, software, writing

Did you enjoy this post? If so, please comment on it or share a little link love:
 Add to Del.icio.us     Technorati This     Digg This     Stumble it!     Tweet This

Holy cow!

Yesterday, my Fifth Generation iPod — approximately equal to what they’re now calling an iPod Classic — the first version to support video — died again. I have a tendency to let the battery drain completely and sit in my purse like that. Then, when I attempt to sync, my Mac doesn’t know what the heck it’s connected to and wants to restore it.

This is the fifth time this has happened and the third time it has happened in the past two months. When I left for an appointment yesterday, it was still connected to my Mac, trying to import about 25GB of podcasts and music and videos. It was taking a long time, so I left it.

Coincidentally, that appointment was at the Biltmore Apple Store, which is walking distance from our “Rear Window” apartment in Phoenix. I was bringing in my 12″ PowerBook, which had a dead hard disk. I wanted to know what it would cost to replace the disk. I learned a few things:

• The 12″ PowerBook computer was first manufactured in early 2003.
• I bought mine in July 2003.
• On a 12″ PowerBook, you must remove 23 screws to get at and remove the hard disk. You then have to screw them all back in. In the right places.
• Apple has absolutely no interest in repairing 6-year-old laptops.

I’ll blog more about my solution to this another time. Let me get back to my new Nano.

Of course, I hadn’t bought it yet. But I figured that since I was there, I may as well take a look.

This isn’t my Nano, my thumb, or a video of anyone I know. But mine looks a lot like this one.

And I liked what I saw. So I bought a 16 GB red one. Yes, it’s (product)red, so a portion of the purchase price goes to fight AIDS in Africa. But that’s not why I picked red. I just like red. I’d like to help fight AIDS in Africa, but they’d get a lot less money from me if it was (product)turquoise.

Understand this: I bought a new iPod to replace one that simply wasn’t functioning reliably. The idea was to buy an iPod that would work with the iPod setup in my car and elsewhere. (The Shuffle won’t.)

I liked the idea of video, but since the video feature sucked battery power in my old iPod, I didn’t use it often. I didn’t expect to use it much on this iPod either.

All I wanted was something I could use to listen to podcasts and music while I drove or flew.

I got so much more.

This little sucker is absolutely packed with features.

• It plays MP3s and other audio format files.
• It plays movies.
• It has an FM radio tuner built in. The FM tuner can identify songs so you can tag them and later sync them with your computer for easy shopping on the iTunes Store.
• It has a video camera.
• It has a pedometer. It can sync up with Nike’s Web site for some reason I’m not clear about and probably wouldn’t care about if I did.
• It has games.
• It can tell when you tilt it so it orients the screen properly. This tilt thing can also be used by games.
• It can record voice memos.
• It can store and display photos.
• It can sync with Address Book and iCal on my Mac.
• It can store notes.

It does a huge amount of stuff I didn’t expect. And every time I find something new, I get all giddy, like a kid.

Playing with one of these silly things for the first time — as an owner — is better than opening presents at Christmas.

Now I know what you’re saying. “Maria, you work with Apple products all the time. Didn’t you know that the Nano had all these features?”

No, I didn’t. I mean I knew about the movies and heard about the built-in video camera. But the tilt thing and games and pedometer and radio were all quite a shock.

Maybe you’re saying, “Maria, how could you spend nearly $200 and not know what you’re getting?”

Well, I thought that what I thought I was getting was worth $200. The Nano comes in a really sleek little package. Weighs next to nothing. Incredible quality video for such a tiny screen. I was satisfied.

Now I’m beyond that.

Do all MP3 players have this many bells and whistles? What have I been missing?

As you might imagine, I’m very happy with my new purchase. The only adjustment I’ll need is limiting the data I put on it to less than 16 GB. My old iPod has a 30 GB hard disk in it; this is quite a step down.

But I’ll deal with it.

Call Me a Geek iPod, movies, music

Did you enjoy this post? If so, please comment on it or share a little link love:
 Add to Del.icio.us     Technorati This     Digg This     Stumble it!     Tweet This