Source: http://www.google.com/patents/US20050172262?dq=7,249,099
Timestamp: 2016-02-10 11:34:18
Document Index: 21522456

Matched Legal Cases: ['art 505', 'art, 507', 'art, 607', 'art, 609', 'art, 705', 'art, 707']

Patent US20050172262 - Site menu - browser toolbar-based user interface for navigating web site pages - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inPatentsThe present invention generates a browser toolbar-based site navigation menu interface that appears uniform across different websites. A website developer can define and store the site menu contents in the web pages, root directory of the website, or a central repository. A central repository editor...http://www.google.com/patents/US20050172262?utm_source=gb-gplus-sharePatent US20050172262 - Site menu - browser toolbar-based user interface for navigating web site pagesAdvanced Patent SearchPublication numberUS20050172262 A1Publication typeApplicationApplication numberUS 10/769,003Publication dateAug 4, 2005Filing dateJan 30, 2004Priority dateJan 30, 2004Publication number10769003, 769003, US 2005/0172262 A1, US 2005/172262 A1, US 20050172262 A1, US 20050172262A1, US 2005172262 A1, US 2005172262A1, US-A1-20050172262, US-A1-2005172262, US2005/0172262A1, US2005/172262A1, US20050172262 A1, US20050172262A1, US2005172262 A1, US2005172262A1InventorsRajesh LalwaniOriginal AssigneeAhika CorporationExport CitationBiBTeX, EndNote, RefManPatent Citations (15), Referenced by (60), Classifications (13), Legal Events (1) External Links: USPTO, USPTO Assignment, EspacenetSite menu - browser toolbar-based user interface for navigating web site pages
DESCRIPTION OF PREFERRED EMBODIMENTS [0031] The present invention provides a ‘Site Menu’, which is a uniform Graphical User Interface (GUI) for Internet applications. The Site Menu interface is in the form of a menu inside the toolbar of a browser, the display of the menu being uniform in appearance for all web pages across all websites. However, the contents of the menu keep changing depending on the web page or website that is browsed. The menu allows a user to efficiently navigate a website. [0032] Menus provided on a web page are often positioned at various locations for different websites. Therefore, a user has to go through the inconvenience of finding the menu and getting used to the position, images, text, and format for each menu. The present invention overcomes these difficulties by presenting the user with a web page or website-specific menu that always appears on the toolbar. Moreover, the present invention offers the user menus that are uniform in appearance. Therefore, the user observes a familiar menu for all web pages across different websites. [0033] FIG. 1 illustrates an Internetworking environment where a system in accordance with the present invention can be implemented. The function provided by the system of present invention is embedded in a program called Toolbar Software 100. Toolbar Software 100 is a program that is installed and run by Web Services Client 101. Web Services Client 101 is a client, which uses Toolbar Software 100 of the present invention. The system, facilitating Toolbar Software 100 of the present invention, is hereby referred to as Site Menu System 107. All the system elements contained within Site Menu System 107 are explained with reference to FIG. 2. Herein, Site Menu System 107 is shown comprising a Web Services Server 201, a Central Repository 203, a Web-based UI Server 205, and a Central Repository Editor's PC 207. [0034] The inventive application preferably operates independently using the Site Menu System software program called Toolbar Software, which is installed and run by Web Services Client 101. [0035] Referring to FIG. 1, a Web Services Client 101 downloads a web page from a Web Server 109 over the Internet. The downloaded website or web page generally contains a navigating menu that is embedded into a Browser 103. In a preferred embodiment, Browser 103 is a Microsoft Windows Internet Explorer. However, the present invention should not be limited to Internet Explorer. Any other browser, including Mozilla or Netscape's Navigator, can be used. The navigating menu allows a user to navigate to various web pages within a website. Nevertheless, as mentioned earlier, this approach to navigate is at times confusing and time-consuming. Toolbar Software 100 of the present invention provides a user with a uniform Site Menu Toolbar 105 inside Browser 103. The menu displayed on Site Menu Toolbar 105, provided by Toolbar Software 100, is in addition to one or more menus that may have been provided within the displayed web page. [0036] Toolbar Software 100 is an intelligent software process that is initiated each time a web page is downloaded by Browser 103. This software process resides in the Personal Computer (PC) of Web Services Client 101 after Web Services Client 101 installs and runs Toolbar Software 100. Toolbar Software 100 searches for the menu contents of the downloaded web page in the documents related to the web page. The menu contents may be present either in the markup language document of the web page, in the root directory of the website of that web page, or in a database that is maintained by Site Menu System 107. Subsequent to searching for the required information, Toolbar Software 100 extracts menu contents for the web page. Toolbar Software 100 is also responsible for displaying these menu contents inside Site Menu Toolbar 105 of Web Services Client 101. It is also possible for Toolbar Software 100 to contain some standard menus in addition to the web page or website specific menus, for the purpose of display to the user. The standard menus may provide links that Web Services Client 101 may desire to access at any time during browsing. The standard menus are displayed inside Site Menu Toolbar 105 for all web pages and websites that are downloaded by Web Services Client 101. Toolbar Software 100 merges site-specific menu contents with the standard menu contents to present Web Services Client 101 with a single Site Menu Toolbar 105. An example of site specific menu contents and standard menu contents has been illustrated in the screenshot of FIG. 5. [0037] Site Menu Toolbar 105 is created using C++ as the programming language. However, the use of programming language should not be limited to C++. Other programming languages such as Visual Basic, C#, Java, or any other language, may be used. It is important to ensure that the programming language that is employed for the purpose of the present invention can use the Application Program Interface (API) that is supported by Browser 103. Once the menu contents are known, Toolbar Software 100 creates and presents the menu on Site Menu Toolbar 105. [0038] Information regarding the menu contents of a web page can be extracted by Toolbar Software 100 from various sources. Information obtained from some of the sources is stored in a database contained by Site Menu System 107. This database is referred herein as Central Repository 203. [0039] One of the possible sources from where information relating to the web pages of a website can be derived is Web server 109 of the website itself. In this case, first Toolbar Software 100 searches the HTML document of the Web page for a <Sitemenu> tag. However, the present invention should not be considered limited only to searching for the HTML documents. Other markup languages that are used for constructing Web pages, such as DHTML, XML, or any other language, may be used. The <Sitemenu> tag is an element in the markup language document of the web page which defines the contents of the menu within that web page. [0040] Another source within the website may be the root directory of the website. It is possible for a web administrator or developer to store a file in the root directory for their website. Wherein, this file, an XML file, defines menu contents for a web page within the website. [0041] In addition, Site Menu System 107 provides a user interface to the website administrator or developer to facilitate feeding of information about the menu contents of the web pages in that website to Central Repository 203. [0042] According to a preferred embodiment of the present invention, the website administrator or website developer can feed the information by uploading a sitemenu.xml file. An example of sitemenu.xml file has been illustrated in FIG. 8. [0043] In order to make sure that the person claiming to be the website administrator or the developer of a particular website has the proper authority to define the contents of the Site Menu for that website, an editor to Central Repository 203 may ask for the person's credentials. According to a preferred embodiment, the editor to Central Repository 203 provides a unique Site Menu ID which must be stored in a file called sitemenu_id.xml in the root directory of the website. The ability of the person to store a sitemenu_id.xml file in the root directory of the website provides the necessary proof that the person has the authority to define the contents of the website. [0044] Once the website administrator or developer uploads a sitemenu.xml file using the interface provided by Site Menu System 107, that file is stored in Central Repository 203. Here onwards, Site Menu System 107 is responsible for the generation and display of Site Menu Toolbar 105 corresponding to that particular website. Site Menu System 107 also defines the appearance and location of the menus on the Site Menu Toolbar 105 and its contents, that are specific to that website. Hence, a web administrator or developer is saved from the need to program the display of Site Menu Toolbar 105. This feature of Site Menu System 107 makes the system of the present invention easy to use for the website administrator or developer. [0045] However, it should be noted that the website administrator or developer creates the sitemenu.xml file. The sitemenu.xml file can be created, using any editor, such as XML Spy or Notepad, to generate and edit XML files. [0046] Another possible source for obtaining information relating to the menu contents of the web pages within a website can be within Site Menu System 107. Herein, one or more editors may be employed for generating menu contents for websites. An interface, similar to that provided for web administrators and developers, is provided to editors of Central Repository 203. This interface enables an editor to upload sitemenu.xml files forwebsites to a server that directs all such information to Central Repository 203. Hence, sitemenu.xml files that are uploaded by the editor are consequently stored in Central Repository 203. Site Menu System 107 also provides for a method wherein an editor, with proper access rights, creates the sitemenu.xml file for a web page within a website directly on the server. An editor is required to provide information for websites for which the <Sitemenu> tag or the sitemenu.xml file could not be found, in the markup language document, or in the root directory of the website. [0047] By and large, Site Menu System 107 acts as an Application Service Provider (ASP). Toolbar Software 100 is supported by Site Menu System 107 that obtains, manages, and provides menu content information for Web Services Client 101. By means of the ASP-based architecture of the system of the present invention, users are able to efficiently navigate through different websites. [0048] The functions provided by Site Menu System 107 are not limited to the display of Site Menu Toolbar 105 to users. As mentioned earlier, Site Menu System 107 also allows the website administrator or developer to conveniently create a menu for their website. Toolbar Software 100 is an intelligent program that can extract, interpret and display the menu contents of a web page within a website by merely searching for related data in that website or in Central Repository 203. [0049] As has been mentioned earlier, Site Menu System 107 comprises multiple elements, with each element being specific to a particular functionality. Referring again to FIG. 2, the functioning of Site Menu System 107 and its elements is described below. [0050] Site Menu System 107 consists of a Web Services Server 201 that supports Toolbar Software 100 for presentation of Site Menu Toolbar 105 in Browser 103. Also, Site Menu System 107 contains a Central Repository 203, which is a database that contains menu content information corresponding to the websites, and feeds this information to Web Services Server 201. Further, Site Menu System 107 contains a Web-based UI Server 205, which provides user interfaces to website administrators and Central Repository 203 editors, to facilitate their uploading information to Central Repository 203. Site Menu System 107 also contains one or more Central Repository Editor's PC 207, using which, Central Repository 203 editor creates and modifies menu content information. All of the above-mentioned elements are explained in detail hereafter. [0000] Web Services Server 201 [0051] Web Services Server 201 is responsible for providing an interface between Toolbar Software 100 and Central Repository 203. In other words, Web Services Server 201 carries out the function of a gateway. Broadly speaking, a gateway is a network point that acts as an entrance into another network. Therefore, Web Services Server 201 acts as a gateway for communication of information from Central Repository 203 to Toolbar Software 100. For the purpose of the present invention, the information is in the form of a sitemenu.xml file that is stored in Central Repository 203. Web Services Server 201 performs this operation on Central Repository 203 each time Web Services Client 101 downloads a web page and Toolbar Software 100 is unable to extract either <Sitemenu> tag, or the sitemenu.xml file from the root directory of that website. Web Services Server 201 then searches for the corresponding sitemenu.xml file for that web page in Central Repository 203. It is possible to enhance the performance by caching the information in Web Services Client 101, so that Toolbar Software 100 communicates with Web Services Server 201 only once a day for the same web page, or only when information about a website is stored in Central Repository 203. [0052] Programs residing in Web Services Server 201 provide Web Services Client 101 with the services of the present invention over the Internet. Web Services Server 201 has a client/server-programming model, wherein programs at Web Services Server 201 await and fulfill requests from client programs. In a preferred embodiment of the present invention, a client request is received each time a user at User PC 101 downloads a web page into Browser 103, and Toolbar Software 100 is unable to extract either the <Sitemenu> tag, or the sitemenu.xml file from the root directory of that website. In response to this request, Web Services Server 201 searches Central Repository 203 for that web page's corresponding sitemenu.xml file. Web Services Server 201 then communicates the information obtained from Central Repository 203 to Toolbar Software 100. As already mentioned, the sitemenu.xml file contains the <Sitemenu> tag. Wherein, the <Sitemenu> tag contains information regarding menu contents for the corresponding web page. Toolbar Software 100 utilizes this information contained in the <Sitemenu> tag to extract menu contents for displaying Site Menu Toolbar 105 inside Browser 103 for the Web page that is downloaded by the user. Optionally, the Web Services Server 201 may merge the standard toolbar contents with the web page-specific contents, and send the merged content containing a <Toolbar> tag to Toolbar Software 100. [0000] Central Repository 203 [0053] Central Repository 203 is a form of memory where sitemenu.xml files corresponding to several websites are stored. In other words, Central Repository 203 is a database of XML files from which Web Services Server 201 identifies a sitemenu.xml file corresponding to a requested Web page, to send the file to Toolbar Software 100. The mapping is performed, and a corresponding sitemenu.xml file is sent only if Toolbar Software 100 fails to locate either the <Sitemenu> tag in the markup language document, or the sitemenu.xml file of the web page. FIG. 8 illustrates an example of a sitemenu.xml file for a web page. [0054] The system of the present invention facilitates access to one or more persons to maintain Central Repository 203. These are called editors to Central Repository 203. Editors to Central Repository 203 can also upload sitemenu.xml files using Web-based UI Server 205. [0055] The menu contents information is fed to Central Repository 203 from all different sources, using web-based UI Server 205. [0000] Web-based UI Server 205 [0056] The chief purpose of Web-based UI Server 205 is to provide an interface for website administrators and developers, and editors to Central Repository 203, to upload information concerning the menu contents of the web pages within a website. The system of the present invention ensures proper authentication of the website administrator or developer to define the Site Menu contents for a website. The information concerning menu contents is in the form of a sitemenu.xml. In other words, Web-based UI Server 205 is a server that presents an interface for collecting information, and feeding and updating Central Repository 203 with that information. [0057] The interface provided by Web-based UI Server 205 is of significance to website developers and administrators who want to upload a sitemenu.xml file to Central Repository 203. This feature enables display of Site Menu Toolbar 105 in Browser 103 of Web Services Client 101 each time a web page within a website belonging to the web administrator or developer is downloaded. It is also possible for a website developer or administrator to modify or update an already existing sitemenu.xml file for their website, using the same interface provided by Web-based UI Server 205. This feature, provided by Site Menu System 107, also allows modification of web page-related information without the need for programming or re-programming of previously fed information. [0058] A similar interface is provided to an editor of Central Repository 203. Using this interface, an editor can upload sitemenu.xml files for several websites. The editor creates these sitemenu.xml files. The system of the present invention also facilitates the editor, with proper access rights, to create a sitemenu.xml file for a web page on Web-based UI Server 205. In the latter case, a sitemenu.xml file is directly created on Web-based UI Server 205 and fed to Central Repository 203. [0000] Central Repository Editor's PC 207 [0059] Site Menu System 107 editor, through Central Repository Editor's PC 207, provides menu content information in the form of sitemenu.xml files. The editor provides information corresponding to the websites and web pages for which the system of the present invention has been unable to collect any menu content information due to the absence of either the <Sitemenu> tag in an HTML document related to a website, or by input from the website administrator or developer for their website. The latter may occur in websites whose developers have not yet chosen to define a sitemenu.xml file either in their websites' root directory or in Central Repository 203, using Web-based UI Server 205. [0000] Process flow for the Site Menu [0060] The flow chart of FIG. 3 illustrates an exemplary flow of tasks and processes in the system in accordance with the present invention. At step 301, Toolbar Software 100 is initiated each time Web Services Client 101 downloads a new web page into Browser 103. Following step 301, at step 303, Toolbar Software 100 searches the HTML document related to the web page for a <Sitemenu> tag. As mentioned earlier, the <Sitemenu> tag lists all the details that define the contents of the menu corresponding to a web page. [0061] As soon as the <Sitemenu> tag is found, the system proceeds to step 311. However, in case no <Sitemenu> tag is found by Toolbar Software 100, then Toolbar Software 100 explores the root directory of the website for a sitemenu.xml file at step 305. The website administrator is responsible for creating the sitemenu.xml file and storing it at the root directory of its website. Once the file is found at this location, the system proceeds to step 311. However, if the search at this location is also ineffective, the system continues to step 307. At step 307, it looks for site menu information in the form of the sitemenu.xml file corresponding to the web page or website in Central Repository 203. [0062] In case steps 303, 305 and 307 are unable to yield the desired information, the system of the present invention proceeds to step 309. If at step 309, the system concludes that there is no information for generating contents for Site Menu Toolbar 105 that are specific to that web page within the website the system proceeds to step 313. At step 313, information regarding Site Menu contents is merged with the information regarding standard menu contents that are always presented to the user. In this case, since the web page-specific site menu information is not present, the system displays only standard menu contents at step 315. Toolbar Software 100 gets these standard buttons from Web Services Server 201. The contents of standard buttons usually remain uniform across all websites and web pages that are downloaded by Web Services Client 209, but can vary for each Web Services Client 209. [0063] On the other hand, if any of the searches carried out in steps 303, 305 and 307 present Toolbar Software 100 with the required information, then the system proceeds to step 311. Herein, at step 311, Toolbar Software 100 parses either the <Sitemenu> tag in the HTML document, or the <Sitemenu> tag in the sitemenu.xml file, to extract the menu contents. The menu contents extracted may be in the form of buttons, images, menu structures, sub-menu structures, or in any other form. At step 313, the Toolbar Software merges the web page or website specific contents if available, with the standard contents to create the contents for the entire toolbar containing the <Toolbar> tag. At step 315, Toolbar Software 100 uses the merged toolbar contents to create a uniform looking menu. This step is further explained in FIG. 4. [0064] In accordance with a preferred embodiment of the present invention, Site Menu Toolbar 105 is displayed in a format that is similar to the menu on Microsoft's Windows application. However, the present invention should not be considered limited to the format provided in Microsoft's Windows. Other formats that are widely in use or formats that are provided by other operating systems may be referenced. Additionally, it is possible to utilize images by including them inside Site Menu Toolbar 105 buttons or icons that are created by Toolbar Software 100 in accordance with an embodiment of the present invention. Images make Site Menu Toolbar 105 more attractive and user-friendly. At step 317, once Site Menu Toolbar 105 has been displayed, the user interacts with the menu to execute certain tasks. For instance, a user may click on a text or title presented, using buttons or icons inside Site Menu Toolbar 105, in order that the browser directs the user to a new web page or to execute a specific JavaScript. This action is performed preferably with the help of functions such as but not limited to a GetToolBar function. It is also possible that when a user clicks on a button inside Site Menu Toolbar 105, another menu is displayed. This is called a pop-up menu. According to a preferred embodiment of the present invention, functions such as, but not limited to, a ShowPopupMenu function are used to display the pop-up menu. [0065] FIG. 4 elucidates step 315 of FIG. 3. In step 315, the Site Menu Toolbar is displayed. According to step 401, Toolbar Software 100 first parses the merged XML file. The file is parsed in recursive, depth-first order. In step 403, Toolbar Software 100 traverses nodes in the XML file. If a <label> node is encountered, Toolbar Software 100 proceeds to step 405. At step 405, Toolbar Software 100 stores a command to create a caption in Site Menu Toolbar 105. From step 405, the process flows back to step 401. Hence, Toolbar Software 100 remains in a loop until all nodes have been traversed. In case the current node is not a <label> node, the process continues to step 407. At step 407, Toolbar Software 100 searches for a <Separator> node. If the <Separator> node is present, Toolbar Software 100 proceeds to step 409. At step 409, Toolbar Software 100 stores a command to create a separator corresponding to the separator found in the search in Site Menu Toolbar 105. Toolbar Software 100 uses the following to create a separator: [0066] TBBUTTON BtnData; [0067] BtnData.fsStyle=BTNS_SEP [0068] It is commonly known to a person skilled in the art that a data structure such as but not limited to TBBUTTON is used to carry the information about buttons in a menu. Additionally, fsStyle is used to define the button style. Herein, the button is a separator, and hence fsStyle is set to BTNS_SEP. [0069] Furthermore, from step 409, the process flows back to step 401. The process remains in this loop until all the nodes have been traversed. In case the current node is not a <Separator> node, the process flows to step 411. At step 411, Toolbar Software 100 conducts a search for <Menu> nodes. In case a <Menu> node is found, Toolbar Software 100 proceeds to step 413, where it parses all <Menu> or <MenuItem> children in a recursive, depth-first order. In this step, Toolbar Software 100 uses the structure such as but not limited to the following: [0070] TBBUTTON BtnData; BtnData.fsStyle|=BTNS_BUTTON; [0071] BtnData.fsStyle|=BTNS_WHOLEDROPDOWN [0072] In these structures, BTNS_BUTTON creates a standard button. Moreover, BTNS_WHOLEDROPDOWN specifies that the button will have a drop-down arrow. Proceeding further, at step 415, it fetches any images that may have been specified in the <Menu> or <Menultem> nodes. It may be appreciated by a person skilled in the art that functions such as but not limited to the URLDownloadToCacheFile function can be used to download image data into the Internet cache. Following this, Toolbar Software 100 stores a command to create menus and submenus corresponding to the information obtained. From here, the process flows back to step 401 and remains in this loop until all nodes have been traversed. In case more nodes are present, Toolbar Software 100 proceeds to step 401 and remains in this loop until the search for all the nodes has been completed. Subsequent to concluding the search, at step 421, Toolbar Software 100 creates all the captions, separators, menus, etc., in the order. Step 421 is executed with the help of SendMessage TB_INSERTBUTTON to create all the captions, separators, buttons and drop-down menus on the toolbar. From step 421, Toolbar Software 100 proceeds to step 315 of FIG. 3. [0073] FIG. 5 illustrates a sample site menu interface of the present invention that is displayed in Site Menu Toolbar 105 of Browser 103. Browser 103, used herein, is Microsoft's Internet Explorer. Nevertheless, the present invention allows the use of any other browser such as Mozilla or Netscape's Navigator. The menu that is displayed in FIG. 5 relates to SBC's website. This menu, called Site Menu 501, corresponds to Site Menu Toolbar 105 of Web Services Client 101. Site Menu 501 can be seen on top of the website, below the address toolbar, inside the browser window. Site Menu 501 of the present invention may optionally display a short title, called Toolbar Title 503, of the toolbar. The remaining part of Site Menu 501 is further divided into two parts: 505, 507. The first part 505 consists of six standard buttons: ‘Chase’, ‘My Accounts’, Fill Form’, ‘Bill Reminder’, ‘Save Page’, and ‘Logout’. The other part, 507, consists of buttons that display menus and sub-menus that are specific to the web page. These contents are hereby referred to as Site Menu Interface 513. Site-specific Site Menu tab 507 can display any possible contents for the web page in FIG. 5. It is evident that the web page for SBC already has a menu 509 placed vertically on the left side in the browser window. An additional menu, 511, is seen in the right-hand side of the web page. Additional menu 511, similar to menu 509, is also provided by the web page itself. Contents of menus 509 and 511 are useful for directing a user to other parts of the website, which may not directly relate to the functions that are offered by the web page in FIG. 5. However, the contents of Site Menu 501 of the present invention offer the user a broad overview of the functions provided by the web page, as well as of the website. Services presented by separate menus inside a web page are combined into a comprehensive menu, provided in Site Menu 501. The standard buttons 505, incorporated by Site Menu 501, encapsulate various services commonly provided across different websites. [0074] Every time Web Services Client 101 selects one of the contents from Site Menu Interface 513, the action associated with that content is executed. For example, sub-menus for that content may appear in a drop-down box 515, and the user may be directed to another web page, and so forth. The display of sub-menu 515 depends on the hierarchical classification of the corresponding web page and website. [0075] Site Menu 501 facilitates ease of navigation for the user since it provides an interface that is familiar to the user. The screenshot of a web page in FIG. 5 illustrates that Site Menu Interface 513 is similar in appearance to the menu toolbar provided by Windows that is located at the topmost part of the window. Images added to the contents make Site Menu Interface 513 eye-catching and user-friendly. [0076] FIG. 6 illustrates another website, which is for Citibank. The menu presented by Site Menu System 107 is Site Menu 601. By observing FIG. 5 and 6, it follows that Site Menu 501 and Site Menu 601 are uniform in appearance. Here too, Site Menu 601 consists of a Toolbar Title 603. Toolbar Title 603 remains the same as in FIG. 5. This is because the web pages displayed in FIG. 5 and 6 have similar functions. Additionally, Site Menu 601 consists of a Site Menu Interface 605, which may be further divided into two parts. The first part, 607, consists of standard buttons that are identical to the standard buttons of FIG. 5. The second part, 609, consists of a menu and sub-menu that are specific to the contents of the web page of FIG. 6. Therefore, the Site Menu appearance is uniform throughout all the web pages that are browsed by the user. [0077] FIG. 7 shows yet another web page of a different website, for which a Site Menu 701 has been created by Toolbar Software 100. Referring to FIG. 7, the rightmost part (Toolbar Title 703) of Site Menu 701 shows the title of the toolbar. The remaining part of Site Menu 701 again consists of two parts. The first part, 705, comprises standard buttons that have not changed in either content or appearance. The second part, 707, comprises an inactive menu button. The button is inactive because no information about the menu contents available for the web page. Referring to FIG. 3, this implies that Toolbar Software 100, according to step 309, concludes that Site Menu Toolbar 105, specific to the web page, cannot be displayed. Consequently, it is apparent that Site Menu Toolbar 105 of the present invention remains uniform in appearance for all web pages across websites. At the same time, the contents of Site Menu Toolbar 105 are customized in accordance with each web page and website. Also, standard contents provided by Toolbar Software 100 remain in Site Menu Toolbar 105 for each web page and website. [0078] A person skilled in the art will appreciate that the process of the present invention can be programmed using C++ as a programming language. However, other programming languages such as Visual Basic, C#, Java, or any other language, can also be used instead of C. [0079] Additionally, a person skilled in the art can appreciate that all the connections between the various elements of the system of the present invention may be wired or wireless, depending upon the requirements of the system. Also, it should be noted that it is not essential that the various processing machines and/or storage elements be physically located in the same geographical location. The processing machines and/or storage elements may be located in geographically distinct locations and connected to each other to enable communication. This facilitates convenient and speedy navigation of websites. [0080] While the preferred embodiments of the disclosed method have been illustrated and described, it will be clear that the disclosed method is not limited only to these embodiments. Numerous modifications, changes, variations, substitutions and equivalents will be apparent to those skilled in the art, without departing from the spirit and scope of the disclosed method. Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS5742768 *Jul 16, 1996Apr 21, 1998Silicon Graphics, Inc.System and method for providing and displaying a web page having an embedded menuUS5914714 *Apr 1, 1997Jun 22, 1999Microsoft CorporationSystem and method for changing the characteristics of a button by direct manipulationUS6031534 *Jul 10, 1996Feb 29, 2000Microsoft CorporationOperating system function for specifying a checked image representation and an unchecked image representation of a menu itemUS6035330 *Mar 29, 1996Mar 7, 2000British TelecommunicationsWorld wide web navigational mapping system and methodUS6359633 *Jan 15, 1999Mar 19, 2002Yahoo! Inc.Apparatus and method for abstracting markup language documentsUS6393422 *Nov 13, 1998May 21, 2002International Business Machines CorporationNavigation method for dynamically generated HTML pagesUS6546397 *Dec 2, 1999Apr 8, 2003Steven H. RempellBrowser based web site generation tool and run time engineUS6819343 *May 5, 2000Nov 16, 2004Microsoft CorporationDynamic controls for use in computing applicationsUS20010029527 *Mar 15, 2001Oct 11, 2001Nadav GoshenMethod and system for providing a customized browser networkUS20020057299 *May 23, 2001May 16, 2002Dobronsky OrenSystem and method for the dynamic improvement of internet browser navigabilityUS20030043208 *Aug 31, 2001Mar 6, 2003Staelin Carl H.Dynamic menu systemUS20030202009 *Jan 27, 2003Oct 30, 2003Stephane KasrielIntegration toolbarUS20050039141 *Mar 18, 2004Feb 17, 2005Eric BurkeMethod and system of controlling a context menuUS20050081165 *Oct 19, 2004Apr 14, 2005Microsoft CorporationDynamic controls for use in computing applicationsUS20050149853 *Oct 21, 2004Jul 7, 2005Fujitsu LimitedDocument display program and method* Cited by examinerReferenced byCiting PatentFiling datePublication dateApplicantTitleUS7703036 *Sep 30, 2004Apr 20, 2010Microsoft CorporationUser interface for displaying selectable software functionality controls that are relevant to a selected objectUS7707255May 19, 2004Apr 27, 2010Microsoft CorporationAutomatic grouping of electronic mailUS7716593May 21, 2004May 11, 2010Microsoft CorporationConversation grouping of electronic mail recordsUS7739259May 9, 2006Jun 15, 2010Microsoft CorporationIntegrated search and find user interfaceUS7739620 *Sep 29, 2005Jun 15, 2010Adobe Systems Inc.Method of setting alternate style assignments to menu elements of an applicationUS7747966Sep 30, 2004Jun 29, 2010Microsoft CorporationUser interface for providing task management and calendar informationUS7853877Nov 5, 2004Dec 14, 2010Microsoft CorporationGallery user interface controlsUS7886290Jun 16, 2005Feb 8, 2011Microsoft CorporationCross version and cross product user interfaceUS7895531Jun 13, 2005Feb 22, 2011Microsoft CorporationFloating command objectUS7978665 *Jul 12, 2011Verizon Laboratories Inc.Systems and methods for providing connection status and location information in a wireless networking environmentUS7984379Apr 4, 2008Jul 19, 2011Microsoft CorporationStandard schema and user interface for website mapsUS8117542Sep 30, 2004Feb 14, 2012Microsoft CorporationUser interface for displaying selectable software functionality controls that are contextually relevant to a selected objectUS8146016Sep 30, 2004Mar 27, 2012Microsoft CorporationUser interface for displaying a gallery of formatting options applicable to a selected objectUS8150930Apr 5, 2010Apr 3, 2012Microsoft CorporationAutomatic grouping of electronic mailUS8201103Jun 12, 2012Microsoft CorporationAccessing an out-space user interface for a document editor programUS8234575 *Nov 30, 2007Jul 31, 2012Microsoft CorporationDynamic updateable web toolbarUS8239882Aug 30, 2005Aug 7, 2012Microsoft CorporationMarkup based extensibility for user interfacesUS8255828 *Sep 30, 2004Aug 28, 2012Microsoft CorporationCommand user interface for displaying selectable software functionality controlsUS8302014Jun 11, 2010Oct 30, 2012Microsoft CorporationMerging modifications to user interface components while preserving user customizationsUS8402096Jun 24, 2008Mar 19, 2013Microsoft CorporationAutomatic conversation techniquesUS8484574Dec 6, 2007Jul 9, 2013Microsoft CorporationRule-based multi-pane toolbar displayUS8484578Jun 27, 2008Jul 9, 2013Microsoft CorporationCommunication between a document editor in-space user interface and a document editor out-space user interfaceUS8599806Jul 5, 2011Dec 3, 2013Verizon Laboratories Inc.Systems and methods for providing connection status and location information in a wireless networking environmentUS8605090Jun 1, 2006Dec 10, 2013Microsoft CorporationModifying and formatting a chart using pictorially provided chart elementsUS8627222May 9, 2006Jan 7, 2014Microsoft CorporationExpanded search and find user interfaceUS8638333Oct 6, 2009Jan 28, 2014Microsoft CorporationModifying and formatting a chart using pictorially provided chart elementsUS8689137Apr 10, 2006Apr 1, 2014Microsoft CorporationCommand user interface for displaying selectable functionality controls in a database applicationUS8762880Jun 27, 2008Jun 24, 2014Microsoft CorporationExposing non-authoring features through document status information in an out-space user interfaceUS8799353Mar 30, 2009Aug 5, 2014Josef LarssonScope-based extensibility for control surfacesUS8799808May 21, 2004Aug 5, 2014Microsoft CorporationAdaptive multi-line view user interfaceUS8839139May 11, 2010Sep 16, 2014Microsoft CorporationUser interface for providing task management and calendar informationUS8972863May 27, 2011Mar 3, 2015Microsoft Technology Licensing, LlcStandard schema and user interface for website mapsUS9015621Feb 17, 2009Apr 21, 2015Microsoft Technology Licensing, LlcCommand user interface for displaying multiple sections of software functionality controlsUS9015624Feb 15, 2011Apr 21, 2015Microsoft CorporationFloating command objectUS9046983May 12, 2009Jun 2, 2015Microsoft Technology Licensing, LlcHierarchically-organized control galleriesUS9075892 *Jan 25, 2011Jul 7, 2015Miiicasa Holding (Cayman) Inc.Method for automatically inserting an embedded toolbar into a web browser directly by way of a gateway deviceUS9098473May 4, 2012Aug 4, 2015Microsoft Technology Licensing, LlcAccessing an out-space user interface for a document editor programUS9098837Feb 9, 2008Aug 4, 2015Microsoft Technology Licensing, LlcSide-by-side shared calendarsUS9223477Aug 27, 2012Dec 29, 2015Microsoft Technology Licensing, LlcCommand user interface for displaying selectable software functionality controlsUS20050004990 *May 21, 2004Jan 6, 2005Microsoft CorporationConversation grouping of electronic mail recordsUS20060059459 *Sep 13, 2004Mar 16, 2006Microsoft CorporationGenerating solution-based software documentationUS20070094267 *Oct 20, 2005Apr 26, 2007Glogood Inc.Method and system for website navigationUS20080005125 *Nov 3, 2006Jan 3, 2008Dewey GaedekeSystem for displaying user generated content in a web browserUS20080005282 *Nov 3, 2006Jan 3, 2008Dewey GaedckeMethod for displaying user generated content in a web browserUS20080104505 *Oct 27, 2006May 1, 2008Keohane Susann MMethod, System and Program Product Supporting Customized Presentation of Toolbars Within a DocumentUS20090144723 *Nov 30, 2007Jun 4, 2009Microsoft CorporationDynamic Updateable Web ToolbarUS20090150810 *Dec 6, 2007Jun 11, 2009Microsoft CorporationRule-Based Multi-Pane Toolbar DisplayUS20090164922 *Dec 20, 2007Jun 25, 2009Ouneheuane PhakousonhAuto toolbarUS20090199080 *Jan 31, 2008Aug 6, 2009Microsoft CorporationAdaptation of display pages for client environmentsUS20090254834 *Apr 4, 2008Oct 8, 2009Microsoft CorporationStandard Schema and User Interface for Website MapsUS20090257085 *Mar 27, 2009Oct 15, 2009Ricoh Company, Ltd.Generation of a web page including menu items for web pagesUS20090300478 *Dec 3, 2009Ricoh Company, Ltd.Image forming apparatus, information processing method and programUS20100070889 *Mar 18, 2010Adam WeisbartMethods for Bundling Disparate Sets of Web Resources to Unique String IdentifiersUS20100169363 *Jun 27, 2009Jul 1, 2010Dewey GaedckeSystem and method for managing and displaying additive content in a web browserUS20100180226 *Jul 15, 2010Microsoft CorporationUser Interface for Displaying Selectable Software Functionality Controls that are Relevant to a Selected ObjectUS20110072089 *Sep 21, 2009Mar 24, 2011Yahoo! Inc.Method and system for synchronizing software module hostsUS20110231776 *Sep 22, 2011Microsoft CorporationStandard schema and user interface for website mapsUS20120151375 *Jun 14, 2012D-Link CorporationMethod for automatically inserting an embedded toolbar into a web browser directly by way of a gateway deviceEP2272042A2 *Mar 23, 2009Jan 12, 2011Microsoft CorporationIntelligent autocompletionWO2009131779A2Mar 23, 2009Oct 29, 2009Microsoft CorporationIntelligent autocompletion* Cited by examinerClassifications U.S. Classification717/109, 707/E17.118, 717/173, 707/E17.121International ClassificationG06F9/44, G06F17/30, G06F3/048Cooperative ClassificationG06F17/30896, G06F3/0481, G06F17/30905European ClassificationG06F3/0481, G06F17/30W9V, G06F17/30W7SLegal EventsDateCodeEventDescriptionJan 30, 2004ASAssignmentOwner name: AHIKA CORPORATION, CALIFORNIAFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:LALWANI, RAJESH;REEL/FRAME:014952/0658Effective date: 20040129RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services