Thanks a lot to Swaroop for mentioning about Roorky on his blog post Interactive Python Book. Its interesting to see that there is a mixed feeling about the product.
One of the major motivation for coming up with iPUB is to reducing “Copy, Paste, Run and See” cycle is to just “Execute”. Whenever I am reading a programming book usually I copy the code seen in the eBook. Paste it in some code editor, run it and see the output. After few chapters/sections in the book this process becomes tedious and boring. Apart from that because of plain laziness not add additional files per snippet the original code snippet will be in horrible shape as lots things gets commented, changed etc., When reading a programming book I am just interested in seeing whether the code works or not? If I change something in the sample code listing how the output will change? Going through the phase is quite tedious many a times as all human beings do – I skip some of the experimentation. Later point of time I figure out things in hard way. :)
One of the things from my experience is that – “Easier you make try out the things, users will use those features more and experiment with it more”. Major motivation for iPUBs is to make trying out the contents of “programming books” a lot easier and less painful. The purpose was never to replace IDE and compete with it. iPUBReader will never become an IDE. But it will do everything to provide “Hassle free reading and experimentation experience” to its readers.
In the next post I will explain what are plans to improve the learning and sharing experience that lacks when you are reading an eBook.