As we are now weeks from the device getting to market I thought I would put down my thoughts on how well the ipad will do.

The ipad IS the new “ipod” and “iphone” , a trendsetting device which will first define and then dominate the category of handheld content consumption devices.

At 499 it is the perfect internet reading device . Yes it will bring the internet to everyone!. Just as we all stopped using our CD collection once we could carry our albeit lower quality mp3 collections around with us. We will stop using our laptops and computers to consume our internet content on the ipad and other similar devices.

Multitouch is the best thing to happen to UI since windows and the mouse. Anyone who has an iphone and the kindle realizes how much more intuitive it is to slide across the screen and touch something and see it respond. It does seem like Apple with its custom silicon and ipad screen will dominate the innovations around multitouch as it gets integrated into more and more apps that work on this bigger screen. The new avataar of of iphoto and Mail.app it seems are so revolutionary in their approach to UI, that ipad apps will become the new showcases for killer apps across all platforms.

Despite the fact that it does not give you the refresh free comfort of e-ink. The fact that it can do video and the web natively will ensure that e-ink and kindles etc move away from mainstream towards the hardcore reader market. The ipad will become the reader of choice for everyone. It will be wrong to call this the kindle-killer , but for everyone who has not already bought a kindle or reads less than one book a week , they will prefer the ipad.

The rebirth of the web-app. If you have ever saved a website as an icon on your iphone , or used a site specific browser like Fluid or others , you know how much sense it makes to consume a website as an App. The ipad will ensure that javascript and native web interfaces will get comeback as the chosen way of delivering functionality to users without suffering the control of the apple app store.

Perhaps contradictorily, the app store will retain its stranglehold over the iphone-ipad ecosystem. Just as everything from Yelp to Evernote to even gmail is now “just an app” for everyone. Teams of people will develop exclusive Apps for their portals , if they chose not to re-engineer their websites to feel native on the ipad screen. App development will now make more sense for everything from board games to radiology and imaging to photo-management and sharing.

If there ever was a non computer – web browsing device..this is it! It really will change the way we consume content, watch video , listen to podcasts , watch HULU , Boxee , read Ebooks , subscribe to podcasts, watch webcasts….you name it!. I believe the ipad is the next iphone and will be a worthy successor to the ipod and iphone as trendsetting devices that will be huge successes.

Its been almost three weeks since I released my maiden python-wxpython app. While Ive been busy doing other things , I decided to write this post to say how painful the “deployment” process of writing an application has been.
The most ironic fact is that the easiest platform to deploy for has ironically been Windows.
Once I used py2exe and innosetup I had a working setup.exe that installed the app on Windows Xp and Vista , 32 and 64 bit.
The next most fun platform to create a deplyment target for was linux. It was almost trivial to use the cxfreeze to create a binary build for Ubuntu Linux 32 bit and 64 bit . With the help of a Virtualbox VM for 64 bit SUSE, I could even release a binary build for that platform because someone asked.

But thats when the fun ended!. The mac has been an extremely painful platform to deploy python application for!.
I am using py2app to create standalone binaries. The idea is to have an app that I can click on and have it launch on any mac.
Some interesting hurdles:
1) If you create a standaone py2app build on Leopard it is not guaranteed to work on tiger
2) If you create one on Leopard it definitely does not work on snow leopard.

The only solution is to create a standalone app on tiger and then maybe it will work on Leopard.

In the end I did manage to solve my mac deployment issues which I detailed on this wiki page. Also Chris Lasher Lasher pointed me onto his series of links which talk about python deployment, Ian Bickings response is specially worth noting.

Its mainly thanks to c2cbio that I finally decided to sit down and start coding . Thanks to our many conversations about what makes a good programmer ,  version control , IDEs , test driven development and agile programming, I decided to try and put these into practice while I attempted to statisfy my code-itch.  Thanks to all the git topics from Atom , I too decided to start playing with git. The fun part was when I could see myself coding a lot more and writing code that even I reused. Another conversation had us talking about Living code , about how Paul Buchheit built gmail and add-sense  . The take home message for me was to prototype and test extensively, and release often .   All of these lessons combined with version control have ensured that I am few days away from a simple app that hopefully makes creating and keeping track of crystallization solution grids easier.

Thanks to the podcast I feel I get to keep up with the goings on, especially when bench work leaves me with little time to browse and catch up.

Thanks to everyone for listening and writing in  . Heres to podcasting , coding and hopefully a lot more episodes of c2cbio.

I have also been coding a lot lately and have gotten started with some GUI writing in wxpython.

This post is about trying to get back into the groove by telling you about argparse . Having talked about optparse and command line parsing , I heard about argparse thanks to a talk that I caught  by clicking a link on  the Pycon2009 master schedule .  This link has all the Pycon 2009 slides and video links in one place – a great resource.

For those interested in argparse check out the “Plenary Evening session ” on Sunday Mar 29th 1.20 pm at PyCon2009 where Steven Bethard talks about argparse.

The most important difference between argparse and optparse is that argparse provides better handling for positional arguments in addition to optional arguments . Argparse also provides automatically generated useage information and   takes care of handling cases like when the user forgets to provide any arguments and prints the help information by default.

The key differences are summarized in the excellent documentation at this URL , so I will not rehash it . But I have happily switched over to argparse from optparse and hope argparse becomes part of the python standard libraries soon.

For some code examples check out my github repository especially the script maskconvert.py