Currently, the premier authoring platform for EPUB ebooks is Adobe's InDesign. This is a huge validation of that format from Apple, and is a move I genuinely applaud, but that move to support that open format raises more questions than it answers.įirst is the issue of authoring tools. Apple has so far stated that the target format for iBooks will be EPUB. From what is known about the iBooks store at initial launch, it will be seeded with eBooks from several large publishing houses. We need a Safari simulator for iPad and we need it really soon. The User Agent from iPad's Safari also needs to be known so that so that web developers can make programmatic changes to our web sites to give iPad users an optimized website experience. While many websites will probably just "Work" with iPad, since the screen dimensions and resolution are closer to a Mac or a PC's native web browser than an iPhone, any number of UI and usability considerations are going to have to be examined for compatibility to make sure stuff isn't just broken or if various things need to be tweaked.
#APPLE IBOOKS AUTHOR EXPLOIT CODE#
This seems like either a glaring omission or that the Safari code for the SDK's simulator or for the final shipping device hasn't been baked yet. From what my colleagues who have been working with the iPad SDK tell me, the SDK is primarily for testing native applications which use the iPhone OS APIs in Objective C, not for testing the iPad simulator with websites.Īpparently the implementation of Safari which runs on iPad isn't part of the current iPad 3.2 SDK in the simulator. However, this SDK does not address what is perhaps the iPad's "Killer App" which is the viewing of content itself, meaning optimized websites and the eBooks that will run in the iBooks application on the device.įirst, lets tackle the issue of optimized websites.
0 kommentar(er)
