Newton Poetry

With Eckhart Köppen’s Newtpocalypse patch for the eMate complete, I thought I’d install it and see how it performs on my own Newton eMate.

First, though, I downloaded the new Classilla browser for OS 9. This variation of the old Mozilla browser is getting a lot of attention, and deservedly so. Development on iCab has ceased, and many of the Classic Mac browsers do a poor job of rendering modern web sites.

As a test, I used Classilla to navigate Köppen’s 40Mhz.org site, where he posts his Newton projects, and download the patch from Sourceforge.

It’s easy to install Köppen’s patch. In fact, it’s nothing more than a simple package installation with an automatic reset added at the end. You can either use the Classic Mac installation methods, using Newton Connection Utilities, or the modern NCX or various other OS X-based Newton apps.

I’m using Newton Connection Utilities on an iMac G3 running OS 9, and connecting with a serial-to-USB dongle.

First, download your specific patch file from Köppen’s 40Mhz.org site. As you see above, you’ll have a few options on which patch to download. In my case, I need the 73J186 version.

Above you see that my eMate is running Newton OS 2.1, version 737041. This is the part that’s going to change.

To install Köppen’s Patch 73J186, head to Newton Connection Utilities (on OS 9, or another package installer on OS X) and pick your patch version (above).

Your package installer will upload the patch to your Newton.

After the patch is done installing, your Newton will reset on its own.

After the restart, my eMate shows the Newton OS 2.1, version 73J186 (the same as the patch version) is installed and up to date.

That’s it. And so far, after running my eMate through a battery of high-powered tests (like turning it on and scribbling some notes), everything is hunky-dorey. Bring on 2010.

How did your patching process turn out?

Martin Hahn, developer of SBM Utilities for the Newton, has released the application (ZIP file) he uses to create registration codes for the app, essentially unlocking the app for all to use. Via Frank Gruendel at PDA Soft is hosting the file.

Hahn at Softwarebüro Müller has created many other packages for the Newton, including Icon Editor and Soup Transport.

[Via Newtontalk.]

After installing a new battery pack in my Newton eMate 300, I wondered about the pack’s abilities: how long did it take to charge? How could I find its exact charge capacity? How long would it take to discharge?

Thankfully, I found a super-useful application (thanks to Tony Kan) to find all this out: Frank Gruendel’s NewtTest.

NewtTest is an all-in-one information source for any Newton ever created, from the OMP to the MessagePad 2100. As Frank says:

NewtTest will only show tests that make sense on the particular machine it is running on (you won’t, for example, find the backlight test on an OMP). Hence it will look different on different Newton models.

Once you install NewtTest on your Newton, you have access to tons of great tidbits of data. From the most detailed, like the above screenshot under “System Info,” to a “Backlight” feature that simply lets you turn your backlight-capable Newton on or off.

For my own use, the “Battery” section showed my eMate’s capacity, temperature, and voltage. It also recognized the type of battery pack I installed as an Apple NiMH rechargeable pack. Gruendel’s attention to detail here is impressive, and much-appreciated.

Another benefit is the “Clock” feature. If you’ve ever had to reset your Newton’s clock (on OS 1.x models) or calendar date (on any Newton), you know how frustrating it is.

NewtTest makes it simple by letting you pick the year first (above) and then worry about the date. Since my eMate was constantly running out of juice, I spent a lot of wasted time resetting the date by scrolling through the months and years (usually starting with 1997). NewtTest’s “Clock” feature becomes a big time saver.

Other “Test Types” in NewtTest, like testing the sounds on your Newton (cuckoo!) and calibrating the digitizer, are so helpful I wonder how I’ve lived without them.

For instance, my eMate’s screen shows a few faded or missing pixels on the right-hand side of the screen. With NewtTest’s “LCD Display” test, I can show a fully black screen, or a series of horizontal lines. It turns out that my eMate has a vertical line of faded pixels running the entire length of the screen. That’s not good news, but it’s worth knowing.

Gruendel has developed a few other applications for the Newton, but NewtTest is so practical that no MessagePad or eMate user should be without it.

Steven Frank, at his stevenf.com blog, has been thinking about what could possible replace the desktop metaphor that XEROX and Apple helped to pioneer.

Besides the desktop paradigm, Frank describes the pros and cons of other computing models – like the Newton’s soup-based data model and the iPhone’s multi-touch platform.

The Newton’s model had benefits, Frank says, but crumbled under the weight of OS-to-OS translations:

The Newton’s object store was an engineering marvel that fell apart as soon as you needed to exchange data with the outside world. You couldn’t just take a text file and send it over to your Newton because the Newton didn’t understand the concept of “file”. Your text first had to go through a conversion (via Newton Connection Utility) into an object format that some Newton application (in this case, probably Notes) could handle. Then you’d have the reverse problem going the other way.

Because desktop apps and Newton apps would never offer exactly the same feature set, inevitably these conversions result in loss of some information. Nitty-gritty things like precise formatting, metadata, and so on are the first things out the window when you need to convert data between two formats. It leaves you with a “lowest common denominator” form of information exchange that’s more frustrating than just being able to send files around. But in order to “just send files around”, you’d have to jettison all your radical (and useful) innovations and go back to square one: the good old hierarchical file system.

It’s a heckuva read, even if Frank offers no clear solution to what will come (web apps? Spotlight?) after the desktop metaphor has outlived its usefulness.

John Gruber at Daring Fireball has mentioned this before, but what I like about the Newton OS is that everything is automatically saved for you. When you scribble out a new note, you never have to press a “save” button. The only action you take with a note, after you’ve finished it, is to move it into some sort of organizational file system. But that’s optional. If you don’t want to move it, you don’t have to; you can shut off your Newton and the note stays right where you left it.

It’s like the Notes app on the iPhone, or the Stickies app on the Mac. Everything is automatically saved to some arcane folder deep in the Mac Library system.

What do you think? What’s the best possible platform to inherit the desktop’s dominance in computing?

Mike Levins on his favorite programming language:

I used to say it was 1992-era Dylan. Dylan was a Lisp that Apple invented. I worked for several years on Apple’s Newton project. Newton was initially written mostly in Dylan, and I got to write a lot of OS code in Dylan. That was a time of high joy in my programming life.

It didn’t last, of course. The story of Newton’s abandonment of Dylan and its other adventures makes entertaining reading, but the short of it is that eventually I had to stop programming in Dylan.

Turns out Dylan is still around, but Levins has moved on to a Lisp dialect called Clojure.

There are a few iPhone apps available that attempt to mimick Newton features, such as an updated PocketMoney and a few sketching applications.

The one that recently got my attention was WritePad by Phatware. WritePad is a free download, and offers the one Newton feature that the iPhone has been lacking so far: handwriting recognition (HWR). WritePad also offers cut and paste, a feature iPhone and iPod Touch users won’t experience until the 3.0 release this summer.

But how does it work?

Before we get into that, it’s worth noting that WritePad is a trial application. Phatware wants to test HWR on the touchscreen and is looking for feedback from WritePad users. That feedback will help develop the PhatNotes app. Hence the free download. Phatware also uses WritePad’s HWR engine to power other iPhone apps, like WritePad Events and WritePad Notes.

It’s basically a word processing program that lets you make and edit text files on your iPhone. The app includes a lengthy tutorial on how to use WritePad’s myriad features, like Auto Correct and user-defined dictionaries. There’s a lot to read and digest.

To start with, the logistics of “handwriting” on Apple’s new touchscreens are difficult. With only a few square inches to work with, and a thicker-than-a-stylus finger, your results will definitely vary. Accuracy is limited by the size of your scribbling, the size of your fingertip, and your handwriting style. And unlike the Newton, the iPhone’s relatively small screen size limits the length of your scribbles. WritePad employs a unique solution to the small screen size: you can overlap your letters in individual words. But is that even practical?

iTouch Tips give a great demonstration of the many features, like gestures and HWR options, and I’d recommend reading their post before digging in with WritePad’s options.

Without messing with the options or the tutorials, I went ahead and gave WritePad a test drive. Here are a few examples.

Given short, one-word scribbles, WritePad does a fair-enough job. I made a conscious effort to write neatly and cleanly on my iPhone, and WritePad’s HWR did the job just fine.

Given groups of complicated words, however, WritePad starts to fall apart. It reminds me of Newton 1.x’s brand of HWR: effective at times, but not nearly as good as 2.x.

I made several attempts at writing “Egg Freckles” in WritePad, and none of the translations came up accurate. In fact, the text got more garbled the more I tried.

WritePad does offer a “learn your handwriting” option, where possible words pop up to match your own scribbles. And supposedly, after a while, WritePad will learn your handwriting style. So part of it is patience, and part of it is giving the system time to adapt.

The only problem is, your words-per-minute speed will be miserable using WritePad’s HWR. With the keyboard, it logically gets better. Maybe an iPhone stylus would improve things, but I imagine few iPhone users will bother with a stylus.

It’s too bad that WritePad’s HWR is limited to in-app use. I imagine developers could find some use for system-wide HWR using WritePad’s method, but HWR is probably one of those “background” features that Apple doesn’t allow.

The other feature WritePad offers is copy/cut/paste, and this is done fairly well.

Here I write “Paste” using WritePad’s HWR (again, it does well at translating simple words).

WritePad translates the word (above). To copy the text, tap twice and drag across the word to highlight it.

WritePad offers cut, copy, and paste buttons at the bottom of the screen. To cut my “Paste” word, I just tap on the little scissors icon. To paste, simple tap on the clipboard icon, and WritePad pastes the word as many times as you tap. Clean and easy.

With the buttons, WritePad’s style of copy and paste differs both from the Newton and the upcoming iPhone 3.0 way of doing things. I can’t say if it’s better or worse because you can only copy and paste within the app. When you’re in WritePad, the copy and paste buttons are an automatic part of the UI. They work as advertised.

I had hoped that WritePad could act as a Newton-like Notepad application for the iPhone. Since you can open and save text files within WritePad, you can accumulate a hefty amount of notes. The Newton Notepad offered easy ways to organize your notes, however, which is something WritePad lacks. With WritePad, you have a list of text files with no apparent folder or file system to organize your notes.

If you want an easy way to edit and write text files on your iPhone, WritePad is a fine enough word processor – assuming you use the keyboard. But any hope for using HWR in an iPhone app effectively, especially one that replicates the Newton, is dashed when you start to write longer-form words or sentences on the smaller iPhone screen. WritePad’s HWR doesn’t seem practical enough for extended use.

A WritePad app on a larger-form iPod Touch or tablet, however? The possibilities of Newton-like performance start to grow. And to be fair, WritePad is a simple testing application that provides Phatware with enough user testing to implement WritePad’s HWR engine into a new, improved suite of apps.

So we’ll see how it works out. In the meantime, WritePad offers a bit of Newton-like functionality with the HWR, and a preview of cut/copy/paste that we’ll see later this summer. And hey – it’s free, which helps.

Former Apple developer Chris Christensen has a lot to say about the beginnings of Apple’s former online community, eWorld, and how it grew parallel to the Newton.

Apple’s eWorld was an America Online-like online hub that was created in the early days of the Internet. Since its creation, AOL has worked closely with Apple (ever wonder why iChat automatically uses AIM accounts?), including on NewtonMail. The relationship wasn’t always beneficial to both parties, says Christensen:

[AOL] also had two engineers on their side assigned to develop a new registration system that would be appropriate for the Newton. eWorld systems engineering resources also had to be redirected to NewtonMail instead of the eWorld launch to meet the NewtonMail schedule. Thus by doing my job of adding email to the Newton I helped slow down the eWorld launch.

Christensen goes into more detail about how missed deadlines and the growth of the World Wide Web spelled doom for the fledgling eWorld community.

AOL has since declined dramatically in popularity. It was the first Internet service I used, in 1995 or 1996, back when those annoying and wasteful CD-ROMs with the AOL start-up software were mailed to everyone in America. Remember those? They made great coasters.

It’s interesting that the development of eWorld and the Newton platform were from the same division at Apple, and running pretty much side-by-side before their launch.

For nostalgia’s sake, you can download eWorld’s sound files for your Newton, or have fun with an eWorld emulator.

[Via Newtontalk.]

Does the Newton’s 2010 bug got you down? Eckhart Köppen, the same Newton developer who created a Wiki on the 2010 bug, has issued a Y2010 Diagnostic application to help relieve some of the symptoms.

Köppen told the NewtonTalk list:

This small application lets you diagnose the content of your soups, and check which kind of alarms you have set. It should clarify what exactly might go wrong in the future instead of second guessing and brain wiping the Newton without proper reason…If you’re hit by an infinite alarm loop, you can if you’re lucky launch the Y2010 Diagnostic app and use it to clear the alarms.

Köppen suggests anyone who installed the problematic Fix2010 patch should remove it, and says that a fix to the whole issue should be out “well in time before 2010.”

[Thanks to NewtonTalk on Twitter.]

Sometimes it’s fun to see how the other guys do it. In this case, T-Mobile is offering a G1 simulator running Google’s Android operating system.

It’s really an Adobe Flash-based simulator, but it gives you a good feel for how the G1’s music player (above), contacts, and apps behave. Most of all, it’s neat to see how another touch-screen phone other than the iPhone operates.

Hopefully, Palm will do something similar when they release the Palm Pre.

Since my eMate 300 arrived at the end of last summer, I’ve struggled with ideas on how to use it. I bought mine mainly as a testing machine; my MessagePad 110 could only run Newton OS 1.x applications, and I wanted to experiment with more recent Newton apps. Also, eMates don’t have the portability and flexibility of their MP2x00 cousins.

So, what to do? It’s only recently, as I think back to the eMate’s original use (education, writing, word processing), that I’ve thought of a practical use for the little green machine: a journal writer.

I’ve been a writer as long as I can remember. As a kid, I used a typewriter to hammer out short stories. When I discovered the computer, it opened up a whole new world for me. I grew up to be editor of my high school and college newspaper, earned my degree in journalism, and went on to be a professional public relations writer. I live and breathe the written word.

A few years ago, I picked up journaling after a long hiatus. A plain notepad and pen have been the victims of random thoughts since I graduated college in 2003. After using a keyboard for so long, though, I notice my hand fatigues after only a few paragraphs. It’s no laughing matter.

I thought about using one of my Mac SEs as a journaling machine, just as an excuse to turn on of the little guys, but the SEs lack the true portability I was looking for. Laptops are fine – I have two iBooks – but finding excuses to use my classic Apple hardware was the goal. The eMate was just what I was looking for in a writing machine.

At home, the eMate works fine. But the rechargable battery is dead, and it’s not like a standard MessagePad with replaceable batteries. The eMate’s battery is wired in. So my next project is to find a usable eMate battery and replace my dead one.

When that happens, the eMate’s portability will be good enough to carry with me on vacations, trips to the coffeeshop, and even local performances or exhibits, where I can type down my thoughts. The smaller eMate keyboard will take some getting used to, but I’ve used it a few times already, and it’s not that big of a change.

In the meantime, I’m going to use Newton Works (with, perhaps, a few add-ons) to keep an electronic journal. I may search for other word processor apps, just to test the options, and implement a folder structure by year for organization. Now that I have Newton-to-OS X syncing down pat, I can even export my entries as text files – just in case any of them work as a blog post.

It’s hard to justify owning an eMate just for testing and projects alone. Over time, I can think about other uses for it other than journaling – like recipe-keeping (that old cliché) or even Twittering. Who knows?

All this will give me an excuse to poke around the Newton 2.0 interface a bit more, try out some apps, and goof around with my newest Newton. Stay tuned – the next Newton Poetry post could be typed out on an eMate keyboard.