Hi Jirka : I'm very much glad to see the first reply from my mentor on "Extend output formats". And also thank you very much Jirka for paying attention about my doubts and give some explanations.
I went though your reply. But I found some ideas which are not fully clear to me. On Tue, Mar 27, 2012 at 2:07 PM, Jirka Kosek <ji...@kosek.cz> wrote: > On 26.3.2012 22:31, gihan karunarathne wrote: > > > I need to understand few thing about the project idea of "Extend support > > out put formats"[0]. > > First, I also need to clarify the idea which is in the idea page[1]; > > *“Output format packages” output by the DocBook style sheets would be > > easily consumable / installable by hosting applications.* > > What does it mean by "easily consumable / installable" ?. Can you > explain > > further ?. > > Sure, for example output for Android should be application which can be > installed as any other application. So that means, output Android application like some thing which is include the content of information which is given by user in xml. So, I'm going to create an application which include tools for easy access to the content (like search..). > Application will contain both simple application for browsing content and > content itself. > For an Android application, I should mostly focus on effectively use of display size and building more user friendly searching mechanism, index page etc.. > > > As I understood, the main goal of this project is generating an another > > type of formats file (ex:Android,iPad) by a XSLTProcessor. So, in order > to > > do that we want xsl style sheet which includes instructions and other > > directives that guide the processor in the production of the output > > document, right? > > Yes, but you will need also some postprocessing step which will take > resulting HTML/CSS/image files and pack them together into single > package, sometimes together with simple application for viewing content. > Do you mean that some thing like "webhelp" which use XHTML to generate the content from user then include index for built XHTML output and also include search. Do you mean some thing like that ? > > > My problem was, is it possible to run a apk which is not encrypted (as > like > > XHTML-xsl , webhelp-xsl ) and create the structure by using XSLT ?. > > I never developed Android application myself, but I bet that you can put > any additional resources into .apk including HTML/CSS/images. > I think, you got me wrong at this point. I told that, is it possible to make apk structure with out using "Android compiler". I think it is not possible. > > > Or do we have to create the common structure according to the Android > > source code and compile is using Android tools and embedded the DocBook > > documentation into apk application. Thus we can open it in Android. Also > we > > can use ANT to configure the procedure. > > What method should I do ? Is there any other successful way to do it ?. > > > > I also like to know, what should be the output of DocBook Android_xsl(a > > name that is made by me) should look like. I mean, what is final goal of > > this project look like. > > Output (in case of Android) should be tool (probably Java written, maybe > Ant build file will be sufficient) which takes as an input DocBook XML > document and proudces Android application which can be installed and > after it is installed it can be used for browsing original DocBook > document including features like collapsible table of contents, > searchable index and full-text searching. > I not afraid to tell that you are thinking about some thing like "webhelp", is it?. With some changes those should enhance the use of content. If I got some thing wrong, please correct me ?. I can send you a prototype of appearance of the application which I'm going to build, if you wish. 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
