Image via WikipediaAs it was noted in major publications several times already, NVidia made quite a mistake when they produced N84/N86 graphic cards with faulty parts. So when I became an early adopter and bought myself a Macbook Pro in July of 2007, I was also given one of these graphic cards and until now it's performance was nothing but breath taking. Unfortunately it appers that my usage patterns (probably a bit above-average carrying around, but not everyday) have finally brought it to it's knees and on Friday evening it died.
With my mind at rest about possible costs of repair I decided it was time to see how can I make the newest backup of the data on the hard drive. Since I could clearly see that my MBP successfully log-ins and connect to my home WI-FI network (broadcasting ping helped with that - ping -b 192.168.1.255), my first thought was that I should use SSH to log into the computer and then begin the painful process of copying somewhere around 100GB of data over 802.11G WI-FI and to the USB hard drive. But this didn't work because I have closed port 22 for SSH. For a laptop, that seemed quite reasonable at the time.
After discussing options like taking disk out and use converter for SATA/IDE-to-USB to plug it into other computer, mounting my MBP as target disk on my friend's Mac, etc., I was finally struck with divine inspiration - "If it can connect to WI-FI then obviously everything starts as normal, therefore I can just use Time Machine". The second I thought about it I was thinking to myself "how couldn't I thought of that before"?
Few minutes on and Time Machine was happily making backups.
So remember kids: Use backup and use a backup solution that can do EVERYTHING on itself with no buttons like "Yes, make me a backup".
Image by riccardodivirgilio via FlickrAfter playing around with my iPod Touch for a few days (didn't jailbreaked it yet though) I quickly came to the idea of reading PDFs on it - and as simple as that may sounds, it turns out it's not. Although you can sync quite a few things with your Mac, you can't sync PDFs.
At first I tried by just importing PDFs to iTunes, but you still can't copy them over to the iPod. Then I tried to save and view PDF as an image but although I was using pretty decent images, iPod still shrinks them down to 640x480 or something which makes them unreadable.
Two ways that I found to actualy work were mailing PDFs to myself and reading them in the Mail application or using Filemark Maker. Mailing PDFs would be acceptable, but it still feels a bit awkward to me personaly and I decided that for the time being I will be using Filemark Maker.
Basicaly what Filemark Maker does is that it uses data: URI scheme to encode PDFs as URLs which you can bookmark and - after syncing your bookmarks with your iPod Touch - open and read as if they were located localy on file system.
It works well with small files and until you bookmark a couple of PDFs - after that I noticed a bit of a lag (about 5-10 seconds) when starting Safari for the first time since restarting iPod. I suspect it caches bookmarks afterwards and all works well.
I am still wondering however why Apple decided not to support syncing of PDFs or giving iPod Touch and iPhone users some other way of storing PDFs and other formats that Safari/Mail support...
Source: FlickrWhen Apple held their press event for the announcment of SDK previous thursday I was watching closely what will come out of it - after all, there was a whole bunch of rumors and predictions about the direction that Apple could take and how it can either win the hearts of developers or burn in hell with it's platform by it's side.
As far as I'm concerned I think Apple more or less won my heart. Although I already downloaded[1] the iPhone SDK and installed it, I haven't yet programmed anything with it - one notable obsticle is that I am far more into web development and have almost no experiance whatsoever with Objective-C. But as I spend more and more time reading about Objective-C and watching various iPhone Application Framework videos of what can be done (and how) I am becoming a bit more confident to say that Apple's aproach is the right one.
Not only does a developer get a stable enviorment that Apple itself used to develop it's mobile version of OS X and has a lot of similarities with desktop/server version of OS X (this is one of those things that any Mac developer will appreciate because they can start programming without having to re-examinate yet another platform), they also get access to huge userbase that is accustomed to using iTunes and ready to pay for things they like.
App Store, the store which Apple will use to distribute software among users and give them a one-click-away solution for purchasing all software ever developed for the platform is what in my opinion distinguishes Apple's platform from other already developed and marketed solutions. It will be installed on iPhone and integrated into iTunes and therefore have a tremendous userbase - and it's userbase is what gives Apple an edge over it's competition. It is consisted of people that pay for their music, are a bit more tech-savvy than avarage population and will therefore appreciate the ease of use and user experiance that Apple will give to them. And gladly pay for the software that will be useful to them.
Business model used also seem rather fair to developers - if you want to charge for your applications you get to share 30% of your income with Apple and remaining 70% gets into your pocket. I find it a bit less friendly if you are prepared to give your application away for free - you will still have to get yourself iPhone Developer Program account that will cost you $99 per year - but I do not mind paying up those 99 bucks if they provide good enough value with their offical support.
Another very pleasing sight is how other software companies began stepping up their efforts for an emerging platform - my biggest surprise was Sun's announcement that they will develop Java for iPhone. I understand how they can develop it with the technology provided but I am very interested knowing how they will bypass various legal issues. Not that I mind if Java is developed for iPhone - on the contrary, I will be more than pleased to use a whole bunch of already developed Java applications.
How will all this come together in reality is yet to be seen in July when Apple will relase final version of SDK and give users second version of it's iPhone software that will include support for applications from 3rd party developers. I will however try to get familiar with Objective-C and start playing with SDK soon - and hopefully there will be a follow-up to this blog post in near future that will discuss my experiences with development itself.
[1] you need to have Apple Developer Connection account in order to download the SDK - free account will do