Good News for PalmOS Fans

For a while it looked like Palm had turned its back on PalmOS, the operating system which had powered its PDAs and smartphones for year. And to a certain extent they have but the situation may not be as dire as die-hard PalmOS fans had thought.

With the latest version of webOS, version 2.0, Palm has removed the PalmOS ROM from the phone which is the actual code which the Classic PalmOS emulator uses to run PalmOS apps on webOS phones like the Palm Pre and Pixi. It was a serious enough problem that MotionApps, the company which makes Classic essentially threw in the towel and stopped selling Classic. But it turns out that with a little digging and command line hacking, that the PalmOS ROM can be installed on a phone with webOS 2.0.

Two interesting points come out of this development. One, longtime PalmOS users who have already purchased Classic will be able to continue using once they upgrade to webOS 2.0 devices like the Pre 2 or after their older devices are automatically upgraded to webOS 2. The other interesting point is that since the PalmOS ROM is clearly separate from the Classic emulator, then creating a PalmOS emulator for webOS might be a lot easier than people realize. Even if MotionApps stopped selling Classic, it should be possible for someone else (perhaps even Palm themselves) to create an emulator for PalmOS apps.

While I wouldn't expect to see a lot of PalmOS emulators coming out any time soon, it's an interesting thing to note that since Palm is putting out the PalmOS ROM themselves through their webOS Doctor software, it should help keep PalmOS die hards going while they search for webOS equivalents to their beloved PalmOS apps.

Google Reinvents Graffiti

Google has added a new feature to Android which looks a lot like an old feature from another mobile OS. Palm's old PalmOS PDAs had stylus-based input system called "Graffiti" where you would enter characters based on set of predefined pen strokes. It worked very well for years until the emergence of smartphones required Palm and Handspring to adopt keyboards for their devices. Add a long lawsuit by Xerox and Graffiti disappeared into the mists of gadget history.

Sort of. The idea of Graffiti remains popular enough that there is even a version available for iPhones. So it was probably only a matter of time before someone tried to bring it to Google's Android OS. That someone turned out to be Google itself which recently released a Gesture Search application which allows you to run searches by simply drawing letters. This is essentially what you did with the old PalmOS Graffiti.

But Gesture Search is a single standalone application while Graffiti was an essential part of the PalmOS and could be used with every PalmOS application. In fact even after Palm abandoned having a dedicated Graffiti input area for its Treo phones, it was still possible to install an app which would allow you to enter Graffiti strokes directly on the phone's screen.

That has gotten me to think about webOS on my Palm Pre. While there is a virtual keyboard available for webOS, there is nothing like Graffiti or even Gesture Search available for webOS. And that's disappointing because after all, Palm was the company which made this sort of input work in the first place.

And I think that Palm is uniquely suited to make it work again. Palm already has the code to Graffiti and Graffiti II—the successor to Graffiti which Palm introduced in part because of the Xerox lawsuit. And Palm has a its dashboard notification system which would be a convenient place to keep the controls for a Graffiti-style input system. So there really is no reason why Palm couldn't create another version of Graffiti and have it work on the entire operating system.

I used Graffiti for years on Palm PDAs. And I've used smartphone keyboards for years. But I was never really able to get used to using virtual keyboards which is one reason why I never got an iPhone. Now if I could have Palm's old Graffiti writing system back and have it live in my Palm Pre's dashboard, that would be a great alternative to sliding open my Pre when I only have to enter one or two characters.

Official Google Mobile Blog: Search your Android phone with written gestures

Classic—Bringing New Life to Some Old Apps

I checked the Palm Pre's App Catalog today and it had the same thirty applications that have been there for at least a week. Thirty apps. That's one ten thousandth the number of applications available for the iPhone and about one thousandth the number available for Android phones like the T-Mobile G1. But all is not lost for the Pre. One of the apps in Palm's App Catalog, is MotionApps' Classic PalmOS emulator. This app makes it fairly easy to run many of the thirty thousand apps available for older PalmOS devices on the Palm Pre.

But how easy is it to run PalmOS apps using Classic really? Since I've been a Palm user for over ten years, I was eager to learn. While the results are somewhat mixed, I've come to the conclusion that Classic is definitely a viable solution for Palm enthusiasts trying to convert to the Pre.

The Classic screen resembles that of a Treo smartphone—well, really it resembles the Palm Centro with its stacked, paired buttons and big d-pad. Unfortunately, Classic is locked into a 320x320 interface, using the rest of the screen for its virtual buttons. On the list of improvements that I want to see in Classic, being able to take advantage of the Pre's 480x320 screen is number one.

Number two is being able to copy and paste between other webOS applications. Classic handles copy and paste among applications that run inside it just fine. In fact in some ways it's even better than the implementation of copy and paste in webOS as a whole. But you can't for example cut a block of text from the PalmOS Memos app in Classic and paste it into the modern webOS Memos app.

Classic is also missing sound and codec support. This makes games somewhat less exciting and is a disappointing omission.

Classic also has problems with stability. It will sometimes throw up a Windows like BSoD which asks you to close the window and try again. Sometimes it will even crash the Palm Pre itself, causing it to reboot. Fortunately, these crashes are rare and have become even more rare since MotionApps updated Classic to version 1.0.2. MotionApps also has a separate Rom Update application which helps fix some bugs when it is installed inside Classic. We sometimes forget how unstable and cranky the PalmOS had become in its final years and some of these problems have definitely been carried over into Classic. But again, these problems are rare. Generally speaking most apps run faster and better under Classic than they ever did under the old PalmOS. MotionApps claims that PalmOS apps will run twice as fast under Classic as they would on a native PalmOS device and that seems about right. Everything in Classic seems to happen instantly and that is definitely a good thing.

While Classic does emulate an SD card treating its "ClassicApps" folder on your Pre as if it were an SD card, I've found that most of its crashes can be traced to a conflict between the app its trying to run and Classic's SD card emulation. It's much easier to "install" applications into Classic by putting them into a folder, appropriately named "Install" which Classic creates under its "ClassicApps" folder on your Pre. In the case of older applications which don't support loading from an SD card this is your only option for running them anyway. Also apps which consist of a .prc file with several .pdb data files tend to run better and more stable when they are installed instead of being run from Classic's virtual SD card. This causes a slight start up delay as Classic imports these files but the increased stability is absolutely worth it.

While Classic does not at this time support PalmOS Hotsync (MotionApps claims that it is looking into adding it in the future), it does support a Hotsync ID. This allows users to use software which they've bought and registered over the years without buying it again.

Importing PIM data is a little more involved than importing third party applications. MotionApps has fairly detailed instructions on how to do this but the gist is that you need to use a third party file manager like Filez on your PalmOS device to move the PIM databases to an SD card, copy them to your computer, and copy them again to the "Install" folder on your Pre. Once they are on your Pre, the Classic PIM apps look just like the PIM apps on any PalmOS device. If nothing else they are a good way of handling your imported data while waiting for better native Pre apps to come along.

Overall, Classic is a good way to ween PalmOS enthusiasts off their old apps while plugging some software holes in the Pre App Catalog. Buying Classic was fairly easy. I went to MotionApps' website and bought it and the next time I ran Classic it already knew that it had been registered. While this process is easy, it is interesting to note that the purchasing process for buying apps on Android is even more seemless—if you've ever bought anything through Google, the Android Market has your information and that makes purchases instantaneous.

Here are the applications which I've tried to run in Classic along with brief summary of the degree to which I succeeded:

AcidFreecell—Crashes when run from the ClassicApps folder. Generally stable (still occasionally crashes but not often) when installed into Install folder.

AtomSmash—Not compatible with Classic. Crashes under all circumstances.

Bejeweled!—Runs well in Classic.

BellTime—Runs well but without sound support, alarm clock apps are essentially useless.

BibleReader—This is a pretty good application for showing off Classic's strengths and weaknesses. It crashes when run from the ClassicApps folder and runs well when installed in the Install folder but it cannot see its databases unless they are also installed in the Install folder. Once everything is installed properly, BibleReader runs instantly in Classic—faster in fact than on any PalmOS device which I've ever used it with.

Bubblet—Runs well in Classic.

Converter—runs well in Classic.

D2RuneWords—Crashes when run from ClassicApps folder. Runs well when installed in Install folder.

DateBk5—Runs well when installed in Install folder but floating events require no longer "float" as they require Classic to remain running at all times.

Diddlebug—Runs well when installed in Install folder but requires more precision than is possible with the human finger.

Eat Watch—Runs well when installed in Install folder.

eReader—Runs but cannot see books unless they are installed in the Install folder.

FreeJongg—Runs but distorted graphics make the game unplayable.

HandyShopper—Runs well when installed together with its databases in Install folder.

JFile—Runs well when installed together with its databases in Install folder.

Keygen—Runs well.

Mass Transit—Runs well

Noah Pro—Runs well when installed together with its databases in Install folder.

PalmFiction—My favorite ebook reader on PalmOS runs very well under Classic, viewing books no matter where they are in Classic's directory structure. If only Classic supported 480x320 resolution.

PsMemo—Runs well.

SplashMoney—Runs well when installed together with its databases in Install folder.

T-Crisis—Runs well but virtual D-pad makes control difficult.

Thesaurus—Runs well when installed together with its databases in Install folder.

TopSecret—Runs well when installed together with its databases in Install folder.

WordPop!—Runs well.

USDA Foods—Runs well when installed together with its databases in Install folder.

Cut and Paste—webOS vs Classic PalmOS

One of the big albatrosses around the neck of the iPhone was it's lack of support, until recently, of copy and paste functions. So naturally Palm has trumpeted loudly that the new Palm Pre supports copy and paste from day one. And it does but there's a problem—actually two problems. Palm's copy and paste doesn't work everywhere and it doesn't work as well as it did under the older PalmOS operating system.

In order to copy and paste text in the Palm Pre's webOS, you tap to place the cursor at the beginning of the block of text you want to copy, hold down the shift key, and drag your finger horizontally to choose the text you intend to copy. Then you choose "Edit" from the drop down menu and select ." Palm has even created a little shortcut where you can tap and hold your finger in the gesture area and it acts like an unlabeled Menu key—the Pre will cut, copy, or paste whenever you press the "x," "c," or "v" keys on the keyboard. Pretty slick right? Actually, in the old PalmOS it was even easier to copy and paste. You could simply drag your finger across the text you wanted to copy and select "Cut," "Copy," or "Paste" from the edit menu which is even easier and more intuitive than with the Pre's webOS. In fact, I was so used to this way of doing things from my PalmOS devices that at first the webOS felt more awkward because I was trying to drag my finger across the text I wanted to copy when I was supposed to first place the cursor and drag my finger horizontally in the direction that I wanted the selction to move. This feels confusing and unintuitive, the older PalmOS way of doing things feels simpler to me.

Of course the older PalmOS was designed for PDAs and smartphones with different types of touchscreens than webOS. PalmOS was optimized for use with a stylus while webOS is designed for use with a finger. Could this be the reason for the Pre's Cut and Paste method? If only there were a way to compare these two methods side by side. There is—MotionApps' Classic emulator allows us to run PalmOS apps side by side with webOS apps. So I loaded the webOS Memos application and PsMemo within Classic. And it turns out that it's just as easy and intuitive to use the PalmOS Copy and Paste method in an emulated PalmOS app on my Palm Pre as it is on a Treo or a Palm TX.

I suppose that it doesn't make much difference one way or the other—the Palm Pre cuts, copies, and pastes just fine. It's just interesting how in the march of progress we sometimes take a tiny step back even as we move ahead.

One thing that does make a significant difference to me is the fact that webOS' copy and paste only works in text fields. As a result, you can't copy a block of text from your browser and paste it into a memo or anywhere else. The PalmOS web browser, primitive as it was, has always been able to do this and it should be simple to implement. Of course it this is so simple why did it take Apple, many times larger and richer than Palm, so long to implement it in the iPhone? Even Android, which is made by Google and had copy and paste on day one, took over a year to implement it in its browser. So perhaps I should cut Palm some slack.

Nevetheless, this does have a practical downside. I have secured my home wifi hotspot with a long 63-character wifi password. It's easy for me to put this key in a text file on a flash drive copy and paste it into any laptop that connects to my home network. It's also easy to put it into a memo and copy and paste it onto my Palm TX. With my T-Mobile G1 it was a little harder. First I had to find an Android application that could read text files and copy and paste. Once I had done that, it was easy to copy a text file to the G1 and copy and paste the wifi key.

With the Palm Pre it was even more of a challenge. While I had imported my old PIM data into Classic, including a memo with my wifi key; Classic sadly does not appear to support copying and pasting data between PalmOS and webOS applications. And neither does the Pre's built-in document viewer, the text file option was out. After trying several solutions, I concluded that the easiest solution was to email the wifi key to myself and open the email in my Palm Pre. But since the email application only displays the email I wasn't out of the woods yet. I had to tap reply in order to place the text of the email into a text field so I could copy and paste the key. Once I did that, I finally had access to my wifi hotspot on the Pre. That's not exactly what I'd call elegant.