1. Field of the Invention
The present invention relates generally to an improved data processing system, and in particular to a method and apparatus for processing Web pages. Still more particularly, the present invention relates to a computer implemented method, apparatus, and computer usable program code for managing tab indexes in a Web page.
2. Description of the Related Art
The Internet is a global network of computers and networks joined together by means of gateways that handle data transfer and the conversion of messages from a protocol of the sending network to a protocol used by the receiving network. On the Internet, any computer may communicate with any other computer with information traveling over the Internet through a variety of languages, also referred to as protocols. The set of protocols used on the Internet is called Transmission Control Protocol/Internet Protocol (TCP/IP).
The Internet has revolutionized both communications and commerce, as well as being a source of both information and entertainment. For many users, email is a widely used format to communicate over the Internet. Additionally, the Internet is also used for real-time voice conversations.
With respect to transferring data over the Internet, the World Wide Web environment is used. This environment is also referred to simply as “the Web”. The Web is a mechanism used to access information on the Internet. In the Web environment, servers and clients effect data transactions using the hypertext transfer protocol (HTTP), a known protocol for handling the transfer of various data files, such as text files, graphic images, animation files, audio files, and video files.
On the Web, the information in various data files is formatted for presentation to a user by a standard page description language, the hypertext markup language (HTML). Documents using HTML are also referred to as Web pages. Web pages are connected to each other through links or hyperlinks. These links allow for a connection or link to other Web resources identified by a universal resource identifier (URI), such as a uniform resource locator (URL).
A browser is a program used to look at and interact with all of the information on the Web. A browser is able to display Web pages and to traverse links to other Web pages. Resources, such as Web pages, are retrieved by a browser, which is capable of submitting a request for the resource. This request typically includes an identifier, such as, for example, a URL. As used herein, a browser is an application used to navigate or view information or data in any distributed database, such as the Internet or the World Wide Web. A user may enter a domain name through a graphical user interface (GUI) for the browser to access a source of content. The domain name is automatically converted to an IP address by a domain name system (DNS), which is a service that translates the symbolic name entered by the user into an IP address by looking up the domain name in a database.
When navigating through a Web page, a user may scroll through and select components within the Web page, such as links, by using a pointing device, such as a mouse, a keyboard, or a trackball. Additionally, a user may move through different components in a Web page using a tab function. Web pages are often designed to allow for the setting of tab indexes for different components on a Web page. If the tab indexes are set, the user is able to use the tab function to sequentially move through different components from the beginning to the end of the Web page based on the order set by the designer of the Web page.
This type of feature is convenient for users to quickly move from link to link or field to field in a Web page. However, this type of feature may be annoying to a user who is attempting to focus on a particular field such as a login input field, by causing the user to tab through numerous other components, such as links, to reach the login input field.
The illustrative embodiments provide a computer implemented method, apparatus, and computer usable program code for managing tab indexes. A Web page is displayed, wherein the Web page includes a plurality of tab indexes for a plurality of components in the Web page. User input is received for setting a position for a tab index within the plurality of tab indexes for a component within the plurality of components in the Web page relative to positions of tab indexes for other components within the plurality of tab indexes in the Web page to form a desired position for the tab index. The desired position is stored for the tab index for the component to form stored tab index information. Subsequent visits to the Web page result in the tab index for the component being in the desired position using the stored tab index information.
The novel features believed characteristic of the invention are set forth in the appended claims. The invention itself, however, as well as a preferred mode of use, further objectives and advantages thereof, will best be understood by reference to the following detailed description of an illustrative embodiment when read in conjunction with the accompanying drawings, wherein:
With reference now to the figures and in particular with reference to
Computer 100 may be any suitable computer, such as an IBM® eServer™ computer or IntelliStation® computer, which are products of International Business Machines Corporation, located in Armonk, N.Y. Although the depicted representation shows a personal computer, other embodiments may be implemented in other types of data processing systems. For example, other embodiments may be implemented in a network computer. Computer 100 also preferably includes a graphical user interface (GUI) that may be implemented by means of systems software residing in computer readable media in operation within computer 100.
Next,
In the depicted example, data processing system 200 employs a hub architecture including a north bridge and memory controller hub (MCH) 202 and a south bridge and input/output (I/O) controller hub (ICH) 204. Processing unit 206, main memory 208, and graphics processor 210 are coupled to north bridge and memory controller hub 202. Processing unit 206 may contain one or more processors and even may be implemented using one or more heterogeneous processor systems. Graphics processor 210 may be coupled to the MCH through an accelerated graphics port (AGP), for example.
In the depicted example, local area network (LAN) adapter 212 is coupled to south bridge and I/O controller hub 204, audio adapter 216, keyboard and mouse adapter 220, modem 222, read only memory (ROM) 224, and universal serial bus (USB) and other communications ports 232. PCI/PCIe devices 234 are coupled to south bridge and I/O controller hub 204 through bus 238. Hard disk drive (HDD) 226 and CD-ROM drive 230 are coupled to south bridge and I/O controller hub 204 through bus 240.
PCI/PCIe devices may include, for example, Ethernet adapters, add-in cards, and PC cards for notebook computers. PCI uses a card bus controller, while PCIe does not. ROM 224 may be, for example, a flash binary input/output system (BIOS). Hard disk drive 226 and CD-ROM drive 230 may use, for example, an integrated drive electronics (IDE) or serial advanced technology attachment (SATA) interface. A super I/O (SIO) device 236 may be coupled to south bridge and I/O controller hub 204.
An operating system runs on processing unit 206. This operating system coordinates and controls various components within data processing system 200 in
Instructions for the operating system, the object-oriented programming system, and applications or programs are located on storage devices, such as hard disk drive 226. These instructions may be loaded into main memory 208 for execution by processing unit 206. The processes of the illustrative embodiments may be performed by processing unit 206 using computer implemented instructions, which may be located in a memory. An example of a memory is main memory 208, read only memory 224, or one or more peripheral devices.
The hardware shown in
The systems and components shown in
Other components shown in
The depicted examples in
The illustrative embodiments provide a computer implemented method, apparatus, and computer usable program code for managing tab indexes in a Web page. A Web page is displayed in which the Web page includes tab indexes for components within the Web page. User input is received, setting a position for a tab index for a particular component in the Web page. This position is set relative to the positions for other tab indexes for the other components in the Web page to form a desired position for the tab index. This desired position is stored to form a stored tab index.
Subsequent visits to the Web page result in a tab index being reached in the desired position using the stored position information. For example, a user may wish to set a login field for a Web page as the first tab index. In this manner, the tab index for the login field is changed to become the first component reached when the tab function is used. This tab information is stored. When the Web page is retrieved at a later time, the stored tab information is used to replace the tab information in the Web page to allow the user to reach the login field first when using a tab function.
Turning next to
In this example, browser 300 includes a user interface 302, which is a graphical user interface (GUI) that allows the user to interface or communicate with browser 300. This interface provides for selection of various functions through menus 304 and allows for navigation through navigation 306. For example, menus 304 may allow a user to perform various functions, such as saving a file, opening a new window, displaying a history, and entering a URL. Navigation 306 allows a user to navigate various pages and to select Web sites for viewing. For example, navigation 306 may allow a user to see a previous page or a subsequent page relative to the present page. Preferences such as those illustrated in
Communications 310 is the mechanism with which browser 300 receives documents and other resources from a network such as the Internet. Further, communications 310 is used to send or upload documents and resources onto a network. In the depicted example, communications 310 uses HTTP. Other protocols may be used depending on the implementation. Documents that are received by browser 300 are processed by language interpretation 312, which includes an HTML unit 314 and a JavaScript unit 316. Language interpretation 312 will process a document for presentation on graphical display 318. In particular, HTML statements are processed by HTML unit 314 for presentation while JavaScript statements are processed by JavaScript unit 316.
Graphical display 318 includes layout unit 320, rendering unit 322, and window management 324. These units are involved in presenting Web pages to a user based on results from language interpretation 312.
Browser 300 is presented as an example of a browser program in which illustrative embodiments may be embodied. Browser 300 is not meant to imply architectural limitations to the present invention. Presently available browsers may include additional functions not shown or may omit functions shown in browser 300. A browser may be any application that is used to search for and display content on a distributed data processing system. Browser 300 may be implemented using known browser applications, such as Netscape Navigator or Microsoft Internet Explorer. Netscape Navigator is available from Netscape Communications Corporation, while Microsoft Internet Explorer is available from Microsoft Corporation.
In these illustrative examples, the tab setting features in the illustrative embodiments may be implemented in language interpretation 312. In particular, the different features may be implemented using HTML unit 314. Alternatively, the different features may be implemented in part or in whole within plug-in 326. A plug-in is a program that interacts with a main application, such as browser 300. Typically, plug-ins add functionality to the main program.
In these examples, graphical user interface 302 serves to provide a dialog, such as a pop-up dialog, to allow the user to select an index number when the user desires to change the order in which components are reached when using a tab function. HTML unit 314 or plug-in 326 receives the information setting a tab position for a selected component through graphical user interface 302. This information is then stored in tab index information 328 in association with an identification of the Web page. As a result, when the Web page is subsequently retrieved, HTML unit 314 or plug-in 326 replaces the tab index information for the HTML component with the desired one in tab index information 328.
In particular, the user may click on the desired HTML component and select an option to select the tab index. This user input presents the pop-up dialog to set the tab index number for the component. The identification and name of the component of the tab index being set is stored in tab index information 328.
Turning now to
Window 400 illustrates a graphical user interface for a browser, such as browser 300 in
Turning now to
By setting a tab index of “1” using control 502 for name field 412 in
Turning now to
Turning now to
With reference now to
For example, if index number 806 is set equal to one, the component for entry 800 will be the first component reached when the tab function is used. When a Web page is again retrieved, the process changes the index number for this component in the Web page to one even though its index number may be some other number. The other components following this component are changed in position by increments of one. Of course, the tab settings for the other components could be reset in other ways depending on the particular implementation.
Turning now to
The process begins by receiving a user input selecting a component in the Web page for setting a tab index (step 900). Thereafter, a tab index dialog is displayed (step 902). In these examples, the dialog may be displayed using graphical user interface 302 in
Turning now to
The process begins by receiving a Web page (step 1000). A determination is then made as to whether tab index information is present for the Web page (step 1002). The determination in step 1002 may be made by using the universal resource locator for the Web page and determining whether the universal resource locator is present in an entry for the tab index information. If tab index information is present for the Web page, a component in the tab index information is selected (step 1004). In some cases, more than one component may be set for a Web page. Thereafter, each tab index number for the selected component is changed (step 1006).
Thereafter, a determination is made as to whether additional components are present in the tab index information that have not yet been processed (step 1008). If additional components are present the process returns to step 1004 to select another component. Otherwise, the tab index numbers for other components that were not present in the tab index information are adjusted (step 1010).
In these examples, components following a component that has been set to a new tab index based on the tab index information are adjusted by changing those tab index numbers, if present, by increments of one in these examples. If the other components do not have tab index numbers set for them, those components are reached in the order they are found in the HTML code in these examples. Of course, if two components are present in which tab index numbers are set, the subsequent component does not have its tab index number adjusted in this step. Thereafter, the Web page is displayed (step 1012) with the process terminating thereafter.
With reference again to step 1002, if tab index information is not present for the Web page, no changes are needed. As a result, the process then proceeds to step 1012 as described above.
The flowcharts and block diagrams in the different depicted embodiments illustrate the architecture, functionality, and operation of some possible implementations of apparatus, methods and computer program products. In this regard, each block in the flowcharts or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified function or functions. In some alternative implementations, the function or functions noted in the block may occur out of the order noted in the figures. For example, in some cases, two blocks shown in succession may be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved.
Thus, the illustrative embodiments provide a computer implemented method for managing tab indexes for a Web page. The Web page is displayed in which the Web page includes tab indexes for components in the Web page. User input is received setting the position for the tab index within the indexes relative to the positions of tab indexes for other components. This set position forms a desired position for the tab index. The desired position for the tab index is stored to form stored tab index information. Subsequent visits to the Web page result in the tab index for the component being in the desired position using the stored tab index information.
In this manner, users are able to more efficiently use a tab function to reach desired components in a Web page. With this feature, a user may set one or more components in a Web page in an order as desired to reduce the amount of tabbing that a user has to perform to reach these components.
The invention can take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment containing both hardware and software elements. In a preferred embodiment, the invention is implemented in software, which includes but is not limited to firmware, resident software, microcode, etc.
Furthermore, the invention can take the form of a computer program product accessible from a computer-usable or computer-readable medium providing program code for use by or in connection with a computer or any instruction execution system. For the purposes of this description, a computer-usable or computer-readable medium can be any tangible apparatus that can contain, store, communication, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.
The medium can be an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system (or apparatus or device). Examples of a computer-readable medium include a semiconductor or solid state memory, magnetic tape, a removable computer diskette, a random access memory (RAM), a read-only memory (ROM), a rigid magnetic disk and an optical disk. Current examples of optical disks include compact disk-read only memory (CD-ROM), compact disk-read/write (CD-R/W) and DVD.
A data processing system suitable for storing and/or executing program code will include at least one processor coupled directly or indirectly to memory elements through a system bus. The memory elements can include local memory employed during actual execution of the program code, bulk storage, and cache memories which provide temporary storage of at least some program code in order to reduce the number of times code must be retrieved from bulk storage during execution.
Input/output or I/O devices (including but not limited to keyboards, displays, pointing devices, etc.) can be coupled to the system either directly or through intervening I/O controllers.
Network adapters may also be coupled to the system to enable the data processing system to become coupled to other data processing systems or remote printers or storage devices through intervening private or public networks. Modems, cable modems and Ethernet cards are just a few of the currently available types of network adapters.
The description of the present invention has been presented for purposes of illustration and description, and is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art. The embodiment was chosen and described in order to best explain the principles of the invention, the practical application, and to enable others of ordinary skill in the art to understand the invention for various embodiments with various modifications as are suited to the particular use contemplated.
Number | Name | Date | Kind |
---|---|---|---|
5510811 | Tobey et al. | Apr 1996 | A |
5544299 | Wenstrand et al. | Aug 1996 | A |
5721897 | Rubinstein | Feb 1998 | A |
5796404 | Gentner | Aug 1998 | A |
5963205 | Sotomayor | Oct 1999 | A |
5999948 | Nelson et al. | Dec 1999 | A |
D427575 | Coleman | Jul 2000 | S |
6114978 | Hoag | Sep 2000 | A |
6229539 | Morcos et al. | May 2001 | B1 |
D453937 | Wasko et al. | Feb 2002 | S |
D461821 | Lindsay et al. | Aug 2002 | S |
6452611 | Gerba et al. | Sep 2002 | B1 |
6489976 | Patil et al. | Dec 2002 | B1 |
D469444 | Ording et al. | Jan 2003 | S |
6606106 | Mendenhall et al. | Aug 2003 | B1 |
6643824 | Bates et al. | Nov 2003 | B1 |
6654038 | Gajewska et al. | Nov 2003 | B1 |
6691155 | Gottfried | Feb 2004 | B2 |
D490440 | Ording et al. | May 2004 | S |
6850255 | Muschetto | Feb 2005 | B2 |
6874130 | Baweja et al. | Mar 2005 | B1 |
6918090 | Hesmer et al. | Jul 2005 | B2 |
7007281 | Gajewska et al. | Feb 2006 | B2 |
7111243 | Ballard et al. | Sep 2006 | B1 |
7134089 | Celik et al. | Nov 2006 | B2 |
7216298 | Ballard et al. | May 2007 | B1 |
7219304 | Kraenzel et al. | May 2007 | B1 |
7243309 | Koay et al. | Jul 2007 | B2 |
7263662 | Ballard et al. | Aug 2007 | B1 |
7263663 | Ballard et al. | Aug 2007 | B2 |
7379965 | Sherwood et al. | May 2008 | B2 |
7379977 | Walrath | May 2008 | B2 |
7437672 | Myers | Oct 2008 | B2 |
7568004 | Gottfried | Jul 2009 | B2 |
7603657 | Gassner et al. | Oct 2009 | B2 |
7620886 | Young | Nov 2009 | B1 |
7631278 | Miksovsky et al. | Dec 2009 | B2 |
7636897 | Koralski et al. | Dec 2009 | B2 |
7685234 | Gottfried | Mar 2010 | B2 |
7707505 | Ohrt et al. | Apr 2010 | B1 |
20030023670 | Walrath | Jan 2003 | A1 |
20030073064 | Riggs | Apr 2003 | A1 |
20030137538 | Hesmer et al. | Jul 2003 | A1 |
20030227487 | Hugh | Dec 2003 | A1 |
20040090463 | Celik et al. | May 2004 | A1 |
20040205497 | Alexander et al. | Oct 2004 | A1 |
20050015730 | Gunturi et al. | Jan 2005 | A1 |
20050039127 | Davis | Feb 2005 | A1 |
20050160065 | Seeman | Jul 2005 | A1 |
20050172237 | Cragun et al. | Aug 2005 | A1 |
20060117267 | Koralski et al. | Jun 2006 | A1 |
20060271861 | Yolleck et al. | Nov 2006 | A1 |
20070022367 | Ingrassia et al. | Jan 2007 | A1 |
20080120322 | Liu et al. | May 2008 | A1 |
20080201646 | Cragun et al. | Aug 2008 | A1 |
Number | Date | Country | |
---|---|---|---|
20080141162 A1 | Jun 2008 | US |