Posted by marshall
Thu, 08 Jan 2009 07:43:00 GMT
When I bought my iPhone 3G last summer, I decided to simply set it up as a brand-new device, rather than attempt to upgrade my original iPhone to the 2.0 firmware and then restore to the new one. I didn't really need the call logs, I had used Syphone to save my SMS logs as PDF files, and everything else was synchronized. Or so I thought.
I forgot about Notes. Notes don't sync.
When the iPhone was first introduced, it suddenly made sense why Apple was adding the Notes feature to Mail in Leopard: it needed to be able to sync with the iPhone. When the iPhone was released and Notes didn't sync up at all, I found it somewhat inconvenient, but knew that in just a few months Leopard would be released and all would be well. But then Leopard was released, and still there was no synchronization. It's now been over a year, with a brand-new iPhone OS 2.0 platform with multiple updates, a brand-new iTunes, and several updates to Leopard, but still, no synchronization of Notes. It really is puzzling.
At any rate, there I was with my new iPhone 3G, and I'd already handed down my previous iPhone, and I suddenly realized that my notes were all missing. At the time, I simply wrote them off as gone and moved on. But recently I wanted some information that I remembered storing in Notes on the iPhone, and realized that I still had the backup sitting around from the old device. I just needed to find a way to extract the Notes database and convert its contents into a readable format.
Now, there are existing tools floating around that can extract databases from iPhone backups, but my quick search didn't turn up anything that specifically located the Notes database and converted it to individual files like I wanted. Perhaps there is such a thing somewhere, but I was somewhat inclined to just write it myself anyway, simply for the fun of learning a little more about iPhone internals and solving my own problem. It turned out to be fairly easy to do using the stock Ruby installation in Leopard, which already includes the RubyCocoa and SQLite libraries needed to read the backup files.
So here it is, in case anyone else finds such a thing useful: iPhone Notes Extractor.
Posted in Computing, Smartphones | no comments | no trackbacks
Posted by marshall
Thu, 20 Nov 2008 18:37:00 GMT
From Macworld's review of the BlackBerry Storm 9500:
And while we're on the subject of welcome features that users are clamoring for, let's not overlook (cue fanfare) cut-and-paste. BlackBerry has shown Apple how it's done, by using the same multi-touch technology used in the iPhone 3G. Here's how it works: you put one finger at the start of what you want to copy, and one finger at the end to highlight text; then press the Menu button to select 'cut' or 'copy'...RIM's solution doesn't work well enough for us because it is fiddly beyond belief ("using this would drive you mad," said one of our testers).
I can't tell if the phrase, "BlackBerry has shown Apple how it's done", is sarcasm or not. It seems to be written in complete seriousness, yet I can't see how it could be. It is this kind of thing that demonstrates precisely why Apple has not yet implemented copy and paste in the iPhone. It's not that they don't know what it is, or don't recognize the need for it. It's that, if they're going to implement it, they need a good implementation to begin with, and they haven't got one worked out yet. All the BlackBerry has done is provide a reference implementation of how not to do it...and there are plenty of those already.
Posted in Smartphones | no comments | no trackbacks
Posted by marshall
Mon, 17 Nov 2008 04:06:00 GMT
When I first heard, several months ago, that iPhone OS 2.0 supported hardware-accelerated 3D CSS transforms in WebKit, my first thought was, "CoverFlow could be implemented in Safari with this!" In fact, I fully expected such an implementation to arrive within weeks. Well, months went by, and no one actually wrote such a thing that I could find, so a couple of weeks ago I decided that I ought to.
Last weekend I actually sat down to write it, but first made one more cursory check to see if I'd missed anything. It turned out that, in the previous week, Charles Ying had posted his own work on implementing CoverFlow using 3D CSS transforms, and had even set up a CSS-VFX project on Google Code for continuing work on it.
The CSS-VFX example demonstrates touch events, canvas (for reflections), CSS animation, and rotating images in 3D space, using sample images from Flickr. It's well worth looking at if you're doing any work on iPhone-optimized web sites. And although 3D transforms are currently only available on iPhone OS, they will no doubt make it to WebKit on other platforms in the future, and perhaps even on other browser engines if the extensions make it into an official CSS spec someday.
It's also worth noting that the WebKit team has already implemented a -webkit-box-reflect style in the nightlies, though it hasn't yet made it to iPhone OS. When it does, the canvas code won't even be necessary; the iPhone will be able to do hardware-accelerated reflections in CSS.
Posted in Computing, Smartphones | no comments | no trackbacks
Posted by marshall
Tue, 17 Jun 2008 00:43:00 GMT
I'm back from WWDC, and it was a great week. The sessions were interesting, I had lots of good discussions with friends, and as usual, a bit of sightseeing was worked in as well. The conference itself was far better than last year's blend of dropped Leopard features and the "sweet" "Web 2.0" "app" "solution" for the iPhone. This year, we got solid information on the real iPhone SDK, Snow Leopard, and even some improvements for web apps.
For once the early buzz was fairly accurate, so my predictions for what was likely to appear turned out to be reasonably accurate as well. The things I thought would happen did, and the things I didn't expect (but nonetheless hoped for) were nowhere to be seen. And while there were a few small surprises, there weren't any really big shockers.
That being said, here are the results, broken down in the same way the predictions were...
Read more...
Posted in Musings, Computing, Smartphones | no comments | no trackbacks
Posted by marshall
Sun, 08 Jun 2008 05:41:00 GMT
There is almost always a surprise at Macworld and WWDC keynotes, and no one really knows going in just what's going to happen. There's no real point in trying to figure out ahead of time what sessions to attend at WWDC; the keynote frequently changes everything.
John Siracusa has been making bingo cards for the past couple of years, containing predictions what may or may not appear at the keynote. I never really played along, but I do have my own expections of what will happen. I'm usually wrong -- most spectacularly at Macworld 2007 (my list was similar to Gruber's) -- but even then it's fun to look back later and compare what I predicted with what actually happened.
So here they are, broken down by how confident I'm feeling.
Read more...
Posted in Musings, Computing, Smartphones | no comments | no trackbacks
Posted by marshall
Thu, 05 Jun 2008 22:48:00 GMT
TUAW is saying that WWDC next week will bring a build of Mac OS X 10.6, which "will not include any new significant features from 10.5; instead, Apple is focusing solely on 'stability and security.'"
Daring Fireball notes that the name for this release is rumored to be "Snow Leopard", and follows up with this comment:
"If you’ve ever wished that Apple would spend more time focusing on making existing parts of the OS work better rather than adding new features, this is going to be the release for you."
Count me in among those who have wished for something like this.
Read more...
Posted in Musings, Computing, Smartphones | no comments | no trackbacks
Posted by marshall
Sun, 26 Aug 2007 19:50:00 GMT
The web is a jungle. Most smartphones are swiss army knives. The iPhone is a machete.
I read yet another comment on a blog today that said something along the lines of: "I don't understand the iPhone craze. My phone can do so much more and I've had it on [insert carrier here] for a year."
The iPhone -- and most Apple products for that matter -- is not about bullet points. It's about solving problems well. If you want bullet points, the Nokia N95 has a fantastic set. GPS, 5 megapixel camera, media controls, and so much more. Microsoft's also very much a bullet point kind of company. But bullet points don't tell the whole story. Consider:
McDonald's hamburger
- Meat
- Buns
- Ketchup
- Mustard
- Onions
- Pickles
Outback steak
Wow, that burger sure has a lot more features! But I know which one I'd rather eat.
Posted in Smartphones
Posted by marshall
Tue, 10 Jul 2007 22:46:00 GMT
Well, it's been about a week and a half, and I think I'm faster on the iPhone keypad than I ever was on the E70 or the Treo. We all know about the drawbacks of not having keys you can feel, but I've found that there's an unexpected benefit: you don't have to apply any pressure to said keys. Once my thumbs got used to where the keys were, I started just brushing the screen for every character. The auto-correction takes care of the mis-touches.
This is not to say that I don't accidentally mistype words, or that the auto-correction always works. I still frequently use the backspace key. But I did that even with a physical keypad.
So the virtual keypad really is a non-issue for me. I find myself quite enjoying it. It really does need text selection, though.
Posted in Smartphones
Posted by marshall
Sat, 30 Jun 2007 22:56:00 GMT
Well, it's finally here. And yes, I waited in line at my local AT&T store (no Apple stores nearby, alas) to get one. There were two others in line when I arrived at 12:30 PM, but by the time the store opened the line was down the block and around the corner. Not a bad turnout for a little regional store. I ended up being the first one to actually get one in the store, since the people in front of me took a bit longer asking questions. While it doesn't look like Apple's having trouble keeping up with demand just yet, they did run out of the 8GB models while I was still there looking at accessories, so I'm glad I waited.
First impressions? It's everything I hoped it would be.
The things I missed most from my Treo were the hardware ringer switch and the threaded SMS view. The things I liked best about my Nokia E70 were the Safari browser engine, the wi-fi support, the 2MP camera, the multitasking, and a UI that didn't keep me constantly reaching for a stylus. The problem with both of those devices was stability and lack of memory. While the E70 wasn't anywhere near as infuriating as the Treo in terms of instability, it kept shutting down individual apps because it ran out of RAM, and it could only get through a few web pages before I started getting messages saying I had to close some apps (despite the browser being the only one open).
The iPhone has all of these advantages and none of the drawbacks...plus a wealth of other benefits. And the implementation is just a joy to use. The web browser is outstanding; it really does provide a desktop-class browsing experience. While the E70 had the same browsing engine, the text rendering and navigation is so much more pleasant on the iPhone. The e-mail really does support full HTML messages with no problem, and it synchronized the settings with my e-mail accounts on my MacBook Pro, so I didn't even have to set them up. The iPhone connects to my wi-fi network automatically, and even keeps per-access-point proxy settings. While it felt like other devices were playing at music, playing at e-mail, playing at web browsing, the iPhone feels like the real thing.
And then there's all the little touches. The visual cues like the rubber-banding when you scroll too far and the way photos shrink down into the trash when you delete them. The automatic disabling of the screen when you hold the phone up to your ear. The local recording and editing of your voicemail greeting before sending it to the service provider. The slide-your-finger-to-unlock system that is quick and easy yet makes it virtually impossible to accidentally answer a call while pulling out the phone (a common problem I faced with previous devices). It's truly a revolutionary user experience, both in the big concepts like multi-touch, and in the small details that make everything just a bit more enjoyable.
What I am the most pleased with, though, is the speed. My E70 had Google Maps, but in order to use it, I had to unlock the phone (press menu key, press star, unless it was already unlocked and I didn't notice the difference in the left menu title text, in which case I just re-locked it and have to do it again after a slight delay for the phone to catch up), then I had to arrow over to the Google Maps app, then I clicked. After 5-10 seconds during which it looked like the phone wasn't doing anything, the Google Maps intro screen would appear with a progress bar. Then I'd wait another 20-30 seconds for the app to load.
On the iPhone, though, it's a single swipe to unlock (or just a press of the Home key if I'm in another app), a single tap on Google Maps, and I'm instantly there. No load time. And this is with multiple pages loaded in Safari, an e-mail message in the middle of composition, and music playing in the background. Of course, the map images themselves take time to load, especially when not on wi-fi, but switching between applications is instantaneous and trouble-free.
Now, while it's true that the iPhone is all I hoped it would be, it isn't all that I hope it will be. I knew going in what to expect. I was already aware that there was no 3G (AT&T doesn't offer it around here anyway, so that doesn't bother me much, plus it apparently kills battery life). I already knew there were no included games. I already knew that the keypad takes some getting used to (and I don't think it will ever match the feel of the Treo's or the utility of the E70's, though I appreciate the way it adapts to the task at hand). I'd already heard and complained about Apple's ridiculous press release that they were "supporting third-party Web 2.0 applications" (heck, I write so-called "Web 2.0" apps for a living and I still think Apple's current public position is stupid). There's definitely room for improvement, and I have no doubts that improvements will come: one of the great benefits of the iPhone is that software updates will come out for existing models and be effortlessly installed via iTunes, and I expect that we'll soon be seeing third-party games available on iTunes as well -- though I'm guessing ScummVM won't be on the list. I also wouldn't be surprised if, once the UI conventions have been established, a real SDK is made available (WWDC 2008?).
But even though I'll enjoy improvements when they come, it does what I wanted it to do, and it does it extraordinarily well. It's a superb web browser. It's a solid e-mail client. It's great for text messaging. And it has some little bonus features like making phone calls and playing music and videos and stuff. I guess some people think those are important.
Kottke is right: we're in the future. But I still want a hovercar.
Posted in Smartphones
Posted by marshall
Thu, 23 Feb 2006 11:03:00 GMT
I was going to title this, "Palm OS is Dead, Long Live the 'Access Linux Platform'", but then I discovered that someone already used it. Ah well.
As expected, ACCESS has killed off Palm OS Cobalt, destroying all hopes that I once had of owning a Treo with an advanced Palm OS. But it turns out that what they're replacing it with inspires far more hope than Cobalt ever did. ACCESS has announced the ACCESS Linux Platform (ALP), which boasts the following among its many promised features:
- Full standard Linux kernel
- User interface library based on GTK+
- "MAX" application framework built from the ground up for smartphones
- Modular GStreamer media framework
- Embedded SQLite database engine
- ACCESS NetFront browser
- Messaging and telephony software from PalmSource
- Runs existing (well-written) Palm OS applications unchanged
This answers just about every complaint that I had about the Treo. The Linux-based OS means the Treo will finally gain desperately needed stability and full multitasking. The new designed-for-smartphone application framework means that the five-way navigator will no longer be a second-class input citizen, and the support for softkeys should eliminate the button confusion on the Treo (which, after spending some confusion-free time with S60 lately, I am attributing to the lack of a solid "Back" button). And full Bluetooth 2.0 support is being built in, right from the beginning.
On top of all these "fixes", the new platform further improves upon the many things I liked about the Treo. The compatibility with Palm OS applications means that a huge library of existing software will be immediately available, while the use of GTK+ for new applications will encourage Linux programmers to apply their existing knowledge to creating new software. I'm hoping that the implementation of the PalmSource messaging system means that the Treo's excellent SMS "chat" view will be carried over. And then there's the built-in media framework, the SQLite engine (same as is bundled with OS X), and the improved browser (NetFront is widely regarded as one of the best browsers available for handhelds). All in all, a very promising platform.
The trouble, of course, is that it's still just promised. They're saying it will be out around the end of the year -- I guess that's just the happenin' time for OS releases, with Leopard and Vista scheduled for release around then as well -- but even if they make that self-imposed deadline, Palm never showed much interest in Cobalt, and it remains to be seen if this new platform winds up in a future Treo. If it does, it's probably still two years away.
But oh...an ALP-based Treo with a GoForce, an internal antenna, a P990-style jog wheel, built-in wi-fi, and a 4 MP camera...it's all more than doable by that time. What a wonderful dream.
Posted in Smartphones
