REQ: Add 'Fit-width' or 'Fit-visible' view mode, in which the zoom level is automatically set based on the width of the _current_ page.

Question

Currently, the default zoom level when viewing a page of a PDF file is automatically calculated based on the width of the "widest" page of the document. This means that, if the document contains one page that is wider than the others or is in landscape orientation, then the default zoom, when viewing all the other narrower pages, is set in a way so that the page does not use the full width of the screen. This results in very poor experience, because the zoom level and the visible area of the page have to be constantly adjusted for each page. The latest update (at the time of writing) has added some extra view modes, but not the much needed 'Fit width' or 'Fit visible'.
Personally, I can find no reason valid enough to justify the lack of such a view mode. Automatically setting the zoom level based on the width of the current page so as to take advantage of the full width of the screen should be a must have feature for mobile devices, if not the default behavior. The current default behavior regarding the zoom level is pretty much useless, even on 8"/10" screens. There should be a view mode in which the full width of the screen is always used to display the document.
Examples of documents for which the Adobe Reader for Android provides a poor reading experience are:
documents which contain some of their pages in landscape orientation.
publications which, apart from the main content, also contain the full front and back cover in a single page (usually first page which is much wider than the content pages) or any other extra pages like cards or application forms (that are meant to be printed) which usually use an A4/Letter page size etc.
documents which have been cropped by external utilities or scripts so as to eliminate unneeded white margins (in some cases not all pages have the same width).
Please consider fixing the default behavior in future releases of the Reader for Android or add a 'Fit width' or 'Fit visible' view mode.
Thank you in advance.
Message was edited by: George Notaras
Improved descriptions of example documents.

Answer 1

To add to this, if you prefer you can separate your JavaScript from your JSF pages.
Add a folder (I named mine 'js') to your application's ViewController project's public_html folder.
Via JDeveloper, create a new JavaScript file inside your newly created folder and place your JavaScript functions inside it.
You can then 'load' the .js file using the method Shantala described, with the addition of an added 'source' property to the af:reference tag.
(This can also be a URI reference to a JavaScript file hosted on a web server)
<f:facet name="metaContainer">
  <af:resource source="/js/myJsFile.js" type="javascript"/>
</f:facet>The benefits of this 'split' are cleaner JSF page source and also code-highlighting and formatting within the .js file making finding and fixing bugs in your JavaScript much easier.
It appears however, that when using <af:resource> to load scripts, once the page has been submitted even once, the JavaScript is no longer available to the page. Which isn't very useful.
A solution is to use <trh:script>.
Add xmlns:trh="http://myfaces.apache.org/trinidad/html" to your <jsp:root> tag and install the library.
then in place of the above code use:
<f:facet name="metaContainer">
  <trh:script id="script1" source="/js/myJsFile.js"/>
</f:facet>Now after a page submit the JavaScript still functions.
Edited by: Matthew Carrigy on 12/08/2009 10:39