Method for maintaining the look and feel of a user interface between uses

• US 20060085411A1
• Filed: 12/07/2005
• Published: 04/20/2006
• Est. Priority Date: 12/14/1995
• Status: Abandoned Application

• Current Assignee: GraphOn Corporation
• Original Assignee: GraphOn Corporation
• Inventors: Coley, Christopher D., Wesinger, Ralph E. Jr.
• Application Number:
  US11/297,204
• Publication Number:
  US 20060085411A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
• CPC Class Codes: G06Q 30/0623 Item investigation
• CPC Class Codes: Y10S 707/913 Multimedia
• CPC Class Codes: Y10S 707/99939 Privileged access
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing

Abstract

Methods and apparatus for maintaining the look and feel of a user interface between uses are disclosed. After validating the identity of a user, a user preferences file corresponding to the user ID may be accessed. A user interface may then have user-defined preferences restored in accordance with the user preferences file.

Claims

1. A method for maintaining the look and feel of a user interface between uses comprising:

receiving a request from a user to access a web page;

querying the user for a user ID;

responsive to receiving a valid user ID from the user, accessing a user preferences file corresponding to the user ID; and

restoring user-defined preferences of a user interface in accordance with the user preferences file.

2. The method of claim 1, further comprising the act of presenting the user with a page for adding entries to an on-line database.

3. The method of claim 2, further comprising the act of allowing the user to index said entries by one of a category, keyword, or URL.

4. The method of claim 3, further comprising the act of assigning a Transaction ID corresponding to each entry.

5. The method of claim 4, further comprising the act of allowing a user to add at least one link to either of an email address or a URL link corresponding to an entry.

6. The method of claim 4, further comprising the act of allowing a user to add a graphical image to an entry.

7. An apparatus for maintaining the look and feel of a user interface between uses comprising:

means for receiving a request from a user to access a web page;

means for querying the user for a user ID;

means for accessing a user preferences file corresponding to the user ID responsive to receiving a valid user ID from the user; and

means for restoring user-defined preferences of a user interface in accordance with the user preferences file.

8. The apparatus of claim 7, further comprising means for presenting the user with a page for adding entries to an on-line database.

9. The apparatus of claim 8, further comprising means for allowing the user to index said entries by one of a category, keyword, or URL.

10. The apparatus of claim 9, further comprising means for assigning a Transaction ID corresponding to each entry.

11. The apparatus of claim 10, further comprising means for allowing a user to add at least one link to either of an email address or a URL link corresponding to an entry.

12. The apparatus of claim 10, further comprising means for allowing a user to add a graphical image to an entry.

13. A web server configured for maintaining the look and feel of a Hyper Text Markup Language (HTML) front-ended publicly accessible database comprising:

a server site connected to a public network;

web server software operatively disposed within said server site;

HTML front-ending tools operatively coupled to the server site and configured to communicate through a publicly accessible user interface;

database management software operatively coupled to the HTML front-ending tools; and

said HTML front-ending tools being configured to;

receive a request from a user to access a web page;

query the user for a user ID;

access a user preferences file corresponding to the user ID;

validate said received user ID; and

restore user-defined preferences of a user interface in accordance with the user preferences file.

14. The web server of claim 13, wherein an entry may be created by said user that may be retrieved and displayed over the publicly accessible network by searching said site using a keyword associated with a user-defined category.

15. The web server of claim 14, wherein said server is configured to allow a user to update their entry over the public network.

16. The web server of claim 15, wherein said server is configured to allow a user to add an image to their entry.

17. The web server of claim 16, wherein said server is configured to create a Transaction ID for associating personal information of a user with a database entry and associated contents.

18. The web server of claim 17, wherein said server is configured to allow the user to add a new entry.

19. The web server of claim 18, wherein said new entry is associated with said user through said Transaction ID.

20. The web server of claim 13 wherein said HTML front-ending tools are written in C and configured as a CGI script.

21. The web server of claim 13 wherein said HTML front-ending tools are written in Java and configured as a Java script.

22. The web server of claim 13 wherein said HTML front-ending tools are written in a Unix shell language.

23. The web server of claim 15 wherein said HTML front-ending tools are written in C and configured as a CGI script.

24. The web server of claim 15 wherein said HTML front-ending tools are written in Java and configured as a Java script.

25. The web server of claim 15 wherein said HTML front-ending tools are written in a Unix shell language.