Notebook Views Within Web Pages
Original Publication Date: 2000-May-01
Included in the Prior Art Database: 2003-Jun-19
Disclosed is solution for handling mega data found within web pages on the internet without scrolling through many form data entries, or without numerous communication with the server after each web page is submitted or loaded. A Notebook page view for a web page allows a concentration of data within a single web page, thus eliminating scrolling of previous data as is now the custom. All form data can now be displayed within pages of a notebook, and can be viewed by selecting the page containing the data, without scrolling the whole web page and losing the view of previous information, or, without submitting numerous pages to the server with the inputted information thus causing slow downs on the internet. Currently, many web pages on the internet contain form pages which require users to enter information. Due to size restrictions of terminals and browsers, much of this information being required encompasses more than the screen will allow at one time. The solution to this problem is to have a scrollable page, allowing all input to be entered on the one page by scrolling to the input fields, or by having multiple pages which allows input to the visible fields, then calling the next page to continue the input, thus causing server communication with the access to each new page. The problem this current approach presents is that in the scrollable page where data is entered by scrolling to the correct input field, is that the whole page scrolls by and data at the top of the page is removed from the screen as data is entered into fields on the bottom of the page. With the multiple pages of input scenario, as each page is completed and submitted with the input data, and the new pages for input are displayed, the server is accessed to receive and display each of these pages causing system delays and bottle necks with the overall internet system. This disclosure addresses these problems with the implementation of a notebook view and notebook pages. The problems mentioned above are solved first by eliminating the scrollable web page by allowing all form data to be displayed and entered within the pages of a user defined notebook. The pages contain all the input fields and are accessed by selecting the different pages where they reside. By utilizing this approach, all data being shown by the web page outside of the notebook bean, is still visible and scrolling, though still an option, is not needed to display all of the input fields. The second problem of communicating with the server as each new page is loaded is eliminated by the fact that each entry field selected and used within a notebook page is maintained much the same as it is with scrollable pages having much input data, and only supplied to the server once the complete web page is submitted, or by specifically sending the form data to the server by use of a push button, thus allowing the form data to be supplied to the server. Notebook views and notebook pages are not new to the user interface of software programs, however, they have not been used within web pages on the internet. To accomplish this, a Notebook bean would be used to control the notebook pages within the notebook. The Notebook view itself would have a binding specification, thus allowing a certain type of binding to be shown, as well as the position of the binding within the notebook. The three-dimensional effect is created by displaying the back pages of the notebook which shows the recessed edges of the pages. The location of this edge can also be specified by the user. Tabs, both major and minor are used to allow instant access to a particular page. Minor tabs are used within the realm of a major tab. Location of these tabs are determined by location of the major tabs, binding, and back pages. Text associated with the tabs are also by users control. The non-visible aspects of the Notebook bean is the control of the pages within and the form data being collected from these pages.