Browse Prior Art Database

Document page moving basing on sub-divide pages

IP.com Disclosure Number: IPCOM000240122D
Publication Date: 2015-Jan-05
Document File: 7 page(s) / 88K

Publishing Venue

The IP.com Prior Art Database

Abstract

With the application development on mobile, more and more readings move to the mobile device, our disclosure focuses on the document in image copy type. It is common that if we zoom the whole pages to fit the size of the mobile screen, the characters would become too small to read; if we zoom the pages to suitable size to read, it would bring another problem that we need to take careful action to next section to reading. It is obvious that the type of actions would affect our reading efficiency. and user experience. Our disclosure impose that the reader would not take cautions on the section changes of the pages, it could easily be applied to all the reading application with better user experience.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 01 of 7

Document page moving basing on sub

Document page moving basing on sub-

With the application development on mobile, more and more readings move to the mobile device, our disclosure focuses on the document in image copy type. It is common that if we zoom the whole pages to fit the size of the mobile screen, the characters would become too small to read; if we zoom the pages to suitable size to read, it would bring another problem that we need to take careful action to next section to reading. It is obvious that the type of actions would affect our reading efficiency. and user experience. Our disclosure impose that the reader would not take cautions on the section changes of the pages, it could easily be applied to all the reading application with better user experience.


1. We should calculate how many sub part the page should be divided depending on current zoom scale.

We should fix the percents of the whole page held by the screen. The integer would be chosen for the document as the basic split number. The number of split might be not exactly a integer, we could tolerate with rounding up to an integer that the adjacent pages have overlap with each.


2. Adjust mechanism to get best fit.

To decrease the split times for a page and better user experience, we would provide a adjust mechanism. We assume that 5% size of the page would not affect the reading, we would also try the adjust scale range from 95% to 105%.


2.1 We would try to calculate the split number by decreasing the scale size as 95% to check whether we could reduce the number of dividing which means when we read a page we could save 1 slide here. If the tiny change for scale could help to decrease the slide times, we could get a proper scale number between 95% to 100%. If it could save the slip times, we would apply this new size.


2.2 If the overlap between pages is large comparing to each sub-page is high, we might try get a scale up for the page size within 5% but a premise that we should not increase the split times. We would calculate the scale up checking and overlap checking. If the number of slide does not increases and the overlap is greater than 5%, we would apply this new size.


2.3 To get a better reading experience, we assume 2% overlap is a better value. The function of overlap is to make sure the reading would know where should the start point. If the conditions above are triggered. The bound for the size should be 95% ~ 105%.


3. Fix the location for each split


After fixing the size of the page...