Software application agent interface

Abstract

A software application system and method for facilitating the communication in a distributed computer environment among different processes active on the same or different computing platforms. In an embodiment of the invention, a server process running on a first computer system communicates with an application process running on the same computer via an application agent. The agent is designed specifically to work with a particular application, and translates or otherwise relays requests from the server process to the application process, and vice versa. The method is advantageous in that changes to the application process may be compensated for by updating the application agent only—no changes are required at the server process level. This allows rapid deployment of new or updated application throughout the enterprise.

Description

COPYRIGHT NOTICE

[0002] A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.

CROSS-REFERENCE CASES

[0003] The following applications are cross-referenced and incorporated herein by reference:

[0004] U.S. Provisional Application entitled “Configurable Graphical User Environment,” by Clayton Wishoff and Linda Byrne, Serial No. 60/218,123, filed on Jul. 13, 2000; U.S. Provisional Application entitled “Notification Device for a Graphical User Environment,” by Clayton Wishoff, Serial No. 60/218,095, filed on Jul. 13, 2000; U.S. Provisional Application entitled “Application Container for a Graphical User Environment,” by Clayton Wishoff, Serial No. 60/217,919, filed on Jul. 13, 2000; and U.S. Provisional Application entitled “Distributed Application Interface and Authentication Process,” by Clayton Wishoff, Claudio Werneck and James Pearce, Serial No. 60/217,886, filed on Jul. 13, 2000.

FIELD OF THE INVENTION

[0005] The invention relates generally to systems used for creating graphical user environments or interfaces, and specifically to a system and method for creating a configurable graphical user environment.

BACKGROUND OF THE INVENTION

[0006] With the growth of Internet and satellite communications and the hardware and software which supports the same, there are a number of opportunities for companies which provide services and functionality for communicating information effectively between individuals and entities. By way of example only, one service provider, America Online, provides both Internet access as well as its own content. This provider targets a variety of user bases, including children, and derives most of its revenue from advertising. This provider provides a large amount of content and a user interface for its audience. In addition, this provider can leverage its log-in base network to address the demographics of its user base.

[0007] Another example which is used in schools is the Channel One System. This system operates an advertising-supported educational television service for secondary school students in the United States. Historically, the system brings news and current events for the schools by satellite, generating revenue from advertising interspersed in the programming.

[0008] Yet another example includes the Hughes Electronics System which offers satellite-based broadband Internet access for consumers. The system does not provide its own content. A further example of such a system is offered by Disney. This system offers a wide variety of Internet contact provided to children.

[0009] Accordingly, there still exists a need to build a broadband interactive network which is highly configurable and which can address the content and communication needs of a wide variety of private, educational, institutional, commercial and industrial environments.

SUMMARY OF THE INVENTION

[0010] In a distributed computer environment, it is desired to provide an interface so that a first process on a first computer may act upon or communicate with a second process operating either on the same computer or on another computer. It is an objective of the invention to provide a system and a method to allow a process to interact with another process by means of an application interface, agent or applet.

[0011] In an embodiment of the invention, a server process running on a first computer system communicates with an application process running on the same computer via an application agent. The agent is designed specifically to work with a particular application, and translates or otherwise relays requests from the server process to the application process, and vice versa. The method is advantageous in that changes to the application process may be compensated for by updating the application agent only—no changes are required at the server process level. This allows rapid deployment of new or updated application throughout the enterprise.

[0012] A variety of simple and complicated menu structures may be added to the server process to compliment the user's specific needs. The menus may be used to facilitate the communications between the server process and application processes.

BRIEF DESCRIPTION OF THE FIGURES

[0013] The present invention will be described with references to the accompanying drawings, taken in conjunction with the following description wherein,

[0014] FIG. 1 illustrates the placement of the Jaguar server of an embodiment of the invention within a typical system environment.

[0015] FIG. 2 illustrates how components in the Jaguar server system of an embodiment of the invention interoperate with each another.

[0016] FIG. 3 illustrates a screen display produced by the Jaguar server on parsing the skin file of Appendix A of an embodiment of the invention.

[0017] FIG. 4 shows a block diagram with interconnects of an embodiment of the invention at a system level.

[0018] FIG. 5 shows two examples of an interaction between the Jaguar Server and a third party application of an embodiment of the invention.

DETAILED DESCRIPTION OF THE INVENTION

[0019] FIGS. 1-3:

[0020] The Jaguar Graphical User Interface System

[0021] The invention as embodied relates to a series of novel enhancements and modifications for use with a distributed media communications and advertising system. Specifically, in the environment of a school, university, or other similar institution where many users may commonly share several user computers, or user machines, there exists current systems and methods to allow an advertiser to send, or otherwise display advertisements of their products or services on the user's computer. The invention describes a unique variant of such a system, together with a number of features which may further be used in other systems, by other vendors, and for other purposes.

[0022] The communications and advertising system embodied herein is known as “Jaguar Graphical User Interface”. Jaguar comprises a Server element, commonly called the “Jaguar Server,” “Jaguar” or simply the “Server”. The Jaguar Server operates upon the user's machine to generate display screens in accordance with defined rules and variables. Some of these rules may determine a user's access rights, the type of software application available to a user, or the advertising or news media information the user will receive.

[0023] The user interacts with the Server by means of an agent process, which can for example be a login process, a configuration process, etc. The Server similarly interacts with other Servers, such as mail Servers, and other entities (e.g. software applications), by means of similar agents. One common agent is a browser agent, which allows the user to access the Server in a browser or Net-like manner. The desktop environment may in this manner be thought of as a ‘Netspace’—a visual space or desktop through which the user interacts with the environment surrounding him.

[0024] An embodiment of the Jaguar system as it may be embodied in a school or educational environment 100 is shown in FIG. 1. As illustrated, a Jaguar Server 110 is in communication with both a centralized network operations center 120 and a school Server 130. Each of these components may have several sub-components, not shown here for clarity. In essence the Jaguar Server 110 utilizes information from a Network Operations Center NOC 120 to instruct the school Server 130 to customize the media, news, or advertising content 135 which the user 105, sees, dynamically and instantly, as determined by the instructions given to the NOC by a advertising/media coordinator 150. A database is maintained by the NOC, both for purposes of validating user logins, storing advertising information, and storing demographic information on each user so as to better target specific media/advertising.

[0025] Focusing more on the Jaguar Server, the manner in which it interoperates and communicates with other processes is shown in FIG. 2. In this embodiment the Jaguar Server 170 may communicate with a login agent 175 to validate user logins and generate initial screens or Netspaces. A Jaguar client 180 reads skins to dynamically change the look and feel of the usual environment of the fly. Application agents 185, 190, 195 interact with the Jaguar Server, while a Message Trap 200 detects and notifies the user of actionable events. Some agents, such as a Microsoft Word agent 190 allows the Jaguar Server to make COM calls directly to the application (i.e. Word) itself. The key components of the system are as follows:

[0026] Jaguar Server 170

[0027] The Server is COM automated. COM is an architecture for defining interfaces and interaction among objects implemented by widely varying software applications. A COM object instantiates one or more interfaces, each of which exposes zero or more properties and zero or more methods. All COM interfaces are derived from the base class IUnknown. Technologies built on the COM foundation include ActiveX and OLE. The methods the Jaguar Server exposes are used to customize it's look and feel for different users. The Jaguar Server sends events to the client applications using an event sink that was initiated by the client. The Server is like the engine of a car, it works on its own but, without a frame and wheels it isn't very useful. The Configuration Agent is the frame and wheels and the other clients are like options.

[0028] Jaguar Configuration Agent and Skin File Reader 180

[0029] The Jaguar Server launches the Jaguar Configuration Agent (client) at startup. The client then reads the skin file and instructs the Server via COM calls to create buttons, menus etc . . . . The client then launches the login agent and any other agents the skin file requests. Any agent that is launched has the responsibility to connect to the Server in order to control it. This allows the Server to be independent of any agent. It also allows for multiple clients to control and effect changes in the Server.

[0030] Other Agents 175, 185, 190, 195

[0031] The other agents in FIG. 2 are the login agent, the browser agent and the e-mail agent. All three agents act in the same way as the Jaguar Client except for one major difference. If one of these agents wants to launch an agent itself (i.e. The email agent launches a browser agent) they send a request to the Server who launches it. This way all applications are launched in the same manner and can be kept track of by the Server.

[0032] Login Agent 175

[0033] At startup the Configuration reader instructs the Server to launch the Login Agent. The Server is primarily disabled (buttons are inactive and no ads are served) until the user has logged in. The login script launches a browser that's soul function is to control the log-in state. Once the user gives a correct username and password the Login Agent is hidden until logout and a Browser Agent is launched. When this new agent gets the username and login information in its URL it tells the Server that login was successful and items become enabled in accordance with the instructions from the Skin File. When the user logs-out or it times out then all open applications (except the Server and Configuration Agent) are instructed to close and the Login screen will reappear to log in the next user.

[0034] Browser Agent 185

[0035] The Browser Agent contains an Internet browsing window. This agent is used by the Server to display browsers that are task specific. The browser was created to support the Multi-browser Architecture. The Multi-browser architecture gives the user the ability to have more than one browser up at a time with its own forward and back state. In Internet Explorer or Netscape Navigator navigating can be cumbersome because all navigation occur in one primary window. With Jaguar the designer can have browsers that perform specific task like searching, e-mailing, updating their calendar etc. each in their own browsers with their own back/forward state. These windows are independent of any other browser. If the user selects the search button from the desktop (Server) the Server checks to see if a dedicated browser for search is already running if not it launches one otherwise it brings the search browser to the top. This feature makes users much more efficient and saves time.

[0036] E-mail Agent 195

[0037] The E-mail Agent in one embodiment instructs the Server to launch a version of the Browser to be the container of the E-mail. The email agent also controls the e-mail notification icon that may appear on the desktop. This icon on the Server will flash (animate) when the user has new unread mail. The e-mail agent is hidden and very small in size. It transparently controls the Server's e-mail icon. This is another example of the flexibility of the Jaguar Architecture.

[0038] Third Party Applications 190

[0039] The paradigm of having an agent that controls the communication between a Server and a third party application (as seen in the diagram for Microsoft Word) is very powerful. Any third party application can be added to the ZapMe! product offering by simply installing the application and a very small agent. In the past entire servers would have to be changed in order to add applications.

[0040] Message Trap 200

[0041] The Message Trap traps all system messages and filters the messages related to window sizing and placement. It gets its parameters for the area to contain from the Server who reads it from the skin file. The message trap also controls the information about the systems idle state. If the user moves the mouse or uses the keyboard then the idle state is reset. The Server will log the user out automatically if the idle state is more than a specified value (15 minutes is the default). The Server tells the message trap via a function call to set the containment area at a certain location and size. Any attempt to resize or move the windows to a location outside that area will fail. This guarantees advertisers that, while playing, their ads will not be covered up.

[0042] ZapMe! and Jaguar

[0043] Jaguar is the user's primary interface to the ZapMe! netspace and may be referred to as the “desktop”. The Jaguar interface is the starting point for all activities within the ZapMe netspace. Imaginative use of color, graphics and animations give the GUI an exciting look, while new and creative controls provide a fun experience. Jaguar also functions in the home market, giving a consistent look and feel to users whether at home or at school.

[0044] ZapMe! Client

[0045] The ZapMe! client, the user interface for the ZapMe! netspace, creates a set of features which gives access to the next generation of new technology. These new features and functions are so dynamic and compelling that kids are drawn to maximum use of the ZapMe! netspace. The ZapMe! netspace for school is delivered via satellite to each ZapMe! school. The ZapMe! netspace for the home is distributed via CD-ROM.

[0046] The ZapMe! netspace is a complete solution for the educational and entertainment lifestyle concerns for the targeted age group. This school and home product may be considered the “method of choice” for kids to communicate with their friends and to gather information about the world around them.

[0047] Jaguar Features

[0048] 1. Desktop

[0049] In one embodiment, Jaguar is a window that is 1024 pixels by 768 pixels. This window will cover the entire screen and not have a title bar or borders. In effect it will be a full screen window whose client area extends to the edges of the screen. Jaguar may be set to run primarily in a 16-bit color mode (e.g. 65536 colors). While Jaguar will support 8-bit color mode (256 colors) it will not do so at the expense of the visual appeal of the 16-bit color version. For example, the 8-bit version may use a different set of skins than the 16-bit version so as not to impact the visual appeal of the 16-bit color version. Jaguar will still occupy (or attempt to occupy) the entire screen when the resolution of the Windows desktop is 1024×768 or 800×600.

[0050] 2. Login

[0051] When Jaguar is started, the user is shown a login screen. The login screen resides in the Container Area and its function is to prompt the user for his/her name and password. All other Jaguar user interface features that accept user input will be disabled or display an alert dialog to remind the user to log in with the exception of the Reset (School environment)/Exit (Home environment) button as described in the section titled Exit Button.

[0052] 3. Container Area

[0053] Jaguar is designed to have a large section of the screen reserved for the “Container Area”. The Container Area is the only area of the screen where applications launched by Jaguar can create their own windows. Jaguar can be directed to never allow any part of an application window to escape the Container Area. All operations on application windows (including moving, dragging, resizing, minimizing, maximizing, etc.) must keep the window constrained to this Container Area. In a school environment, the Container Area is typically set to be 800 pixels by 600 pixels. In a home environment, due to varying Jaguar desktop sizes, the Container Area may occupy an area that maintains the same distance from the Jaguar GUI controls as in the school environment.

[0054] 4. Launch Pad

[0055] In one embodiment Jaguar provides a set of menus called the “Launch Pad” that incorporates the six major categories of activities available to the student, including: Communication, Entertainment, Tools, Lifestyle, eCommerce, and Content. Each menu contains submenu items that can be dynamically added via a configuration file. Menu items may also be added by applications launched by Jaguar. ZapMe! may deem activities on the Launch Pad inappropriate for either the home or school environment in which case the menu item for that activity may invoke a demo and/or promote the version of Jaguar where the option is available. Launch Pad items can include not only activities created in-house by ZapMe!, but activities created by third parties as well, for example MS Word and MS Excel. These third party applications should be well behaved. Well-behaved applications are applications that don't break the paradigm of Jaguar.

[0056] 5. Open Apps Menu

[0057] Jaguar supports a menu that contains a list of all the open (e.g. running) applications. Selecting an item from the menu will bring the corresponding application to the foreground. Both Jaguar-aware and non Jaguar-aware applications may be listed in the Open Apps menu.

[0058] 6. History Menu

[0059] Jaguar supports a menu that contains a list of all the documents the user has loaded called the “History”. All documents loaded into any Jaguar-aware application running within Jaguar will be automatically added to the History menu, no user interaction is required. The documents can be of a variety of types, including: MS Word, MS Excel (.xls), MS PowerPoint (.ppt), URLs that reference a specific web page. Essentially, any document that can be loaded into a Jaguar-aware application. The menu is hierarchical with the first level displaying a list of applications. The second level displays a list of documents that the corresponding application has loaded. Documents are added to the top of the second level menus such that the most recently accessed documents will be at the top of the menu. A document will never be listed twice in the same second level menu, but it is possible for the same document to be in two different second level menus if the document was loaded from two different applications. If a document is already listed, the old item is deleted from the menu before the new item is inserted. When a document is selected from the Document History menu it is loaded back into the application from which it was added (launching the application if necessary) and that application is brought to the foreground in the Container Area. The contents of the History menu are not saved across user sessions. When a user logs out the contents of the History menu is lost.

[0060] 7. Bookmarks Menu

[0061] Jaguar supports a menu that contains a list of user selected documents called “bookmarks”. The documents in the Bookmarks menu can be any document that is included in the History menu. If it's listed in the History menu, then it can be added to the Bookmark menu. When a document is selected from the Bookmark menu, it is loaded back into the application from which it was bookmarked (launching the application if necessary). That application is then brought to the foreground in the Container Area. Each user account can maintain a separate list of bookmarks that are saved across sessions so that the user can logout and then log back in (possibly on another workstation) without any changes to the list of bookmarks. The first three menu items on the Bookmarks menu are reserved for bookmark administration and will be added automatically by Jaguar. Add Bookmark—this menu item will add the current document in the foreground application to the Bookmarks menu. Documents will never be added automatically to the Bookmarks menu. While the application may also have a way to add documents to the Bookmarks menu, a specific action on the part of the user is always required to add a document to the Bookmarks menu. Organize Bookmarks this menu item will navigate to a web page where the bookmarks may be moved, copied and deleted. The third item on the Bookmarks menu is a menu item separator to separate the administration functions from the actual bookmarks.

[0062] 8. Notification Items

[0063] Jaguar provides the ability to display a set of “Notification Icons”. The Notification Icons will be arranged next to a small text display called the “Notification Window”. A Notification Icon can be associated with a specific application. An application does not have to be listed in the Open Apps menu (e.g. it doesn't have to be running) to have it's Notification Icon displayed. A Notification Icon can be designated to animate to alert the user that the application wants the user's attention. Together with the animating icon, a text message will be displayed in the Notification Window to give the user a more precise indication of the nature of the alert. In one embodiment double clicking or selecting a Notification Icon will bring that application to the foreground (launching the application if necessary). Double clicking the icon will have the same effect regardless of the alert state of the icon; essentially providing a short cut to the application. A single click on a Notification Icon will cancel a pending alert without bringing the application to the foreground. If multiple alerts are pending, the Notification Window can cycle the messages from all the pending alerts. Holding the cursor over a Notification Icon displays the name of the icon unless it is in an alert state. If the Notification Icon is in an alert state, it displays the alert text message instead.

[0064] 9. Logos

[0065] Jaguar provides the ability to display logos. The logos may be animations that can be played, or set to display any frame in the animation, including for example uncompressed AVI files. When double-clicked, a logo can broadcast an event via Jaguar's event mechanism so that specific behaviors can be attached.

[0066] 10. Ticker Tapes

[0067] Jaguar provides the ability to display single-line message windows called “Ticker Tapes”. A Ticker Tape can display text messages of arbitrary length, regardless of the size of the Ticker Tape window. A message will scroll smoothly across the Ticker Tape until the entire message is completely out of sight. When double-clicked, a Ticker Tape can broadcast an event via Jaguar's event mechanism so that specific behaviors can be attached.

[0068] 11. Dynamic Billboard

[0069] Jaguar provides the ability to display HTML windows called “Dynamic Billboards”. A Dynamic Billboard displays advertisements and other HTML content to the user. The content displayed by the Dynamic Billboard will be dynamically configurable by ZapMe!. At no time is the Dynamic Billboard obscured by any other piece of Jaguar. Jaguar does not interfere or enhance the operation of the HTML window. The only exception is if the HTML window tries to create a new window, in which case Jaguar will redirect the navigation that attempted to leave the HTML window to the same URL but using ZapMe!'s proprietary browser. If the target of the navigation (the target is specified in the HTML code that tried to open the new window) is “ZapMeLaunch” (case sensitive), then the URL is assumed to be the name of a program which is then launched in the Container Area.

[0070] 12. Date and Time

[0071] Jaguar displays both the date and the time to the user. Both the date and time can be the current date and time as reported by the computer (local time) or one of a variety of worldwide time zones. The format the date and time are displayed in is dynamically configurable by ZapMe!

[0072] 13. About Box

[0073] Jaguar can display an “about” box, which contains, for example: The name and version number of the skin; Jaguar's version number; the name of the workstation Jaguar is running on; the IP address of the workstation Jaguar is running on; the IP address of the school Server where Jaguar is running; the screen name of the student logged in; and a copyright message.

[0074] 14. Idle Time

[0075] After a dynamically configurable amount of time, Jaguar can be set to enter an idle mode. Jaguar will exit this idle mode if there is any keyboard or mouse activity. There is no built-in action upon entering or exiting idle mode; events are sent via Jaguar's event mechanism so that specific actions can be taken.

[0076] 15. Background Bitmap

[0077] The user can set a specific bitmap to be the background of their user interface. This background is the basic element in which all other buttons, menus, etc. are placed.

[0078] Skin Files

[0079] Jaguar provides the ability to configure the desktop via a text file called a Skin. The Skin File provides the ability to create Jaguar GUI objects and attach pre-defined actions to various events that the objects generate. Using Skin Files, it is possible to create a desktop with a particular look, layout and behavior without making code changes to Jaguar.

[0080] Skin Files also provides the ability to change the look, layout and behavior based on information about the user who's logged in, and/or other configurable information available via Jaguar's Configuration API.

[0081] While the Skin File is text-based, it is stored in an encoded format so that inadvertent and/or malicious changes can not be made by non-ZapMe! personnel. The Skin File may include and/or exclude any of Jaguar's GUI features.

[0082] Logging

[0083] Jaguar logs all user activity to a file whose location is dynamically configurable by ZapMe!.

[0084] Architecture

[0085] Since the list of activities that Jaguar supports is not static, Jaguar needs to be expandable in a manner that is elegant and easy to maintain. Allowing a team of engineers to simultaneously work on different features without interfering with each other. To do this Jaguar follows a client/Server model using the COM Automation architecture. Jaguar itself will play the role of the Server, while the activities (also referred to as applets) are COM clients. Jaguar is a separate executable from the applets and each activity is implemented as a separate applet as well. This allows not only for individual development of each applet, but also allows us the creation of new applets, and therefore new activities, without having to modify Jaguar.

[0086] To allow the applets to communicate with Jaguar, Jaguar supports a variety of methods that enable the applets to manipulate the proprietary features of the Jaguar interface. These methods may be invoked using COM Automation technology. In addition, the applets will be notified of actions on the Jaguar interface though the use of COM events and event sinks.

[0087] Jaguar plays a central role in the user's experience. The user interacts with Jaguar to select among a variety of activities. In addition, Jaguar plays the role of coordinator allowing these activities to peacefully co-exist, not only with each other, but also with the proprietary features of the Jaguar interface. To do this Jaguar communicates with the applets providing the activities either directly, through a COM interface that the applet exports via Automation, or indirectly by hooking system services and filtering and/or translating messages sent to the applets by Windows itself. Applets that conform by providing a COM Automation interface, or that can be made to conform by hooking system services, are said to be well behaved. Well-behaved applets are applets that can be programmatically made to do the following: stay within the Container Area; be brought to the foreground; be minimized and restored; add documents they load to the History menu; bookmark documents that are currently loaded; load a specified document.

[0088] The challenge comes when 3rd party applets, applets not written by ZapMe! that don't communicate directly with Jaguar, are incorporated into Jaguar. Solutions to seamlessly integrate 3rd party applets can come from one of two directions:

[0089] The first solution involves hooking system services to monitor the activity of the 3rd party applet. This method can be used to monitor and act upon windows created by the applets. To that extent, constraining an applet to the Container Area, bringing it to the foreground, minimizing and restoring windows can be accomplished by filtering and altering certain messages sent to the applet's windows. Monitoring which documents are loaded by an applet and forcing an applet to load a particular document, while possible, are not well suited to hooking system services; that's where the second solution comes in.

[0090] The second solution involves creating an applet, called an agent, to act as a translator between Jaguar and a 3rd party program, referred to as the target of the agent. In this way, Jaguar doesn't need to know the specifics of 3rd party programs, it treats the agent just like any other applet, and it's the agent's job to make sure that the 3rd party program is well behaved. The methods that Jaguar supports are grouped into interfaces. Each interface provides access to a particular feature of Jaguar; most of which provide access to the proprietary features of the Jaguar interface such as notification icons and ticker tapes. By providing flexible interfaces, Jaguar creates a strong base on which to build.

[0091] Menu Interface

[0092] The menu interface allows access to the standard menus, which are guaranteed to exist, as well as allow an applet to create their own menus. Three different objects, menu buttons, menus and menu items define the menu interface.

[0093] Menu buttons are the anchor points for menus. Menu buttons are displayed on the screen and when pressed show their associated menu. It's also possible to create a menu button without a menu, in which case the menu button acts like a simple button. Menus are the centerpieces of the menu interface. Menus are simply containers that hold menu items. Menu items are where all the action takes place. Menu items can either perform generic actions, or they can have associated menu, in effect creating a sub menu.

[0094] Menu items don't have a preconceived idea of what will happen when they are selected (with the exception of a menu item that has an associated sub menu); they merely fire events back to the owner. It's the owner's responsibility to take appropriate action when they receive the event from the menu item. In this way, actions on menus can be whatever an applet desires. Jaguar uses the menu interface to create the Launch Pad; a set of menus that initiate activities. There are six main menus that make up the Launch Pad: Communication; Entertainment; Tools; Lifestyle; eCommerce; Content.

[0095] While Jaguar initially populates the Launch Pad menus, they are also be available to applets. Since Jaguar created the menus, the applets will not know the handles of the menus, which is required to add menu items to them. To accommodate this, the menu interface also accept a predefined menu ID (each Launch Pad menu will have a separate ID) in place of a menu handle.

[0096] History Menu Interface

[0097] The History menu contains a list of documents that the user has loaded. The menu is maintained automatically by Jaguar. No special action is required on the part of the user to add items to the History menu. Each document that is loaded by an application within Jaguar is added to the History menu. The History menu interface will prevent the menu from growing too long by automatically deleting older items from the menu. Selecting a document from the History menu will cause that document to be displayed in the foreground.

[0098] The History menu interface is implemented as a thin layer on top of the Menu interface to support the proper rules when inserting items into the History menu. These rules include that: New items are always inserted at the top of the menu, such that items accessed more recently will be at the top of the menu. When adding a document that already exists on the menu, the old menu item is deleted before the new menu item is added. When adding items to the History menu a normal menu item is returned. This menu item can be used just like any other menu item and be passed to any method listed in the Menu interface that takes a menu item.

[0099] The menu items returned by the History menu interface will not fire events back to the application that added the menu item because it's very likely that the application that added the menu item is no longer running. Instead, Jaguar determines if the application is still running. If the application is running the document name is sent via a ZapLoadDocument event to the application. If the application is not running, it is re-launched with the name of the document on the command line.

[0100] Bookmark Menu

[0101] The Bookmark menu contains a list of documents that the user has selected. Adding an item to the Bookmark menu requires a specific action on the part of the user. Any document that is loaded by an application within Jaguar can be added to the Bookmark menu. The Bookmark menu can have a hierarchical structure to help organize the user bookmarks. Selecting a document from the Bookmark menu will cause that document to be displayed in the foreground.

[0102] The Bookmark menu interface is implemented as a thin layer on top of the Menu interface to support features specific to the Bookmarks menu. These features include: inserting at the proper position; adding new bookmarks at the Server's request (as opposed to the clients' initiative); editing and organizing the contents of the bookmarks menu.

[0103] When adding items to the Bookmark menu a normal menu item is returned. This menu item can be used just like any other menu item and be passed to any method listed in the Menu interface that takes a menu item.

[0104] The menu items returned by the Bookmark menu interface will not fire events back to the application that added the menu item because it's very likely that the application that added the menu item is no longer running. Instead, Jaguar determines if the application is still running. If the application is running the document name is sent via a ZapLoadDocument event to the application. If the application is not running, it is re-launched with the name of the document on the command line.

[0105] Open Apps Menu

[0106] The Open Apps menu contains a list of applications that are currently running. Items are automatically added/deleted from the Open Apps menu as applications are launched/closed. Selecting an item from the Open Apps menu will bring that application to the foreground.

[0107] The Open Apps menu interface is implemented as a thin layer on top of the Menu interface to support features specific to the Open Apps menu. These features include such as inserting at the proper position.

[0108] When adding items to the Open Apps menu a normal menu item is returned. This menu item can be used just like any other menu item and be passed to any method listed in the Menu interface that takes a menu item.

[0109] Since the menu items are automatically added/deleted by Jaguar, the application doesn't get the events associated with the Open Apps menu items; Jaguar will get them instead. If an application is Jaguar-aware then it will receive a ZapAppToTop event. The application should respond to this event by bringing itself (or its target application in the case of agents) to the foreground. Applications in the Open Apps menu will also be asked to close; this is done by sending their top-level windows a WM_CLOSE message.

[0110] Jaguar determines if the application represented by an Open Apps menu item is Jaguar-aware by inspecting the ownerID associated with the menu item. If the ownerID refers to Jaguar, then Jaguar assumes that the application is not Jaguar-aware and attempts to manipulate the application (bring it to the foreground, closing it, etc), by making Window's calls with the application's processID. If it doesn't refer to Jaguar, then Jaguar assumes that it has been updated by the application, and is therefore Jaguar-aware. Jaguar will send the application events to request a specific action. An application updates the ownerlD of the menu item by calling ZapOpenAppsItemSetLabel( ); therefore, a Jaguar aware application should update its label (even if it just calls ZapOpenAppsitemGetLabel( ) to get the current value) immediately after being launched.

[0111] Progress Meter

[0112] A progress meter reflects to the user how much of a task has been completed and how much of the task is still left to do. A natural way to look at a progress meter is that it portrays how much of a task is completed via a percentage, 0% meaning that the task has just started, while 100% means that the task has been completed. Hence each progress meter will have a value, from 0 to 100, which represents how much of a task has been completed. This value can be updated manually by calling ZapProgressMeterSetPercentage( ), or automatically by calling ZapProgressMeterStartAuto( ).

[0113] Internally progress meters have two parts. The first part is the progress meter state engine. The state engine is responsible for maintaining the value of the progress meter and updating the value when the progress meter is being updated automatically via a call to ZapProgressMeterAutoStart( ). The state engine is responsible for everything but displaying the progress meter on the screen.

[0114] The second part is the progress meter animation engine. The animation engine is responsible for the graphical representation of the progress meter. It takes the current value of the progress meter and displays an image on the screen. Separation and isolation of the state engine from the animation engine is necessary to implement virtual progress meters. A virtual progress meter is a progress meter that doesn't have a visible representation. In other words, a virtual progress meter has a state engine, but not an animation engine.

[0115] Depending on the graphical representation of a progress meters, there may only be one progress meter that is visible at a time. For example, the progress meter may be represented by animating the ZapMe! logo on the Jaguar interface. This means that the single progress meter must be shared by all the applets. Sharing the progress meter is done by creating virtual progress meters when the real progress meter is already being used. A virtual progress meter will fire events and otherwise behave exactly like a real progress meter with the sole exception being that it isn't visible.

[0116] The Popup Question

[0117] The Popup Question interface will present a question to the user along with a list of possible answers. Each question will be displayed in a non-modal dialog window within the Container Area. The format of the popup question varies slightly based on the number of possible answers for a question.

[0118] Container Area

[0119] Since Jaguar supports various activities and other 3rd party applications, an area of the desktop is needed for these activities to display their own windows and present their own GUIs to the user. However, Jaguar will not allow any of these windows to overlap, or obscure, any other pieces of Jaguar. To accomplish this, an area of the desktop is set aside for these windows to reside. This area is called the Container Area.

[0120] The Container Area represents a large portion of the Jaguar desktop and is the only area where non-Jaguar windows may move about freely. Non-Jaguar windows may not leave the Container Area and attempts to move and/or resize (either manually or programmatically) these windows such that they extend past any boundary of the Container Area will not succeed. Inside the Container Area, however, Jaguar and non-Jaguar windows may be moved, resized, maximized, minimized, overlap, etc. such that the look and feel of the Container Area is that of the standard Windows desktop.

[0121] Dynamic Billboard

[0122] The Dynamic Billboard Interface provides the applets with a mechanism to display content to the user that can not be obscured. Dynamic Billboards appear on the Jaguar desktop, but outside of the Container Area so that the user's windows can not obscure them. Dynamic billboards are based on Internet Explorer ActiveX control and can display HTML content.

[0123] Jaguar will not interfere or enhance the operation of the HTML window. The only exception is if the HTML window tries to create a new window, in which case Jaguar will redirect the navigation that attempted to leave the HTML window to a Browser Agent Window displayed inside the container area.

[0124] Ticker Tape

[0125] The Ticker Tape Interface provides the applets with a mechanism to display messages to the user. The messages scroll smoothly across a single-line text window in a round-robin fashion. The caller has no control over when a message added to a ticker tape is actually displayed, but is informed when the message is displayed.

[0126] Notify Item

[0127] The Notify Item Interface provides the applets with a mechanism to notify the user of events that need a response or immediate attention. A notify item represents itself on the Jaguar desktop as a small icon. To notify users of events or conditions, small animations are played in place of the icon and a message is displayed in a single-line text window called the notify window. Clicking on the notify item's icon cancels all pending alerts and returns the icon to it's original image.

[0128] Clock

[0129] The Clock Interface provides the applets with a mechanism to display the date and time on the desktop.

[0130] Logo

[0131] The Logo Interface provides the applets with a mechanism to display animations on the desktop. The AVI video may contain audio, while the video supports any codec installed on the system.

[0132] Configuration

[0133] The Configuration Interface provides the applets with a mechanism to store configurable variables. The variables can then be changed by a configuration applet that can be run either locally or remotely. In any case, by isolating the applets from the mechanism that is used to store the data, Jaguar can shield the applets from any recurring changes that must be made to allow remote configuration.

[0134] Office Applications

[0135] Several Microsoft Office products and other third-party applications can integrate with Jaguar, including Word, Excel and PowerPoint. Each of these applications should be well behaved and integrate seamlessly with Jaguar. Being well behaved was discussed in the Architecture Overview at the beginning of this document. There is no interface that directly supports the Microsoft Office applications, rather this section will discuss the interfaces that the agents will use to link Jaguar with the MS Office applications. There are three areas in Jaguar that the agent must attend to; History, Bookmarks and Open Apps. The use of any other interface to implement additional functionality is at the discretion of the agent.

[0136] The agents that target the MS Office applications must be running at all times, even if the application they target has been closed. The reason behind this is that the agents must respond to menu item events to load documents, launching the target application if necessary.

[0137] History

[0138] The agent must place each document that is loaded by the application into Jaguar's History menu. This can be done with a call to ZapHistoryItemAdd( ). In addition, each time a document is brought to the foreground it must be re-added to the History menu so that it is positioned at the top of the History menu. The History menu interface will take care of making sure that duplicates are removed, etc. The agent must also respond to the ZapMenuItemSelected( ) events that are sent out when items from the History menu are selected. When processing the event, the name of the document associated with the menu item can be retrieved using ZapHistoryItemGetDocument( ). Once an item is selected from the History menu it must be brought to the foreground in the application from which it was added. The appletPath parameter (in the call to ZapHistoryItemAd( )) should be used to identify the application that needs to load the document, rather than using the extension of the document to identify the application. In this way if two applications can load files of the same type, the document is loaded back into the application from which it was most recently used. For example; both Word and Excel can load files with the extension .xls, so assuming that Excel should load all documents with an extension of .xls is incorrect. Documents that are not currently loaded must be reloaded and then brought to the foreground. Documents listed in the History menu will remain in the History menu even if the document is closed from within the MS Office application. The agent must be capable of dealing with this case as well.

[0139] Bookmarks

[0140] The agent must add a name of the current document to the Bookmark menu at Jaguar's request. To do this, the agent must respond to the ZapBookmarkAddRequest( ) event by calling ZapBookmarkItemAdd( ) but only if the target application is in the foreground. If the target application is not in the foreground, the event must be ignored. The agent must also respond to the ZapMenuItemSelected( ) events that are sent out when items from the Bookmark menu are selected in the exact same way as was done for the History menu. Bringing them to the foreground, reloading if necessary, and using appletPath to determine the proper application.

[0141] Open Apps

[0142] The agent must place the name of the application it targets, not the name of the agent itself, into the Open Apps menu when the target application is started, using a call to ZapOpenAppsItemAdd( ). It must also remove this menu item when the application is closed, using a call to ZapOpenAppsItemDelete( ). The agent must also respond to the ZapMenuItemSelected( ) event from the menu item it added to the Open Apps menu by forcing the application to the foreground.

[0143] Software Application Agent Interface

[0144] The Jaguar Server plays a central role in the user's experience. The user will interact with the Jaguar Server to select among a variety of activities. In addition, the Jaguar Server will play the role of coordinator allowing these activities to peacefully co-exist, not only with each other, but also with the proprietary features of the Jaguar Server interface. To do this, the Jaguar Server will be required to communicate with the applets providing the activities either directly, through a COM Automation interface (Agents), indirectly by hooking system services and filtering, or translating messages sent to the applets by Windows itself.

[0145] Applets that conform by providing a COM Automation interface, or can be made to conform by hooking system services, are said to be “well behaved”. “Well behaved” applets are applets that can be programmatically made to do the following: (1) stay within the Container Area, (2) be brought to the foreground, (3) be minimized and restored, (4) add documents they load to the History menu, (5) bookmark documents that are currently loaded, and (6) load a specific document.

[0146] The challenge comes when third party applets, those that do not communicated directly with the Jaguar Server, are incorporated into the Jaguar Server. Solutions to seamlessly integrate third party applets can come from one of two directions.

[0147] The first solution involves hooking system services to monitor the activity of the third party applet. This method can be used to monitor and act upon windows created by the applets. To that extent, constraining an applet to the Container Area, bringing it to the foreground, minimizing and restoring windows can be accomplished by filtering and altering certain messages sent to the applet's windows. Monitoring which documents are loaded by an applet and forcing an applet to load a particular document, while possible, are not well suited to hooking systems services; that's where the second solution comes in.

[0148] The second solution involves creating an applet, called an Agent, to act as a translator between the Jaguar Server and a third party program, referred to as the target of the Agent. In this way, the Jaguar Server doesn't need to know the specifics of the third party programs. Rather, it treats the Agent just like any other applet, and it is the Agent's job to make sure that the third party program is “well behaved”. For example, A user may request a document from a COM Automated application. The Agent then sense the opening of the document in a COM event sink and records the document name. The Agent then notifies the Jaguar Server about the document and tells Jaguar to update its History Menu. The Jaguar Server then sense the Agent's communication and updates the History Menu list. Another Example is when a user selects a document from the Jaguar Server document list. The Agent then senses an event from Jaguar in a COM event sink and notifies the application of the requested action (such as loading a document). The Application sense the signal from the Agent and opens the document as requested. These examples are demonstrated in FIG. 5.

[0149] One example of how the system is embodied begins by a user inputting a signal through Jaguar, such as ‘clicking’ a button. This input is relayed to a Control-Agent which examines the User's input to a pre-defined list of actions. If the requested function is for something outside of the Jaguar Server engine, such as launching a third-party application (e.g. Microsoft Word), then the Control-Unit launches the Agent (e.g. Word-Agent).

[0150] The Agent is transparent to the user. The Agent receives input from the Jaguar Server engine to perform some action with the third party application (e.g. open a document). The Agent communicates with the third party application and informs the third party application that an event has been requested. Once the third party application, performs the requested event, then the Agent notifies the Jaguar Server engine as to the completion of the event. The Jaguar Server then informs the user that the event has completed (e.g. updating a document history list). The user, however, never perceives the Agent. The user perceives that the Jaguar Server engine communicated directly with the third party application to complete the user's request.

[0151] The Jaguar Server is equipped to handle an unlimited number of Agents. For each third party application incorporated with the Jaguar Server engine, a new Agent is created. By creating new Agents, or modifying old ones to accept new third party application functionality, the Jaguar Server engine is safe from unnecessary risks involved with testing. If the Jaguar Server engine was required to be modified every time there was a change in the third party application availability or functionality, then the time required to verify that the changes worked would result in “down time” for the user. By limiting the changes to relatively uncomplicated, transparent Agents, the Jaguar Server engine's integrity is protected.

[0152] Additionally, added flexibility is given to the entire Jaguar Server system by using Agents over direct modifications to the Jaguar Server engine. As new third party applications are added to the Jaguar environment, an Agent is created. Agents are less complicated and require less time than making changes directly to the Jaguar Server engine. Thus, the Jaguar Server engine's architecture remains intact and error free by using Agents to communicate with third party applications rather than communicating with them directly.

[0153] The menu interface allows access to the standard menus, which are guaranteed to exist, as well as allow an applet to create their own menus. Three different objects define the menu interface: menus, menu buttons, and menu items.

[0154] Menu buttons are the anchor points for menus. Menu buttons are displayed on the screen and when pressed show their associated menu. It's also possible to create a menu button without a menu, in which case the menu button acts like a simple button. Menus are the centerpieces of the menu interface. Menus are simply containers that hold menu items. Menu items can either perform generic actions, or they can have an associated menu, in effect creating a sub-menu.

[0155] Menu items don't have a preconceived idea of what will happen when they are selected (with the exception of a menu item that has an associated sub menu). Menu items merely fire events back to the owner. It is the owner's responsibility to take appropriate action when they receive the event from the menu item. In this way, actions on menus can be whatever an applet desire.

[0156] The Menu Interface is used for the History Menu, Bookmarks, and Open Apps menu. For instance, the History menu contains a list of documents that the user has loaded. The menu is maintained automatically by the Jaguar Server. No special action is required on the part of the user to add items to the History menu. The History menu interface will prevent the menu from growing too long by automatically deleting older items from the menu. Selecting a document from the History menu will cause that document to be displayed in the foreground.

[0157] The History menu interface is implemented as a thin layer on top of the Menu interface to support the proper rules when inserting items into the History menu. These rules include: (1) new items are always inserted at the top of the menu, such that items accessed more recently will be at the top of the menu, and (2) when adding a document that already exists on the menu, the old menu item is deleted before the new menu item is added.

[0158] When adding items to the History menu, a normal menu item is returned. This menu item can be used just like any other menu item and be passed to any method listed in the Menu interface that takes a menu item.

[0159] The menu items returned by the History menu interface will not fire events back to the application that added the menu item because it is very likely that the application that added the menu item is no longer running. Instead, the Jaguar Server determines if the application is still running by probing the Agents to see if there is an Agent for the desired application. If the Agent for the application is present, the document name is sent to the event application. If the Agent for the third party application is not present, then the third party application is re-launched with the name of the document on the command line. This opens the application with the document requested showing.

[0160] The Bookmark menu contains a list of documents that the user has selected. Adding an item to the Bookmark menu requires a specific action on the part of the user. Any document that is loaded by an application within the Jaguar Server can be added to the Bookmark menu. The Bookmark menu can have a hierarchical structure to help organize the user's bookmarks. Selecting a document from the Bookmark menu will cause that document to be displayed in the foreground.

[0161] The Bookmark menu interface is implemented as a thin layer on top of the Menu interface to support features specific to the Bookmarks menu. These features include: inserting at the proper position, adding new bookmarks at the Jaguar Server's request (as opposed to a client's initiative), and editing and organizing the contents of the bookmark menu. When adding items to the Bookmark menu, a normal menu item is returned. This menu item can be used just like any other menu item and be passed to any method listed in the Menu interface that takes a menu item.

[0162] The menu items returned by the Bookmark menu interface will not fire events back to the application that added the menu item because it is very likely that the application that added the menu item is no longer running. Instead, the Jaguar Server determines if the application is still running by examining existing Agents. If the application is running, the document name is sent to the application. If the application is not running, the application is launched with the name of the document on the command line.

[0163] Bookmarks are persistent. The contents of the Bookmark menu does not change when a User logs out and then logs back in. A different set of bookmarks is kept per user and stored in the database.

[0164] The Open Apps menu contains a list of applications that are currently running. Items are automatically added or deleted from the Open Apps menu as applications are launched and closed. Selecting an item from the Open Apps menu will bring that application to the foreground. The Open Apps menu interface is implemented as a thin layer on top of the Menu interface to support features specific to the Open Apps menu such as inserting at the proper position. When adding items to the Open Apps menu, a normal menu item is returned. This menu item can be used just like any other menu item and be passed to any method listed in the Menu interface that takes a menu item.

[0165] Since the menu items are automatically added and deleted by the Jaguar Server, the application doesn't get the events associated with the Open Apps menu items. Rather, the Jaguar Server acquires the events. If an application is Jaguar Server aware, then it will receive an event to move the application to the top. The application should respond to this event by bringing itself (or its target application in the case of Agents) to the foreground. Applications in the Open Apps menu will also be asked to close by sending them a “close” message.

[0166] The Jaguar Server determines if the application represented by an Open Apps menu item is Jaguar Server aware by inspecting the ownerlD associated with the menu item. If the ownerlD refers to the Jaguar Server, then the Jaguar Server assumes that the application is not Jaguar Server aware and attempts to manipulate the application through an Agent.

[0167] The application of the preferred embodiment of the present invention is best understood by referring to FIGS. 4-5 of the Drawings, wherein like numerals are used for like and corresponding parts of the drawings. In the following description, numerous specific details are set forth such as agents, applications, communication links, etc., in order to provide a thorough understanding of the present invention. It will be evident, however, to one of ordinary skill in the art that the present invention may be practiced without these specific details.

[0168] FIG. 4 illustrates, in the form of a block diagram, a system for facilitating communication between a Jaguar Server and a variety of applications in accordance with the present invention. Control Unit 402 prepares the Jaguar Server 404 for communications by way of the communications link 430. Once the Jaguar Server 404 has been initialized, the Jaguar Server 404 may require communications with a variety of “Jaguar aware” Applications 420. When the Jaguar Server 404 is ready to communicate with a specific application, the Jaguar Server 404 first queries both the Agent List 406 and the Jaguar Server Aware List 410 to determine whether the application and the Jaguar Server 404 have already established a link.

[0169] If the Jaguar Server 404 requests communication with an application that is a member of the Jaguar Server Aware Application 426 list such as SA1 428, then the Jaguar Server Aware List 410 will have a Notification SAL1 412 such that the Jaguar Server 404 will know that a communication link exists between Jaguar Server 404 and Jaguar Server Aware application SA1 428. If Notification SAL1 412 is contained in the Jaguar Server Aware List 410, then the Jaguar Server 404 can proceed to communicate with Jaguar Server Aware Application SA1 428 through the Communications Link 434 established between them. If Notification SAL1 412 does not exist in the Jaguar Server Aware List 410, then the Jaguar Server 404 sends a request to the Control Unit 402 to activate the Jaguar Server Aware Application SA1 428. Control Unit 402 will then launch the Jaguar Server Aware Application SA1 428 and provide the information necessary to the Jaguar Server 404 along Communications Link 430 so that the Jaguar Server 404 can update the Jaguar Server Aware List 410 with Notification SAL1 412. Once the Jaguar Server 404 has Notification SAL1 412 in the Jaguar Server Aware List 410, then the Jaguar Server 404 will establish the Communications Link 434 with the Jaguar Server Aware Application SA1 428.

[0170] When the Jaguar Server 404 is ready to terminate the Jaguar Server Aware Application SA1 428, then the Jaguar Server 404 sends the appropriate termination signal across Communications Link 434 to the Jaguar Server Aware Application SA1 428. The Jaguar Server 404 then removes the Notification SAL1 412 associated with the Jaguar Server Aware Application SA1 428.

[0171] If the Jaguar Server 404 requests communication with an application which is a member of the Jaguar Server Unaware Application List 422 such as SU1 424, then the Agent List 406 will have a Notification AL1 408 such that the Jaguar Server 404 will know that a communication link exists between Jaguar Server 404 and Jaguar Server Unaware application SU1 424. The communications between the Jaguar Server 404 and the Jaguar Server Unaware Application SU1 424, however, is not a direct link. The Jaguar Server 404 directly communicates with an Agent 416 such as Agent A1 418. Agent A1 418 receives information from the Jaguar Server 404 along Communications Link 432. The Jaguar Server 404 perceives the Agent A1 418 as if it were communicating directly with Jaguar Server Unaware Application SU1 424. The Agent A1 418 receives information from the Jaguar Server 404 along Communications Link 432 and translates the information into a format that the Jaguar Server Unaware Application SU1 424 can process. The Agent A1 418 then transmits this information to the Jaguar Server Unaware Application SU1 424 along Communications Link 436. Communications between the Jaguar Server 404 and the Jaguar Server Unaware Application SU1 424 by way of the Agent A1 418 proceed transparently to one another. When the Jaguar Server 404 transmits the order to terminate the Jaguar Server Unaware Application SU1 424, the Jaguar Server 404 does so in the same fashion that it did for the Jaguar Server Aware SA1 428. A difference, however, is that the termination signal sent by the Jaguar Server 404 is intercepted by the Agent A1 418 and translated into a format that the Jaguar Server Unaware Application SU1 424 can understand. The termination signal is then sent by the Agent A1 418 to the Jaguar Server Unaware Application SU1 424 by way of Communications Link 436. The Jaguar Server Unaware Application SU1 424 is then terminated.

[0172] If when the Jaguar Server queries the Agent List 406 and the Notification AL1 408 is absent, then the Jaguar Server 404 notifies the Control Unit 402 along Communications Link 430. The Control Unit 402 receives the notification from the Jaguar Server 404 and activates the appropriate Agent such as Agent A1 418 by way of Communications Link 416. The Control Unit 402 then notifies the Jaguar Server 404 of the activation of Agent A1 418 along Communications' Link 430. The Jaguar Server 404 then updates the Agent List 406 with the Notification AL1 408. The Jaguar Server then sends an application launch signal to the Agent A1 418 through Communications Link 432. Agent A1 418 translates this signal into a form understandable by the Jaguar Server Unaware Application SU1 424 and activates the Jaguar Server Unaware Application SU1 424 by way of Communications Link 436.

[0173] FIG. 5 illustrates two examples of an embodiment of the invention for communicating between the Jaguar Server and a third party application as well as creating a useful history menu for future access by the user.

[0174] The first example contained on the left side of the figure shows how user actions in MS Word 506 can be detected by the MS Word Agent 504 and result in a new item being added to the History Menu 510 in the Jaguar Server 404. As shown in block 514, the user requests that a document, journal.doc, be loaded by Microsoft Word 506, which executes an event to notify that the document, journal.doc, is being loaded. The MS Word Agent 504 catches the notification and informs the Jaguar Server 404 that the history list is to be updated with the name of journal doc. The Jaguar Server 404 receives the information from the MS Word Agent 504 and updates the History Menu 510 in step 508.

[0175] The second example contained on the right side of the figure shows how selecting an item from the History Menu 510 in the Jaguar Server 404 results in a document being brought to the foreground in MS Word 506. As shown in block 516, the user first selects the file myfile.doc from the History Menu 510. The Jaguar Server 404 then fires an event via COM that an item from the History Menu 510 has been selected. As shown in block 518, the MS Word Agent 504 catches the event from the Jaguar Server 404. The MS Word Agent 504 then notifies MS Word 506 that the file myfile.doc is requested. Block 520 shows MS Word 506 responding to the notification from the MS Word Agent 504 and brings the document myfile.doc to the foreground as directed.

[0176] While the specific embodiment(s) of the present invention have been described above with regard to the best mode and preferred embodiment(s) contemplated by the inventor, it is to be appreciated that the present invention is not limited to the above embodiment(s) and that various modifications may be made to the above embodiment(s) without departing from the broader spirit or scope of the present invention as defined in the following claims. The specific embodiment(s) are, accordingly, to be regarded in an illustrative, rather than a restrictive sense.

[0177] Industrial Applicability

[0178] Example of System Used in a School Environment

[0179] The present system is a broadband interactive network used in order to create an educational environment using the latest technology tools and educational resources. This environment is particularly directed to schools and school districts. This system connects schools and school districts together through the Internet using satellite communication techniques. The present system is directed to making education more engaging and entertaining and providing a rich media computer experience which is easy to use. The system is expandable into homes which enhances the students' educational experience and creates better communication between students, teachers and parents. As indicated, the system has an easy-to-use and configurable interface that provides access to a multiplicity of Internet sites for indexing, with easy reference with respect to content, applications and services. The system also provides computer and word processing tools in addition to a range of communication tools including a network e-mail program. The present system provides a platform for the school community to engage in important activities, including providing teachers and administrators with access to Internet-based vocational content, cost-effective school e-Commerce solutions, and school fundraising opportunities.

[0180] The present system is easily configurable to a number of other environments with the benefits of networking, easy communication, and access to multiple Internet sites. By way of example only, the present system can be configured for just about any type of private, commercial or industrial need. For example, the present system could be configured to meet the needs of participants in the insurance industry, the medical industry, the automobile industry, the finance industry, and many others. The configurable graphical user environment means that individuals with minimal computer knowledge would be able to configure the system for use in any of the above environments.

[0181] Other features, aspects and objects of the invention can be obtained from a review of the figures and the claims.

[0182] While the invention has been described herein with reference to a implementation referred to as Jaguar, and particularly with respect to the ZapMe! application; it will be evident to one skilled in the art that the invention may be equally used within other implementations and with other applications.

[0183] It is to be understood that other embodiments of the invention can be developed and fall within the spirit and scope of the invention and claims.

Claims

1. A system for facilitating communication between a server process and a series of application processes comprising: a server process; a first agent; a first application process; and, a control unit, said control unit includes an agent list and a server aware list, which together determine whether said first application process and said server have already established a link.

2. The system of claim 1 wherein if the server requests communication with an application that is a member of the server aware list then the server will know that a communication link exists between the server and said first application process.

3. The system of claim 1 wherein if the server requests communication with an application which is not a member of the server aware list then the server will know that a communication link does not exist between the server and said first application process.

4. The system of claim 1 wherein the server queries the agent list and the control unit activates an appropriate agent.

5. The system of claim 1 further comprising: a first communications link from the server to the first application; and, a second communications link from the server to the control unit.

6. The system of claim 5 such that the first application is aware of the server.

7. The system of claim 6 such that the control unit provides a first set of instructions to the server through a third communications link whereby the server is set into a ready state for communication with the first application.

8. The system of claim 7 such that the server creates a server aware list comprising a list of server aware applications such as the first application.

9. The system of claim 5 further comprising: a first communications link from the server to the first agent; a second communications link from the first agent to the first application; and, a third communications link from the server to the control unit.

10. The system of claim 1 such that the control unit provides a first set of instructions to the server whereby the server is set into a ready state for communication with the first agent.

11. The system of claim 1 such that the server creates a server unaware list comprising a list of agents such as the first agent.

12. The system of claim 1 such that the control unit causes the first agent to be in a state of readiness for communication with the server and the first application.

13. The system of claim 1 whereby the first agent receives a first set of information from the server through the first communications link, interprets the first set of information, converts the first set of information into a second set of information into a form understandable by the first application, and the first agent transmits the second set of information to the first application through the second communications link whereby the first application performs a first task.

14. The system of claim 13 whereby the first application transmits a third set of information to the first agent through the second communications link, the first agent interprets the third set of information and converts the third set of information into a fourth set of information whereby the server is able to interpret the fourth set of information, the first agent transmits the fourth set of information through the first communications link to the server whereby the server performs a second task.

15. A method for facilitating communication between a server process and a series of application processes comprising: providing a server process; providing a first agent; providing a first application process; and, providing a control unit, said control unit includes an agent list and a server aware list, which together determine whether said first application process and said server have already established a link.