Hi Jirka : > So I think Jirka should conclude the final decision and we should wait > > until his comments. > > I'm not sure what you are asking for now. >
In here, I'm asking from you to make a choice because of you are the one who came up with idea. But finally you give me the key to make a choice. I'm happy about it. In these two ideas, I can see some advantages and disadvantages; 1. Create new document packaging format (something like .epub) and special reader software for it. User will install this reader and then use it to open documents. 2. Package reader software with each documet. Users will just install document as application. In first choice, it may be a generic solution which can use for many different purposes. Also it has some extending capabilities. In a situation like, user want to read two documents which are related to each other simultaneously. So it is possible to implement special reader which can keep track on books(multiple tabs). Also user may not want to be confuse by installing many apps. I think, David is the better person to answer this (because he is engaging with stuff like this). But it may hard to implement. In second choice, it can be easy to implement. Because we embedded every things in building time. May possible to apply different policies on different documents. > > > I'm trying to get in to iOS development[1]. I registered in developer > site > > but unfortunately I can't download their developing tool because of it's > a > > big size of file. I hope to get into iOS soon. These days I'm busy with > > finishing my Android project[2]. After that I can accelarate my work. > Hope > > Jirka will help me to get though this idea. > > David, I think by adding iOS also into my work is enough to do over the > > summer hopefully. > > I don't think that developing native applications for two platforms is > very effective at this stage. > > If you want to cover more platforms, then you can choose completely > different route. Try to create something like WebHelp but with UI > suitable for smaller screens and then use PhoneGap to target multiple > platforms (http://phonegap.com/). > This is a nice idea. We can kill seven birds with one stone (not two). But one thing, I like to mention. It may be not possible to use native support like "speech recognition". I don't know more about "phonegap", so I need some time to understand its capabilities. As I know, Android becoming more popular than other smart phones. So, it is prefer to develop an application for Android with full of user friendly features with multi-tough and native supports. > > You should spend more time on researching possible ways to delivering > documents with good UX on small devices now. Not only thinking about > what can be done, but also looking to existing software like eBook > readers, mobile Web and PDF readers. Create lists of features missing in > those products and things that sucks. Then you can create list of > requirements for your application. After you have this, you should start > thinking about possible implementation strategies. > > As you mentioned above, It will be very good start to understand "webhelp". I followed its documentation partially, so I should finish it firstly. So it is good to use "phonegap" instead of developing for iOS. I like to develop application on "phonegap" and extend the output formats. I invite you to add some comments for developing an application with using native support of Android !. Jirka,David, Kasun and docbook devs; If you can give some ideas or any comments on this project, its highly appreciate. It will greatly help me to start my GSoC application !. Thank you !. -- Regards Gihan Chanuka Karunarathne Department of Computer Science and Engineering University of Moratuwa Sri Lanka Twitter: https://twitter.com/#!/gihanchanuka LinkedIn: http://lk.linkedin.com/pub/gihan-karunarathne/25/ba3/993
