Source: http://www.google.com/patents/US7707514?dq=6,909,910
Timestamp: 2016-05-03 18:37:48
Document Index: 544088169

Matched Legal Cases: ['Application No. 60', 'Application No. 60', 'Application No. 60', 'Application No. 60', 'Application No. 60', 'Application No. 200580016349']

Patent US7707514 - Management of user interface elements in a display environment - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inPatentsA widget manager facilitates management of widgets in a dashboard layer. Management functions can include enablement, preview, importation, exportation, organization, installation, deletion, acquisition, etc....http://www.google.com/patents/US7707514?utm_source=gb-gplus-sharePatent US7707514 - Management of user interface elements in a display environmentAdvanced Patent SearchPublication numberUS7707514 B2Publication typeGrantApplication numberUS 11/429,492Publication dateApr 27, 2010Filing dateMay 5, 2006Priority dateNov 18, 2005Fee statusPaidAlso published asUS20070118813, US20100211886Publication number11429492, 429492, US 7707514 B2, US 7707514B2, US-B2-7707514, US7707514 B2, US7707514B2InventorsScott Forstall, Imran A. Chaudhri, John O. Louch, Eric Steven PeytonOriginal AssigneeApple Inc.Export CitationBiBTeX, EndNote, RefManPatent Citations (288), Non-Patent Citations (115), Referenced by (38), Classifications (22), Legal Events (4) External Links: USPTO, USPTO Assignment, EspacenetManagement of user interface elements in a display environment
US 7707514 B2Abstract
A widget manager facilitates management of widgets in a dashboard layer. Management functions can include enablement, preview, importation, exportation, organization, installation, deletion, acquisition, etc.
1. A widget manager comprising:
a management engine operable to present available widgets in a palette of a user interface display environment;
selectively enable or disable each of the available widgets; and
display enabled widgets in the display environment, where an enabled widget presently executes an associated function including providing a presentation aspect associated with the executing function, and where selectively enabling or disabling includes selecting a widget for enabling or disabling based on statistics for usage of a given widget by one or more users and criteria for evaluating the statistics,
wherein the statistics for usage including statistics for how often over a time period the given widget was enabled by the one or more users and when the respective widget was last enabled and wherein the usage criteria include information on how often the usage information is to be evaluated.
2. The widget manager of claim 1, wherein the management engine is further operable to locate widgets for installation in the display environment.
3. The widget manager of claim 1, wherein the management engine is further operable to install widgets into the display environment.
4. The widget manager of claim 3, wherein installing widgets includes previewing widgets in the display environment.
5. The widget manager of claim 1, wherein the display environment is a user interface of an electronic device.
6. A method of managing widgets for display in a display environment, comprising:
determining usage information for widgets when displayed in a display environment, the usage information including statistics for usage by one or more users of each respective widget, the statistics for usage including statistics for how often over a time period the respective widget was enabled by the one or more users and when the respective widget was last enabled;
determining usage criteria associated with the presentation of widgets in the display environment, the usage criteria defining how to evaluate the usage information in order to make a selection of one or more of the widgets for presentation in the display environment, the usage criteria include information on how often the usage information is to be evaluated;
selectively enabling at least one widget from available widgets based on the usage criteria and the usage information; and
displaying enabled widgets in the display environment.
7. The method of claim 6, wherein determining usage information includes determining usage information for more than one user.
8. The method of claim 6, wherein activation includes user interaction with the widget.
9. A method for managing widgets, comprising:
identifying available widgets for display in a display environment;
determining criteria for selecting ones of the available widgets, the criteria defining which widgets to select based on usage statistics of the widgets by one or more users, the usage statistics related to display of the widgets previously in a display environment and including statistics for how often over a time period a respective widget was displayed by the one or more users;
determining how often to evaluate the criteria including determining a time period;
after expiration of a time period, displaying and enabling selected ones of the available widgets, where an enabled widget presently executes an associated function including providing a presentation aspect associated with the executing function.
10. The method of claim 9, wherein the criteria is a random selection.
11. The method of claim 9, wherein the criteria are based on usage data associated with the available widgets.
12. The method of claim 9, wherein the criteria are defined by the user.
13. A computer-readable storage medium having stored thereon instructions which, when executed by a processor, causes the processor to perform the operations of:
determining usage information for widgets when displayed in a display environment the usage information including statistics for usage by one or more users of each respective widget related to display of the widgets previously in a display environment and including statistics for how often over a time period a respective widget was displayed by the one or more users and when the respective widget was last displayed;
14. A computer-readable storage medium having stored thereon instructions which, when executed by a processor, causes the processor to perform the operations of:
determining information and criteria for selecting ones of the available widgets, the information defining which widgets to select based on usage statistics associated with the widgets, the usage statistics related to display of the widgets previously in a display environment by one or more users and including statistics for how often over a time period a respective widget was displayed by the one or more users and when the respective widget was last displayed, the criteria defining how to evaluate the information in order to make a selection of one or more of the widgets for presentation in the display environment, the criteria defining how often the information is to be evaluated;
displaying and enabling selected ones of the available widgets, where an enabled widget presently executes an associated function including providing a presentation aspect associated with the executing function. Description
This application claims the benefit of priority from U.S. Provisional Patent Application No. 60/737,899, entitled “Management of User Interface Elements In A Display Environment,” filed Nov. 18, 2005, which provisional application is incorporated by reference herein in its entirety.
U.S. Provisional Patent Application No. 60/583,125, for “Procedurally Expressing Graphic Objects for Web Pages,” filed Jun. 25, 2004; U.S. patent application Ser. No. 10/874,829, for “User Interface for Assisting in the Installation of an Asset,” filed Jun. 22, 2004; U.S. patent application Ser. No. 11/145,561, for “Presenting Clips of Content,” filed Jun. 3, 2005; U.S. patent application Ser. No. 11/145,560, for “Web View Applications,” filed Jun. 3, 2005; U.S. patent application Ser. No. 11/145,023, for “Clip View Applications,” filed Jun. 3, 2005; U.S. patent application Ser. No. 11/148,010, for “Preview and Installation of User Interface Elements in a Display Environment,” filed Jun. 7, 2005; U.S. Provisional Patent Application No. 60/734,016, entitled “Preview including Theme Based Installation of User Interface Elements in a Display Environment,” filed Nov. 4, 2005, which provisional application is incorporated herein by reference in its entirety; U.S. Provisional Patent Application No. 60/730,956, entitled “Widget Security,” filed Oct. 27, 2005, which provisional application is incorporated herein by reference in its entirety; U.S. patent application Ser. No. 11/282,110, entitled “Preview including Theme Based Installation of User Interface Elements in a Display Environment,” filed Nov. 16, 2005; and U.S. patent application Ser. No. 11/346,603, entitled “Multiple Dashboards,” filed Feb. 1, 2006. TECHNICAL FIELD
Many of the deficiencies of conventional user interfaces can be reduced using “widgets.” Generally, widgets are user interface elements that include information and one or more tools (e.g., applications) that let the user perform common tasks and provide fast access to information. Widgets can perform a variety of tasks, including without limitation, communicating with a remote server to provide information to the user (e.g., weather report), providing commonly needed functionality (e.g., a calculator), or acting as an information repository (e.g., a notebook). Widgets can be displayed in a display environment and accessed through a user interface, such as a “dashboard.” Widgets and dashboards are described in co-pending U.S. patent application Ser. No. 10/877,968, entitled “Unified Interest Layer For User Interface.”
Due to the large number of widgets available to a user, a virtual desktop or dashboard can become cluttered and disorganized, making it difficult for the user to quickly locate and access a widget. Moreover, many widgets may not perform as expected or advertised when installed. Some widgets may even present a security risk to the host machine and network resources because they include a virus or are designed to carry out malicious activities. Accordingly, tools are required to manage all aspects of widget deployment and display.
In some implementations, a user-activated dashboard (also referred to as a “unified interest layer”) is provided that can contain any number of user interface elements, referred to herein as “widgets,” for quick access by a user. In response to a command from a user, the dashboard is invoked and the widgets are shown on the screen. In one aspect, a widget manager is provided as either a stand alone application, part of an installer process, part of the operating system or otherwise to facilitate management of widgets available to the user. Management functions can include enablement, preview, importation, exportation, organization, installation, deletion, acquisition and the like. Other management functions are possible.
Widgets can be of any type. They can communicate with a remote server to provide information to the user (e.g., a weather report), or they can provide commonly needed functionality (e.g., a calculator), or they can act as an information repository (e.g., a notepad or calendar). Some widgets can provide a combination of these types of functions.
Aspects of the invention can include one or more of the following features. The user interface element can be a widget. The display environment can be a dashboard, a desktop, or other display space.
In some implementations, a widget manager includes a management engine operable to present available widgets in a palette of a user interface display environment, to selectively enable or disable each of the available widgets, and to display enabled widgets in the display environment.
In some implementations, a method of managing widgets for display in a display environment includes: presenting a list of available widgets; receiving user input to enable one or more widgets to be displayed in a display environment; indicating in the list which widgets are enabled and to be displayed in the display environment from the available widgets; and at run time, instantiating each enabled widget in the display environment.
In some implementations, a method of managing widgets for display in a display environment includes: determining usage information for widgets when displayed in a display environment; determining usage criteria associated with the presentation of widgets in the display environment; selectively enabling and disabling at least one widget from the available widgets based on the usage criteria and the usage information; and displaying enabled widgets in the display environment.
In some implementations, a method of managing widgets includes: presenting a list of available widgets in a user interface; enabling a subset of the available widgets; and displaying the subset in a display environment of the user interface.
In some implementations, a method of managing widgets includes: determining user privileges; presenting a list of available widgets based on the user privileges; enabling a subset of the available widgets based on user selection; and displaying enabled widgets in a display environment.
In some implementations, a method for managing widgets includes: determining widgets that are available for display; classifying the available widgets; presenting the available widgets according to the classification; selectively enabling ones of the available widgets; and at run time, displaying enabled widgets in a display environment.
In some implementations, a method of managing widgets includes: identifying available widgets for display in a display environment; presenting the available widgets in a management environment; selectively enabling ones of the available widgets; and displaying enabled widgets in the display environment.
In some implementations, a method for managing widgets includes: identifying available widgets for display in a display environment; determining a criteria for selecting ones of the available widgets; and displaying the selected ones of the available widgets.
Other methods, apparatuses, computer-readable mediums and devices having various features are also disclosed.
FIG. 3 is a block diagram depicting a software architecture for previewing, installing, managing and operating widgets in a display environment.
FIG. 4 a is a screen shot depicting a desktop user interface prior to activation of a dashboard.
FIG. 4 b is a screen shot depicting an initial state for a dashboard.
FIG. 4 c is a screen shot depicting a configuration bar for a dashboard.
FIG. 4 d is a screen shot depicting user selection of a widget from the configuration bar.
FIG. 4 e is a screen shot depicting an installation confirmation.
FIG. 4 f is a screen shot depicting a preview of a user interface element that has been selected to be installed.
FIGS. 4 g-4 i illustrate the deletion of widgets from a configuration bar.
FIG. 5 is a block diagram of an installer process.
FIG. 6 is a flow diagram of a process for installing a user interface element in a display environment.
FIG. 7 a illustrates a user interface for a widget manager.
FIG. 7 b illustrates a widget manager confirmation panel associated with deletion of a widget.
FIG. 7 c is a block diagram of a widget manager process.
FIG. 7 d illustrates a user interface for invoking a widget manager.
FIG. 7 e illustrates an alternative user interface for invoking a widget manager.
FIG. 7 f illustrates a user interface for a widget management window.
FIG. 7 g illustrates a user interface for use in sorting widgets.
FIG. 7 h illustrates an alternative user interface for a widget management window.
FIG. 7 i illustrates a user interface for deleting widgets.
FIG. 7 j shows a method for managing widgets.
FIG. 7 k shows an alternative method for managing widgets.
FIG. 8 a shows an alternative method for managing widgets.
FIG. 8 b shows a method for managing a subset of widgets.
FIG. 8 c shows a method for managing widgets including privilege processing.
FIG. 8 d shows a method for displaying widgets based on classification.
FIG. 8 e shows an alternative method for managing widgets.
FIG. 1 is a block diagram of a hardware architecture 100 for previewing, installing, managing and operating widgets in a dashboard. The architecture 100 includes a personal computer 102 coupled to a remote server 107 via a network interface 116 and a network 108 (e.g., local area network, wireless network, Internet, intranet, etc.). The computer 102 generally includes a processor 103, memory 105, one or more input devices 114 (e.g., keyboard, mouse, etc.) and one or more output devices 115 (e.g., a display device). A user interacts with the architecture 100 via the input and output devices 114, 115.
While dashboards and widgets are described herein with respect to a personal computer 102, it should be apparent that the disclosed implementations can be incorporated in, or integrated with, any electronic device that is capable of using widgets, including without limitation, portable and desktop computers, servers, electronics, media players, game devices, mobile phones, email devices, personal digital assistants (PDAs), embedded devices, televisions, etc.
A system and methods are provided for managing widgets. The systems and methods can be stand alone, or otherwise integrated into a more comprehensive application. In the materials presented below, an integrated system and method for previewing, installing, managing and operating widgets and dashboards is disclosed. However, one of ordinary skill in the art will recognize that the engines, methods, processes and the like that are described with respect to the management of widgets can themselves be an individual process or application, part of an operating system, a plug-in or the like. In one implementation, the system and methods can be implemented as one or more plug-ins that are installed and run on the personal computer 102. The plug-ins are configured to interact with an operating system (e.g., MAC OS� X, WINDOWS XP, LINUX, etc.) and to perform the various dashboard, management and widget functions, as described with respect of FIGS. 2-7. A system and method for previewing, installing, managing and operating widgets and dashboards can also be implemented as one or more software applications running on the computer 102. Such a system and method can be another widget that is configurable to communicate with other widgets, applications and/or operating systems. Such a system and method can also be characterized as a framework or model that can be implemented on various platforms and/or networks (e.g., client/server networks, stand-alone computers, portable electronic devices, mobile phones, etc.), and/or embedded or bundled with one or more software applications (e.g., email, media player, browser, etc.).
For illustrative purposes, in the following description the invention is described as a feature of an operating system 305 (FIG. 3) for use in installing and managing widgets in a dashboard environment; however, one skilled in the art will recognize that the techniques of the present invention can be implemented in other contexts as well, including those described above, to install and manage other elements, and in other environments including environments associated with applications or operating systems (e.g., a desktop environment, a display environment associated with a browser executing on a mobile communication device, etc.). Examples of other environments include e-mail environments, desktop environments, application environments, hand-held display environments, and other display environments.
FIG. 2 is a flow diagram of an implementation of a process for activating and using a dashboard. A dashboard layer (also referred to herein as a “unified interest layer” or “dashboard”) is used to manage and display widgets. A user can invoke a dashboard (202) by hitting a designated function key or key combination, or by clicking on an icon, or by selecting a command from an onscreen menu, or by moving an onscreen cursor to a designated corner of the screen. In response to such user input, the current state of the user interface is saved (203), the user interface is temporarily inactivated (204), an animation or effect is played or presented to introduce the dashboard (205) and the dashboard is displayed with one or more widgets (206). If applicable, a previous state of the dashboard is retrieved, so that the dashboard can be displayed in its previous configuration.
The user interacts with and/or configures widgets as desired including managing the display of the widgets in the display environment (207). In some implementations, the user can move widgets around the screen, and can resize widgets if applicable. A user can enable certain widgets from a list of available widgets, retrieve, preview, install, import, export, email, or otherwise manage the widgets. Widget management is discussed in greater detail below.
In some implementations, the dashboard is automatically dismissed (i.e., without user input) after some predetermined period of time or in response to a trigger event. An animation or other effect is played or presented to provide a transition as the dashboard is dismissed (209). When the dashboard is dismissed, the current configuration or state of the widgets (e.g., position, size, etc.) can be stored, so that it can be retrieved the next time the dashboard is activated. In some implementations, an animation or effect is played or presented when re-introducing the UI. The UI is restored to its previous state (210) so that the user can resume interaction with software applications and/or the computer operating system.
In some implementations, the dashboard is configurable. The user can select a number of widgets to be displayed, for example, by dragging the widgets from a configuration bar (or other user interface element) onto the dashboard, or by selecting widgets to be enabled from a list of available widgets using a management presentation window. Management presentation windows are discussed in greater detail below. The configuration bar can include different types of widgets, and can be categorized and/or hierarchically organized. In some implementations, in response to the user dragging a widget onto the configuration bar, the widget is downloaded from a server and automatically installed (if not previously installed). In some implementations, certain widgets must be purchased, so the user is requested to provide a credit card number or some other form of payment before the widget is installed on the user's machine. In some implementations, widgets are already installed on the user's machine, but are only made visible when they have been dragged from the configuration bar onto the dashboard or enabled (e.g., by checking an enable box associated with a given widget in a UI presented by a widget manager). The configuration bar is merely an example of one type of UI element for configuring the dashboard. Other configuration mechanisms can be used, such as a widget manager, an icon tray, or menu system.
FIG. 3 is a block diagram of a software architecture 300 for implementing one or more dashboards, and displaying and managing widgets. The software architecture 300 generally includes a dashboard server 301, one or more dashboard clients 302, an operating system 305 and one or more widgets 303. The server 301 and/or clients 302 use dashboard configuration information 304 to specify configuration options for displaying the widgets 303, including access levels and the like (if applicable). Such configuration information can include information for two or more dashboards configured by the same user or by different users.
In some implementations, the widgets 303 are displayed using HTML and related web technology. The dashboard server 301 can manage and launch the dashboard client 302 processes. In one implementation, each dashboard client 302 loads a widget 303 (e.g., an HTML webpage) and related resources needed to display the page. In some implementations, the dashboard clients 302 display the widgets 303 without a conventional window frame, menu bar, or other components typically associated with on-screen windows. This technique provides a clean, straightforward display of the overall dashboard to reduce confusion and clutter. One or more dashboard clients 302 can display their respective widgets 303 by rendering web pages into a “WebView,” as described in U.S. patent application Ser. No. 11/148,010, entitled “Preview and Installation of User Interface Elements in a Display Environment.” The size of each WebView is defined as metadata associated with the corresponding widget 303. The server 301 provides data for rendering a separate layer that can be overlaid on the normal desktop of the user interface. The widgets 303 are rendered into the separate layer which, in one implementation, is drawn on top of the normal desktop, so as to partially or completely obscure the desktop while the dashboard is active.
The dashboard server 301 can be a stand-alone process, embedded in another process, or part of the operating system 305. The server 301 can be located at the computer 102 or at the remote server 107. In some implementations, the server 301 provides functionality for one or more processes, including but not limited to: non-widget UI management, window management, fast login, event management, loading widgets, widget arbitration, Core Image integration and widget preference management, as described in U.S. patent application Ser. No. 11/148,010, entitled “Preview and Installation of User Interface Elements in a Display Environment.”
The Info.plist files describe a widget 303 and provide an identifier for a widget 303. Table I provides an example of Info.plist file contents.
FIG. 4 a depicts a desktop user interface 400 prior to activation of a dashboard. The desktop user interface 400 (also referred to herein as “desktop”) is a conventional user interface as may be provided by an operating system, such as Mac OS�. The desktop 400 has a background image, menu bar 401, and other standard features. As is known in the art, the desktop 400 may also include windows, icons, and other elements (not shown). The user activates the dashboard by selecting an item from a menu, or by clicking on an icon, or by pressing a function key or key combination, or by some other means for invoking activation.
FIG. 4 b depicts an initial state for a dashboard layer 402. In some implementations, a configuration bar icon 403 is initially displayed. Alternatively, upon activation the dashboard layer 402 can display one or more default widgets 405, 407. If the dashboard layer 402 has previously been activated and configured, the widgets 405, 407, can be displayed as previously configured. As shown in FIG. 4 b, the dashboard layer 402 is not necessarily visible as a distinct layer. However, its various components (such as widgets, icons, and other features) are visible. In some implementations, these components are displayed in a transparent layer, thus maintaining the visibility of the desktop 400 to the user. In some implementations, the desktop 400 and its components are darkened (or blurred, or otherwise visually modified) while the dashboard layer 402 is active, so as to emphasize that the desktop 400 is temporarily inactive. In other implementations, the desktop 400 is not visible while the dashboard layer 402 is active. The user can reactivate the desktop 400 and dismiss the dashboard layer 402 by clicking on an area of the screen where no dashboard element is displayed (i.e., “negative space”). In some implementations, other commands, key combinations, icons, or other user input can be used to dismiss the dashboard layer 402.
Alternative Implementation of Configuration Bar
FIGS. 4 g-4 i illustrate an alternative implementation for deleting a widget from a configuration bar 416. For example, when a user moves a cursor onto the “calculator” label (e.g., a mouse-over) associated with a calculator widget 418, the label is highlighted or otherwise altered, and a delete mechanism (e.g., a delete button) is displayed. If the user clicks or otherwise invokes the delete mechanism, a confirmation overlay 420 is displayed asking the user to confirm the removal and/or deletion of the “calculator” widget. In some implementations, the confirmation overlay 420 is semi-translucent. If the user requests deletion (e.g., clicking the “yes” button), then the calculator widget 418 is removed from the configuration bar 416, as shown in FIG. 4 i. Installation of Elements
Elements, including user interface elements such as widgets can be installed in a display environment as discussed below. One display environment, a dashboard, will be used for illustrative purposes. Installation can include a preview operation. Installation can include selection of the element, such as by a drag and drop action. Other selection means can be used. In one example, a user can drag widgets from configuration bar 408 onto the surface of the dashboard (in other words, anywhere on the screen), using standard drag-and-drop functionality for moving objects on a screen. Alternatively, the user can select widgets by selecting particular ones of the widgets to be enabled in management presentation window as is discussed in greater detail below.
FIG. 4 d depicts the selection of a calculator widget icon 410 from the configuration bar 408. A calculator icon 410 associated with a calculator widget 409 is highlighted, or otherwise augmented or embellished, to indicate that it has been selected by a user with cursor 411.
In some implementations, an animation, such as a ripple animation, is shown when the user “drops” a widget by releasing a mouse button (or equivalent input device) to place a widget at the desired location. In one implementation, the dragging of the widget to the dashboard invokes an installation process for installing the widget including previewing. After installation, the user can move a widget, to any other desired location, or can remove the widget from the screen, for example by dragging it off the screen, or dragging it back onto the configuration bar 408, by invoking a remove command, disabling a widget in a menu associated with a widget manager or canceling the installation during the preview. In some implementations, the position, state, and configuration of a widget are preserved when the dashboard layer 402 is dismissed, so that these characteristics are restored the next time the dashboard layer 402 is activated.
In some implementations, widgets and/or dashboards (including widgets) can be installed from within a running application. For example, a widget and/or dashboard (including widgets) can be an attachment to an email. When the user clicks the attachment, an installation process is invoked for the widget and/or dashboard which can also include a preview.
Widgets can be installed, managed and/or instantiated using an installer process. The installer process can include a separate user interface or an integrated user interface (e.g., integrated in the display environment or separate from the display environment for example in another display environment associated with another application, such as an email application) for selecting, installing and managing widgets in a display environment. Thus, the installation area for the widget can be embedded within an application display area or window. For example, if a user receives a widget as an attachment to an email, the user can invoke and install the widget from within the email message window without the need for a separate installation window.
Installation processes for widgets are described in U.S. Provisional Patent Application Ser. No. 60/734,016, entitled “Preview including Theme Based Installation of User Interface Elements in a Display Environment,” including additional functionality related to preview, security, themes and deletion functionality. The installer process can include management functionality. Alternatively, a separate management process can be provided. As used herein, the term “process” refers to a combination of functions that can be implemented in hardware, software, firmware or the like. By way of example, an installer based implementation is discussed below. Other variations are possible.
Installer Process Engines Including Management Engine
By way of example, management functions for managing various aspects of the display of widgets in a display environment can be incorporated in an installer process. FIG. 5 is a block diagram of an installer process 500 for installing widgets in a display environment, including a selection engine 543, a security engine 544, a preview engine 545, a theme engine 546, an installation engine 547 including a management engine 548, and a deletion engine 549.
Selection Engine
The selection engine 543 is used to select and present (e.g., a static presentation) a widget for installation. The selection engine 543 can be invoked in a display environment and can produce an installation area (e.g., a dialog, a panel, a window, etc., and hereinafter referred to as an “installation window”), that acknowledges the user's initiation of the installer process. The installation window can include a presentation of a selected widget (or a reference thereto as described below), along with various buttons that may be activated by the user or otherwise to invoke functionality in the installer process.
In some implementations, the installation window 450 is invoked by clicking on a widget file or package. For example, a weather widget file 413 (e.g., “weather.wdgt”) can be downloaded to the desktop 400 from a web site. When the user double clicks the “weather.wdgt” file with cursor 411, the installation window 450 is displayed in the dashboard layer 402, as shown in FIG. 4 e. Security Engine
The security engine 544 is used to determine a security access level (or risk level, or both) for either the user or the element to be installed. Security engine 544 can be used to limit the ability of the user to install particular kinds of elements (e.g., based on categories or criteria). In addition or alternatively, security engine 544 is used to determine a security access level (or risk level or both) of an element to be installed. Based on the security access/risk level, one or more operational or functional constraints can be placed on the element during the preview process. For example, limitations on the ability of the previewed element to interact, access, read or write data, monitor output of other system resources, access other system resources, or other limitations can be invoked. The invocation can be temporary, for a predetermined time period, or until the preview has terminated and completed (non-limited) installation has been performed. Functionality or operations of the element can be enabled or disabled, depending on the access level. The security engine 544 can use metadata associated with the element to be installed, user input, contextual information, file type information, default data, read/write preferences, cookies and/or other information to determine the access/risk level. Access control lists including white lists (e.g., including lists identifying certified or otherwise safe elements), black lists (e.g., including lists identifying un-certified or otherwise un-safe elements) and the like can be used to determine the access/risk level.
Various techniques for widget security are described in U.S. Provisional Patent Application No. 60/730,956, entitled “Widget Security,”.
The preview engine 545 is used to preview (e.g., dynamically) an element (e.g., a widget) that has been selected to be installed. Referring again to FIG. 4 f, the preview engine 545, when invoked, provides an area (hereinafter “a presentation area or presentation window 462” or specifically a “widget window” when used to display a widget) into which the selected element can be displayed. Preview is discussed in greater detail in U.S. patent application Ser. No. 11/148,010, for “Preview and Installation of User Interface Elements in a Display Environment.”
Associated with the preview is a preview designator 464. In one implementation, the preview designator 464 is displayed along with the user interface element being installed (e.g., widget). The preview designator 464 can be of the form of a frame, a carpet on which the presentation window 462 is disposed, a preview theme element, or other designator that overlays, surrounds, bounds or otherwise is associated with the presentation window 462. The combination of the presentation window 462 and the preview designator 464 comprise an installation area for the user interface element to be installed. The installation area can be part of the display environment in to which the element is to be installed (e.g., part of the dashboard) or part of a separate display environment (e.g., part of another user interface, another user interface element, another application, or process, etc.).
When displaying a fully interactive widget in the presentation window 462, user input can be accepted that can result in changes in the presentation. For example, if the widget includes a URL that may be linked to, interaction can include the generation of an underlying page request and the presentation of the requested page in the presentation window 462. Interaction with user interface elements is described in U.S. patent application Ser. No. 11/145,561, for “Application Clipper.” If the interaction is not allowed, a display prompt can be shown to indicate that the operation or function is temporarily disabled during the preview operation.
In some implementations, a window manager 550 is associated with the preview engine 545. The window manager 550 can be a separate process that is used to support the interaction between the presentation window 462, preview designator 464 and the installation window 460 described above. Window management is described in greater detail in U.S. Provisional Patent Application Ser. No. 60/734,016, for “Preview including Theme Based Installation of User Interface Elements in a Display Environment.”
Theme engine 546 is operative to provide additional content to accompany the content displayed in the presentation window or installation window. The theme engine 546 is operative to determine a theme to be associated with an item to be installed (e.g., a widget), identify additional content for concurrent display, and facilitate the display of the additional content. Additional content can be of the form of a frame that is used to bound the item to be installed on one or more sides. Examples of additional content include a picture frame, a content player (e.g., a video player, a still image player, etc.). The additional content can be static or include functional elements (e.g., buttons, for example to play content). Themes and processes associated therewith are discussed in greater detail in “Preview including Theme Based Installation of User Interface Elements in a Display Environment.”
The installation engine 547 is operative to install/instantiate the selected widget in the display environment. The installation engine 547 can copy or move as required the selected widget to an appropriate volume and store the data structures (including preference data, identification data, scripts, navigation data and the like) for use in the display environment. In some implementations, the installation engine 547 includes an automatic invocation of the underlying display environment with the installed user interface element presented (i.e., the installation engine 547 installs the widget in, and opens up, a dashboard including the installed widget in a preview mode). Associated with the installation engine 547 can be a management engine 548 for managing all aspects of control and presentation of widgets. Management engines are discussed in greater detail below.
Deletion Engine
The deletion engine 549 provides control for widgets after installation. The deletion engine 549 can be a separate process from the installer process 541, or included therein. The deletion engine 549 can receive input and display user interface elements (dialogs and the like) to ensure that deletion operations are effectuated as required. The deletion engine 549 can be responsive to the selection of a user interface element, a portion of the element, controls associated with the element and the like.
In some implementations, the installer process 541 is part of a separate process that is not associated with a dashboard. Alternatively, the installer process 541 can be part of a dashboard application and be activated, by for example, by selecting a widget for addition to the dashboard, or by selecting a management or installation icon or the like. Selection can include for example double clicking on a widget displayed in a configuration bar 408, selecting a widget for import from another system or environment and the like (shown in FIG. 4 c). Other installation tools are possible.
In a dashboard environment, one or both of the installer process 541 or management process including management functions discussed below can include either or both of a widget bar and a management palette and an associated installer process. The installer process when invoked can cause the display of the widget bar or the management palette in the user interface. In one implementation, the dashboard itself, as currently configured can also be displayed when the installer process is invoked. The installer process can then be invoked to select available widgets for installation/enablement, preview widgets, or remove installed widgets (e.g., remove widgets from the widget bar) depending on the configuration of the installer process.
In a desktop environment, installer process 541 or management process can be of the form of an application that can be invoked (automatically, by the user, by the operating system, by an application or other invocation tool) to present user interface elements that are available to be installed/enabled in the desktop environment. The installer application can include one or both of a user interface element bar and a management palette and an associated installer process. The installer process when invoked can cause the display of the user interface element bar and/or management palette in the user interface. The installer process can then be invoked to select available user interface elements for installation/enablement, preview user interface elements, or remove installed user interface elements (i.e., remove user interface elements from the user interface elements bar) depending on the configuration of the installer process.
FIG. 6 is a flow diagram of a process for installing a user interface element (e.g., a widget) in a display environment. The process includes identifying a user interface element (602). Identifying the user interface element can include locating a widget. Locating can include using a search tool or the like to locate widgets available for installation. Alternatively, other methods can be used for identifying user interface elements for installation including automatic and user controlled identification methods. Available widgets can be presented in a list, e.g., by a management process as is shown below.
The prompt can be of the form of a confirmation to the user of the underlying action (e.g., prompt 458). In one implementation the prompt can be used to confirm a desire to install a named widget. In other implementations, the prompt can be used to confirm not only the named user interface element for installation, but the display environment into which the user interface element will be installed (e.g., “Install named widget #1 on my desktop?” or “Install widget #1 on dashboard #1 of 2?”). In still other implementations, the prompt can include a confirmation of an action (e.g., “install the widget and open it in my dashboard”).
Continuing with the method, if a preview option is selected or required (optional), then a preview of the widget in a preview environment is created and presented (606). The creation of the preview environment can include the invocation of a window management engine (e.g., window manager 550) for managing the interaction of one or more windows that make up the preview. In some implementations, the preview includes a presentation window (e.g., presentation window 462) and a preview designator (e.g., preview designator 464) that are separate processes. The presentation window is used to display an instantiation of the selected widget. In some implementations, the display of the presentation window includes an instantiation of the selected widget in a selectable interactive environment. The preview designator is provided to clearly indicate that the preview operation is being performed, as opposed to a conventional direct installation. In some implementations, the preview is presented at a same location in the user interface. Alternatively, if other elements are present at this location, another location or a temporary overlay can be used. In some implementations, the preview designator is a carpet, onto which the presentation window is laid (e.g., layered, overlaid, or the like).
In some implementations, theme content can be presented along with the user interface element in the preview installation window. The theme content can include a theme presentation element that operates as the preview designator (e.g., additional content that is recognized as being part of a preview of an item, for example a preview Title or the like). Other theme content can be presented to preview how the final installed version of the user interface element will appear. For example, assuming a theme border is to be presented with the user interface element at installation, the preview can include the same theme border.
Finally, the user interface element can be installed (608). The installation of the user interface element can include the installation on a tool bar (e.g., a widget bar), in a resource, in a widget manager (e.g., in a list managed by a widget management process) or in a display environment (e.g., directly on a dashboard or the desktop). Installation can include the saving of the underlying content metadata including data structures defining the user interface element in a library or the like. Alternatively, the installation can be part of an underlying application (e.g., directly in an associated dashboard application or a library associated therewith). In some implementations, the installation of the user interface element includes the removal of the preview designator. For example, where a carpet is used to designate the preview, the carpet can be removed for the final installation. In one implementation, the final installation is performed at a same location in the user interface as the preview. In some implementations, an animation or other transition effect can be used when moving from preview to final installed user interface elements. Transitions can include the appearance of pulling of a carpet preview designator from under the user interface element or otherwise making the carpet disappear.
Once installed, user interface elements can be removed/deleted, enabled and disabled from the display environment as required. In some implementations, a separate deletion process and/or management process is provided from the installation process. Alternatively, the installer process can be invoked to remove/delete and enable/disable user interface elements as required.
Widget Searching
In some implementations, widgets are associated with a widget data type or other metadata to enable a search engine (e.g., Apple's Spotlight� search engine) to search for widgets in files, documents, images, emails, applications, etc. Widgets can be indexed based on data type and/or other metadata. For example, a query can be generated requesting a list of all widgets on a host machine and/other machines on a network. The search engine accesses the index to locate widgets on the host machine and/or other machines on a network.
As the number of widgets presented in a display environment increases, the need for a tool to organize, and manage widgets (both new and old) arises. In some implementations, a widget manager can be provided to manage installation, access control, security, content control, historical archive, revision, classification, deletion, organization, enablement, placement, importation, exportation, and other functions associated with widgets. With the addition of multiple display environments (e.g., multiple dashboards), the widget manager can provide these and other functions across the multiple display environments to ensure easy of use, flexibility, and customization of each display environment. Below, a number of examples of widget manager instantiations are described. Those of ordinary skill in the art will recognize that the instantiations are exemplary of tools that can be used to enhance the user interface experience and that other variations are possible.
In some implementations, the widget manager is a stand alone application that can be invoked by the user to manage, as described above, widgets. Alternatively, the widget manager can be part of an installer engine as described above, part of an operating system (such as MAC OS X), or a plug in. The widget manager can be a separate process or part of another process executing on an electronic device. The widget manager can be invoked directly, automatically or otherwise as required to allow for interaction with a user. Examples are set forth below with regard to a widget manager and widget manager functions. Those of ordinary skill in the art will recognize that other configurations, including custom configurations based on the device or application, and the like are possible.
In some implementations, a widget manager includes a management engine (similar to management engine 548 discussed above) that is operable to present available widgets in a palette of a user interface display environment, selectively enable or disable each of the available widgets and display enabled widgets in the display environment. In some implementations, the management engine is further operable to locate widgets for installation in the display environment. Location can include locating widgets associated with a given user, display environment or context. Location can include locating widgets for importation from other applications (e.g., e-mail attachments and the like), or from other sources (e.g., web sources). In some implementations, the management engine is further operable to install widgets into the display environment. Accordingly, while reference has been made above concerning one possible implementation where management functions are included in an installer process, other implementations are possible including one where installation functions are included as part of a management process. The display environment can be a user interface of an electronic device.
In some implementations, a widget manager allows users to inspect, remove, enable and disable widgets. The widget manager can be a preference pane or palette, a standalone application or a plug-in, or be part of the installer process described above. The widget manager displays widget information, including but not limited to the widget's title, author, version, class, type, ratings, description, etc. The information can be displayed in any order and format according to one or more sorting criteria, such as alphabetical or chronological order, author, class, rating, etc. In some implementations, the widget manager tracks widget updates and automatically notifies the user or host system or device when an update is available.
In some implementations, the widget manager allows users to perform certain actions on widgets, including but not limited to copying, moving, deleting, uninstalling, deactivating, enabling, disabling, renaming, previewing, etc. In some implementations, the widget manager includes functionality that allows the import and export of widgets to and from various widget sources (e.g., network, email, CD ROM, etc.). For example, widgets can be imported and exported to and from a web site that can be accessed by multiple users. In some implementations, the widget manager includes a search field that allows users to search for widgets on a host system or device, and/or one or more networked devices.
In some implementations, the widget manager can be invoked by a button or other input mechanism located in a user interface (e.g., desktop, system tray, dashboard, configuration bar, etc.). For example, when the button is activated, the widget manager is launched and a user interface is displayed. In_some implementations, the widget manager is a widget itself and includes at least some characteristics, attributes or properties of other widgets. For example, the widget manager can be enabled or disabled, resized, dragged and dropped, flipped to reveal special options or preferences, etc.
In some implementations, the widget manager can be displayed in a format that is consistent with a dashboard theme or content. The appearance_and/or properties of the widget (e.g., colors, styles, fonts, etc.) can be changed by a user via a preference pane or other input mechanism.
Example User Interface for a Widget Manager
FIG. 7 a illustrates a user interface 702 for a widget manager. It should be apparent that a user interface for a widget manager can include more or fewer features than shown.
In some implementations, the user interface 702 is displayed in another user interface 700 (e.g., a desktop or dashboard) in response to user input. User input can include, for example, clicking on a button 716 (e.g., a “Manage Widgets” button) or other input mechanism located in the user interface 700. The user interface 702 can be dismissed by clicking on button 722 or other input mechanism.
In some implementations, the user interface 702 includes a scrollable list 706 of widget names and/or other attributes which correspond to widgets that have been installed on the host system. Double clicking on the name of a widget (or an associated icon or button) launches the widget. In some implementations, the scrollable list 706 includes widgets that reside on the host system but have not been installed (e.g., widgets downloaded to a desktop). This implementation enables users to install or launch widgets from within the widget manager. In some implementations, the list 706 includes names of widgets that reside on another device coupled to the host system via a network connection. In some implementations, a search history is maintained to enable the user to refine search terms and/or re-run a previous search. In some implementations, an event history is maintained which allows users to undo and redo previous widget operations.
Optionally, next to each widget is an icon image 710 associated with the widget that can be used to identify the widget and assist the user in selecting the widget from the list 706. Widgets that are selected to be hidden (e.g., based on a “hide widget” option provided in the widget manager) will not be shown in the list.
The widgets can be scrolled using, for example, a scroll bar 712. Users can also toggle each widget on and off (i.e., enable/disable the widget) by selecting a checkbox 708 located to the left of each widget listing. Similarly, on the right side of some widget listings is a button 707 or other input mechanism that allows users to delete the widget. Note that for this example, widgets that cannot be deleted do not have a corresponding button 707. In some implementation, default widgets or widgets that have been locked may not be deleted.
In some implementations, a button 714 (e.g., a button labeled “More Widgets . . . ”) displays more widgets and a search button 713 allows a user to search for more widgets located in local directories or on one or more network devices (e.g., a website) using known search technologies. For example, the user can enter the query “Sports Widgets” in a search box and click the button 713 to initiate a search for Sports Widgets.
In some implementations, when a widget is enabled (check box 708 is checked) the widget's icon image 720 is displayed in a configuration bar 718 in user interface 700. For example, since the check box 708 associated with the “weather widget” is checked, its icon image 720 is displayed in the configuration bar 718 in user interface 700. Similarly, if the check box 708 is unchecked, then the image icon 720 is not displayed or otherwise deemphasized in the configuration bar 718 or its appearance is altered (e.g., grayed out, darkened, made translucent, etc.) to indicate to a user that the widget is disabled.
FIG. 7 b illustrates a widget manager overlay 730 for requesting a user to confirm the deletion of a widget. In some implementations, when clicking the delete button 707 (FIG. 7 a), a semi-translucent overlay 730 appears within the user interface 702 including a message 728 requesting the user to confirm their intent to delete the widget. For example, the message 728 could be “Move this widget to the Trash?” The user can respond to the message 728 by clicking a button 726 (“OK”), which results in the widget being moved to the “Trash” or otherwise deleted from the host system. The user can also respond by clicking a button 724 (“Cancel”), which results in the deletion operation being terminated. If a widget is moved to the “Trash” or otherwise deleted, then its icon image 720 is removed from the configuration bar 718 and list.
Simple Widget Management
Referring now to FIG. 7 c, in one implementation, the widget manager 740 is a process that includes a sorting engine 742, enablement engine 744, a history engine 746 and a presentation engine 748. The widget manager 740 can be a separate computer process, part of an application, or part of the operating system in a computing environment. Though reference has been made that separate engines are provided, the functions of one or more engines can be combined into a single engine or process. For the purposes of clarity of the disclosure, separate engines are described. Other instantiations are possible.
Sorting engine 742 maintains a list 743 of available widgets, in for example a database (not shown). Sorting engine 742 can be used to sort the entries in the list 743, and present the entries in particular orders based on one or more user sort criteria. In one implementation, the list 743 can include information for each widget. The information can be directly or indirectly associated with the widget. For example, information relating to the name, origin, date, version, type (e.g., type of widget selected from clipviews, webviews, accessories, etc,) and other directly related information can be stored in the list 743 or associated with a given widget. Sorting engine 742 can be used to sort the entries in the list 743 to provide a sorted list for presentation by the presentation engine 748 to a user. Other information including historical access data, preferences, and the like can be stored and used as sort criteria. For example, sorting engine 742 can include a separate or integrated process for gathering statistics regarding the use of widgets (most popular, most often accessed, most often accessed in a given context, most recently accessed, and the like). The statistical metadata can be stored in the list 743. Sorting can be invoked by a keystroke, command, automatically based on preferences, or otherwise with user interaction. Sorting is discussed in greater detail below.
Enablement engine 744 is a portion of the manager process that controls which widgets will be provided in a given display environment. Enablement engine 744 receives input from the user either directly or via preferences, to selectively enable ones of the available widgets in a given display environment. Where there is but a single display environment, enablement engine 744 is used to enable selected ones of the available widgets in the display environment. In a multiple display environment setting, enablement engine 744 can be used to selectively enable ones of the available widgets in each of the display environments. Associated with each available widget can be enablement metadata. The enablement metadata can be stored in list 743. The enablement metadata can define the conditions (e.g., display environment, or other conditions) which must be satisfied in order to allow the widget to be displayed in a given display environment. Enablement engine 744 can at the time of launch, or installation of a display environment (e.g., a dashboard), evaluate the enablement data, and enable selected widgets in the display environment.
History engine 746 can be used to maintain historical information relating to widgets in, for example, list 743. Historical information can include use data, snapshot data (reflecting a state of the widget at a given time), version information, statistical information and the like. History engine 746 can be used to review the historical information, reconstruct a historical event (e.g., reconfigure a widget to a default state) or otherwise.
Presentation engine 748 provides a user interface for the widget manager 740. The presentation engine 748 can provide a complete presentation, or one modified based on the display environment. Details of the operation of the presentation manager 748 are discussed below.
In one implementation, the widget manager 740 can be accessed by a keystroke or other command from, for example, the user interface. In one implementation, as shown in FIG. 7 d, the widget manager can be invoked using a button 750 that is located on the user interface, in the example shown, above a configuration bar. In one implementation, the widget manager 740 is itself a widget that is presented in the configuration bar, in a display environment or otherwise that can be activated by user input. For example as shown in FIG. 7 e, the widget manager 740 can be invoked by selecting (e.g., clicking) the widget icon 752 in the configuration bar (e.g., previously referred to as the Widget Bar).
After invocation, a widget management window 760 is presented in the user interface (e.g., by the presentation engine 748) as shown in FIG. 7 f. In some implementations, a full management window is presented. In display environments that are limited by resources, in hardware, software, size or otherwise, a reduced widget management window may be presented. The reduced widget management window can be smaller in size, display less information, or otherwise be optimized to the limited resource environment in which it is displayed. In the implementation shown, widget management window 760 includes a list of widgets 762, and a plurality of input mechanisms (e.g., sort menu 764 and more button 766). Though reference is made to a button, other forms of activating tools are possible including scripts, windows, bars, or other user interface elements. The term button is used generically, and can be accomplished by a variety of means by those of ordinary skill in the art.
Widget list 762 can include a name 770, an icon or image 772, and an enable button 774. In one implementation, the widget list 762 is associated with a list of available widgets (e.g., list 743) that is maintained by the widget manager 740. The list can be maintained in memory associated with the widget manager 740, and called to populate the widget list 762 as required. Alternatively, the widget list 762 can be unique to the user, and represent a subset of the available widgets in the list 743. The determination of which widgets to present can be made based on criteria associated with the user, context or display environment. The name 770 can be the name of the widget, other metadata associated with the widget (e.g., a pointer to a location in memory where the widget is stored, metadata relating to when the widget was installed, where it was installed, what version number, the source of the widget, etc.). Icon 772 can be a representation associated with the widget. The representation can provide a visual clue to the operation of the associated widget (e.g., a calendar widget could have an associated calendar representation). Enable button 774 can be used to selectively enable available widgets in the display environment. Selection of the enable button associated with a given widget marks the widget for enablement at invocation of the display environment. Enable button 774 can be of the form of a check box as described above. Marked widgets can be invoked in the display environment by, for example enablement engine 744. Unmarked widgets can be hidden, not displayed, not installed or otherwise disabled in the display environment at invocation. In one implementation, the widget list 762 can be sorted to show those items that are enabled versus those disabled. Enablement can be controlled by the user, by an administrator, using content guards or filtering technologies as required. For example, widget manager 740 can include a filter that automatically disables ones of the widgets that would otherwise be available based on a criteria (e.g., parent control criteria, access control criteria or otherwise). In one implementation, enablement engine 744 controls access, and hence enablement for individual widgets.
Sort button 764 can be used to sort widget list 762 in the presentation window. Sort button 764 can include a sort criteria selection for defining the sort criteria. The sort criteria can be provided by the user. Alternatively, the sort criteria can be inferred. In one implementation, the sort button 764 can include a plurality of sort options, presented, for example as pull down selections when the sort button is activated as shown in FIG. 7 g. Exemplary sort options include sorting alphabetically, by type, source, preference, use, context, and the like, and sorting automatically based on user provided criteria.
More button 766 can be invoked to display lists, locations (e.g., web locations), stores, suppliers, or otherwise associated with widgets. In one implementation, more button 766 can be a link to a hosting site that provides widgets available for download. When invoked, more button 766 displays additional widgets that are available for installation, or can be used as a browser to locate available widgets.
An alternative implementation for a management window is shown in FIG. 7 h. In the implementation shown, one or more entries in the widget list 762 include an additional button or activatable feature. In the implementation shown, a delete button 768 is included in the user interface. The delete button 768 (shown as a minus sign in one implementation) can be used to remove the widget from the management environment and the computing environment as required. In one implementation, selection of the deletion button 768 provides a prompt to the user to confirm that the widget is to be removed from the widget manager as shown in FIG. 7 i. In one implementation, the widget can be removed from the widget manager list of available widgets and software associated with the widget can be made available for removal (e.g., placed in the trash). In other implementations, a deleted widget is only removed from the management window, and not removed from the computing/display device. In one implementation, only authorized users are able to delete widgets (e.g., an administrator or user with administrator privileges).
Widget Management Including Sorting and Enablement
Referring now to FIG. 7 j, a method is described for managing widgets in a display environment. At invocation, prompt, or otherwise, a list of available widgets is presented in the display environment 770. The list of available widgets can be drawn from a file of widgets stored on the device. At the time of presentation, the list is sorted in accordance with a user preference or with default preferences 772. Enabled widgets can be designated in the presentation 774. A user selection for sorting, enabling, disabling, or otherwise manipulating the list can be received 776. Otherwise manipulating can include viewing information associated with one or more of the widgets in the list. Responsive to the user selection, the list can be managed to reflect the user selection including enabling, disabling, deleting or otherwise processing the widgets in the list 778. Other user selections can be processed 777 until a deactivation event is sensed 780. At deactivation, the list can be stored including any changed data for future retrieval.
Widget Management Including Instantiation of Widgets
Referring now to FIG. 7 k, in one implementation, a method of managing widgets for display in a display environment includes presenting a list of available widgets 785 and receiving user input to enable one or more widgets to be displayed in the display environment 787. The method includes indicating in the list which widgets are enabled and to be displayed in the display environment from the available widgets 789. At run time, the method includes instantiating each enabled widget in the display environment 791. Presenting the list of available widgets can include presenting a link to a location where widgets can be downloaded and sorting the list. Presenting can also include indicating in the list which widgets are disabled and will not be displayed at run time.
Widget Management Including Usage Criteria Presentation
Referring now to FIG. 8 a, in another implementation, a method of managing widgets for display in a display environment includes determining usage information for widgets when displayed in a display environment 801 and determining usage criteria associated with the presentation of widgets in the display environment 803. The method includes selectively enabling and disabling at least one widget from the available widgets based on the usage criteria and the usage information 805 and displaying enabled widgets in the display environment 807. Usage information can be related to a single user or to a plurality of users. For example, the usage information can include usage statistics relative to the individual user, or a pre-defined group of users. In one implementation, the usage information includes an indication of when a given widget was last activated. The usage criteria can define how to use the usage information. For example, in one implementation, the usage criteria can include information on how often the usage information is to be evaluated.
Widget Management Including Enabling a Subset of Widgets
Referring now to FIG. 8 b, in another implementation, a method is provided for managing a subset of widgets in a given display environment. The method includes presenting a list of available widgets in a user interface 820, enabling a subset of the available widgets 822 and displaying the subset in a display environment of the user interface 824. The method can include selecting a widget from the list of available widgets and sending the widget to another user. Sending can include sending the widget using a transfer protocol (e.g., mail protocol or a file transfer protocol). The method can include storing a copy of at least one enabled widget to guard against file corruption. The method can further include downloading a widget from an external source and installing the downloaded widget. Installing the downloaded widget can include previewing the downloaded widget in a display environment. Downloading the widget can also include determining user privileges including classification privileges, determining a type of the widget and enabling the download only if the classification privileges allow downloading of widgets of the determined type.
The method can include selectively controlling user configuration of available widgets including controlling one or more of enabling, editing, removing, or disabling widgets. The method can include storing historical configuration data for one or more of each widget or a selected subset of widgets.
Widget Management Including Privilege Processing
Referring now to FIG. 8 c, in one implementation, a method of managing widgets includes privilege processing. Privilege processing as used herein, refers to consideration of the privileges associated with a given user to make presentation decisions relative to the number, or kind of widgets that are available for instantiation in a display environment. The method includes determining user privileges 830, presenting a list of available widgets based on the user privileges 832, enabling a subset of the available widgets based on user privilege 834 and displaying enabled widgets in a display environment 836.
Determining user privileges can include authenticating the user. The method can further include loading of a new widget for display, verifying privileges of the user prior to display of the new widget and selectively enabling or disabling display of the new widget based on the user privileges. Presenting a list of available widgets can include determining a type of each widget and making available only widgets having types that are consistent with the user privileges. The type can be based on content displayed by the widget. Presenting a list of available widgets can include rating each widget and making available only those widgets having ratings that are consistent with the user privileges.
Widget Management Using Classification Data
Referring to FIG. 8 d, in another implementation, particular widgets for display can be determined based on classification. Classification can relate to content associated with or displayed by a given widget. Classification can also relate to type of widget in terms of functionality (e.g., webviews, or widgets able to retrieve pages from the internet). Other classification criteria are possible including classifications based on usage, popularity, preference or otherwise. Classification data can be derived by the system or be provided or otherwise associated with a given widget. A method for managing widgets based on classification can include determining widgets that are available for display 840, classifying the available widgets 842, presenting the available widgets according to the classification 844, selectively enabling ones of the available widgets 846, and, at run time, displaying enabled widgets in a display environment 848.
Classifying the available widgets can include sorting the available widgets in accordance with criteria. The criteria can be based on usage of the available widgets or type of widget. Methods associated with criteria selection are discussed below.
In another implementation, a method for managing widgets includes identifying available widgets for display in a display environment, determining criteria for selecting ones of the available widgets and displaying the selected ones of the available widgets. The criteria can be a random selection or based on usage data associated with the available widgets or be defined by the user.
Widget Management in a Dedicated Management Environment Including Geometry Presentation
As discussed above, the management of widgets can be accomplished as a separate process, or within the confines of another process, such as an installer process. In a management environment, administrative and user roles can be provided. Further, in a management environment, customized management tools can be provided to assist either the administrator or the user in the deployment and maintenance of widgets in a given display environment. One example of a custom tool is a geometry tool. A geometry tool can be used to organize the presentation of widgets in the display environment. The geometry tool can have associated display geometry that defines how widgets are to be displayed. The display geometry can include patterns or the like for defining the presentation of enabled widgets in the display environment. Examples include a clock pattern, a square pattern, a three dimensional cube or other patterns. As such, a separate process that focuses just on the management functionalities can be beneficial. In the implementation shown in FIG. 8 e, a method of managing widgets includes identifying available widgets for display in a display environment 850, presenting the available widgets in a management environment 852, selectively enabling ones of the available widgets 854, and displaying enabled widgets in the display environment 856.
Displaying enabled widgets can include controlling placement of each widget in the display environment in accordance with a display geometry. The display geometry can define a location for each widget in the display environment. The method can include identifying a new widget for installation, installing the new widget including previewing the new widget in a location in the display environment defined by the display geometry, and selectively installing the new widget after the preview including adding the new widget in the presentation of the available widgets.
Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS4752893Nov 6, 1985Jun 21, 1988Texas Instruments IncorporatedGraphics data processing apparatus having image operations with transparent color having a selectable number of bitsUS5168441May 30, 1990Dec 1, 1992Allen-Bradley Company, Inc.Methods for set up and programming of machine and process controllersUS5289574Sep 17, 1990Feb 22, 1994Hewlett-Packard CompanyMultiple virtual screens on an "X windows" terminalUS5297250Jan 30, 1992Mar 22, 1994Bull, S.A.Method of generating interfaces for use applications that are displayable on the screen of a data processing system, and apparatus for performing the methodUS5351995Jan 29, 1992Oct 4, 1994Apple Computer, Inc.Double-sided, reversible electronic paperUS5357603Jun 15, 1992Oct 18, 1994Microsoft CorporationMethod and system for changing a shape type while maintaining existing graphic characteristicsUS5388201Aug 11, 1993Feb 7, 1995Hourvitz; LeonardMethod and apparatus for providing multiple bit depth windowsUS5416890Dec 11, 1991May 16, 1995Xerox CorporationGraphical user interface for controlling color gamut clippingUS5481665Jul 14, 1992Jan 2, 1996Institute For Personalized Information EnvironmentUser interface device for creating an environment of moving parts with selected functionsUS5490246Aug 23, 1994Feb 6, 1996Xerox CorporationImage generator using a graphical flow diagram with automatic generation of output windowsUS5522022Nov 24, 1993May 28, 1996Xerox CorporationAnalyzing an image showing a node-link structureUS5537630Dec 5, 1994Jul 16, 1996International Business Machines CorporationMethod and system for specifying method parameters in a visual programming systemUS5564022Feb 9, 1994Oct 8, 1996Intel CorporationMethod and apparatus for automatically inserting clock buffers into a logic block to reduce clock skewUS5588098Jun 7, 1995Dec 24, 1996Apple Computer, Inc.Method and apparatus for direct manipulation of 3-D objects on computer displaysUS5602997Jun 7, 1995Feb 11, 1997Starfish Software, Inc.Customizable program control interface for a computer systemUS5638501May 10, 1993Jun 10, 1997Apple Computer, Inc.Method and apparatus for displaying an overlay imageUS5644737 *Jun 6, 1995Jul 1, 1997Microsoft CorporationMethod and system for stacking toolbars in a computer displayUS5644739Jan 27, 1995Jul 1, 1997Microsoft CorporationMethod and system for adding buttons to a toolbarUS5651107Aug 16, 1994Jul 22, 1997Sun Microsystems, Inc.Method and apparatus for presenting information in a display system using transparent windowsUS5657049Jun 7, 1995Aug 12, 1997Apple Computer, Inc.Desk drawer user interfaceUS5659693Jun 7, 1995Aug 19, 1997Starfish Software, Inc.User interface with individually configurable panel interface for use in a computer systemUS5659694Jun 30, 1994Aug 19, 1997Canon Kabushiki KaishaMethod and system for displaying context sensitive child windows independently of their parent windowUS5671343Dec 9, 1994Sep 23, 1997Canon Kabushiki KaishaThree-dimensional modeling apparatus and method utilizing the extraction of topological data, as from two-dimensional drawingsUS5689664Apr 14, 1995Nov 18, 1997Microsoft CorporationInterface sharing between objectsUS5708764Sep 10, 1996Jan 13, 1998International Business Machines CorporationHotlinks between an annotation window and graphics window for interactive 3D graphicsUS5721848Aug 7, 1996Feb 24, 1998Oracle CorporationMethod and apparatus for building efficient and flexible geometry management widget classesUS5727135 *Aug 2, 1996Mar 10, 1998Lexmark International, Inc.Multiple printer status information indicationUS5731819Jul 18, 1995Mar 24, 1998SoftimageDeformation of a graphic object to emphasize effects of motionUS5742285Apr 18, 1997Apr 21, 1998Fujitsu LimitedVirtual screen display systemUS5754174Nov 4, 1996May 19, 1998Starfish Software, Inc.User interface with individually configurable panel interfaces for use in a computer systemUS5760773Jan 6, 1995Jun 2, 1998Microsoft CorporationMethods and apparatus for interacting with data objects using action handlesUS5764229May 9, 1996Jun 9, 1998International Business Machines CorporationMethod of and system for updating dynamic translucent windows with buffersUS5764238Sep 10, 1993Jun 9, 1998Ati Technologies Inc.Method and apparatus for scaling and blending an image to be displayedUS5790120Sep 12, 1996Aug 4, 1998Starfish Software, Inc.Individually configurable panel user interface with selective launching, sticky windows, hot keys, start up options and configurable backgroundUS5793376Nov 30, 1995Aug 11, 1998Sony CorporationMethod of producing image data, image data processing apparatus, and recording mediumUS5796402Mar 8, 1996Aug 18, 1998Microsoft CorporationMethod and system for aligning windows on a computer screenUS5801703Oct 18, 1996Sep 1, 1998Island Graphics CorporationMethod and apparatus for selectably expandable menusUS5809230Jan 16, 1996Sep 15, 1998Mclellan Software International, LlcSystem and method for controlling access to personal computer system resourcesUS5835692Mar 24, 1997Nov 10, 1998International Business Machines CorporationSystem and method for providing mapping notation in interactive video displaysUS5835693Jul 22, 1994Nov 10, 1998Lynch; James D.Interactive system for simulation and display of multi-body systems in three dimensionsUS5838316Jan 26, 1996Nov 17, 1998International Business Machines CorporationMethod and system for presenting a plurality of animated display objects to a user for selection on a graphical user interface in a data processing systemUS5870734Dec 2, 1996Feb 9, 1999Hewlett-Packard CompanyThree-dimensional file system using a virtual node architectureUS5877741Apr 19, 1996Mar 2, 1999Seiko Epson CorporationSystem and method for implementing an overlay pathwayUS5877762Sep 8, 1997Mar 2, 1999Apple Computer, Inc.System and method for capturing images of screens which display multiple windowsUS5878219Mar 12, 1996Mar 2, 1999America Online, Inc.System for integrating access to proprietary and internet resourcesUS5883639Jul 3, 1997Mar 16, 1999Hewlett-Packard CompanyVisual software engineering system and method for developing visual prototypes and for connecting user code to themUS5900876Apr 10, 1996May 4, 1999Canon Kabushiki KaishaInformation processing apparatus and method with display book page turningUS5903896Jul 15, 1997May 11, 1999Microsoft CorporationMethod for installing a file on demand using a previewUS5920659Jun 24, 1996Jul 6, 1999Intel CorporationMethod and apparatus for scaling image data having associated transparency dataUS5929852Jan 15, 1998Jul 27, 1999Apple Computer, Inc.Encapsulated network entity reference of a network component systemUS5933148Nov 30, 1995Aug 3, 1999Sony CorporationMethod and apparatus for mapping textureUS5949409Nov 30, 1995Sep 7, 1999Sony CorporationImage processing in which the image is divided into image areas with specific color lookup tables for enhanced color resolutionUS5963191Mar 25, 1997Oct 5, 1999International Business Machines CorporationMethod and system for denying graphical pointer access to a widget of a data processing system graphical user interfaceUS5978579Aug 12, 1997Nov 2, 1999International Business Machines CorporationArchitecture for customizable component systemUS5999948Sep 3, 1997Dec 7, 19993Com CorporationDynamic configuration forms in network management softwareUS6005568Sep 30, 1997Dec 21, 1999The United States Of America As Represented By The Secretary Of The NavyComputer system providing platform independent universal client deviceUS6006231Sep 10, 1997Dec 21, 1999Warp 10 Technologies Inc.File format for an image including multiple versions of an image, and related system and methodUS6011562Feb 23, 1998Jan 4, 2000Avid Technology Inc.Method and system employing an NLE to create and modify 3D animations by mixing and compositing animation dataUS6031937May 19, 1994Feb 29, 2000Next Software, Inc.Method and apparatus for video compression using block and wavelet techniquesUS6045446May 6, 1999Apr 4, 2000Konami Co., Ltd.Object-throwing video game systemUS6075543Dec 22, 1998Jun 13, 2000Silicon Graphics, Inc.System and method for buffering multiple frames while controlling latencyUS6128010Oct 6, 1997Oct 3, 2000Assistive Technology, Inc.Action bins for computer user interfaceUS6133915 *Jun 17, 1998Oct 17, 2000Microsoft CorporationSystem and method for customizing controls on a toolbarUS6144381May 14, 1997Nov 7, 2000International Business Machines CorporationSystems, methods and computer program products for compass navigation of avatars in three dimensional worldsUS6154601Nov 14, 1997Nov 28, 2000Hitachi Denshi Kabushiki KaishaMethod for editing image information with aid of computer and editing systemUS6166748Dec 12, 1997Dec 26, 2000Nintendo Co., Ltd.Interface for a high performance low cost video game system with coprocessor providing high speed efficient 3D graphics and digital audio signal processingUS6167533Jun 25, 1998Dec 26, 2000Hewlett-Packard CompanyActive dashboard extensible frameworkUS6188399May 8, 1998Feb 13, 2001Apple Computer, Inc.Multiple theme engine graphical user interface architectureUS6191797May 21, 1997Feb 20, 2001Canon Kabushiki KaishaExpression tree optimization for processing obscured graphical objectsUS6195664Feb 21, 1997Feb 27, 2001Micrografx, Inc.Method and system for controlling the conversion of a file from an input format to an output formatUS6211890Feb 25, 1997Apr 3, 2001Sony Computer Entertainment, Inc.Image processor and image processing methodUS6246418May 9, 1997Jun 12, 2001Sony Computer Entertainment Inc.Data processing method and apparatusUS6259432Jul 20, 1998Jul 10, 2001International Business Machines CorporationInformation processing apparatus for improved intuitive scrolling utilizing an enhanced cursorUS6266053Apr 3, 1998Jul 24, 2001Synapix, Inc.Time inheritance scene graph for representation of media contentUS6266430Mar 8, 2000Jul 24, 2001Digimarc CorporationAudio or video steganographyUS6272484May 27, 1998Aug 7, 2001Scansoft, Inc.Electronic document managerUS6272558Oct 6, 1997Aug 7, 2001Canon Kabushiki KaishaApplication programming interface for manipulating flashpix filesUS6275831Aug 18, 1998Aug 14, 2001Starfish Software, Inc.Data processing environment with methods providing contemporaneous synchronization of two or more clientsUS6278448Feb 17, 1998Aug 21, 2001Microsoft CorporationComposite Web page built from any web contentUS6278450Apr 7, 2000Aug 21, 2001Microsoft CorporationSystem and method for customizing controls on a toolbarUS6300947Jul 6, 1998Oct 9, 2001International Business Machines CorporationDisplay screen and window size related web page adaptation systemUS6304684Feb 15, 2000Oct 16, 2001Cyberecord, Inc.Information processing system and method of using sameUS6307574May 8, 1995Oct 23, 2001Apple Computer, Inc.Graphical user interface with hierarchical structure for customizable menus and control objectsUS6310621Jun 30, 1998Oct 30, 2001Avid Technology, Inc.Extended support for numerical controlsUS6313851Aug 27, 1997Nov 6, 2001Microsoft CorporationUser friendly remote system interfaceUS6321314Jun 9, 1999Nov 20, 2001Ati International S.R.L.Method and apparatus for restricting memory accessUS6333753Nov 25, 1998Dec 25, 2001Microsoft CorporationTechnique for implementing an on-demand display widget through controlled fading initiated by user contact with a touch sensitive input deviceUS6344855Jul 26, 1999Feb 5, 2002Apple Computer, Inc.Encapsulated network entity reference of a network component system for integrating object oriented software componentsUS6353437May 29, 1998Mar 5, 2002Avid Technology, Inc.Animation system and method for defining and using rule-based groups of objectsUS6369823Feb 5, 2001Apr 9, 2002Sony Computer Entertainment Inc.Picture processing apparatus and picture processing methodUS6369830May 10, 1999Apr 9, 2002Apple Computer, Inc.Rendering translucent layers in a display systemUS6396520Jan 5, 2000May 28, 2002Apple Computer, Inc.Method of transition between window statesUS6401104Jul 3, 1999Jun 4, 2002Starfish Software, Inc.System and methods for synchronizing datasets using cooperation among multiple synchronization enginesUS6411301Jun 22, 2001Jun 25, 2002Nintendo Co., Ltd.Graphics system interfaceUS6412021Feb 26, 1998Jun 25, 2002Sun Microsystems, Inc.Method and apparatus for performing user notificationUS6421058Jun 22, 2001Jul 16, 2002Nintendo Co., Ltd.Graphics command stream for calling a display object in a graphics systemUS6424348Jun 22, 2001Jul 23, 2002Nintendo Co., Ltd.Application program interface for a graphics systemUS6434744Mar 3, 1999Aug 13, 2002Microsoft CorporationSystem and method for patching an installed application programUS6452600Nov 28, 2000Sep 17, 2002Nintendo Co., Ltd.Graphics system interfaceUS6456290Jun 22, 2001Sep 24, 2002Nintendo Co., Ltd.Application program interface for a graphics systemUS6457034Nov 2, 1999Sep 24, 2002Ati International SrlMethod and apparatus for accumulation buffering in the video graphics systemUS6466218Jun 22, 2001Oct 15, 2002Nintendo Co., Ltd.Graphics system interfaceUS6469714Dec 29, 1998Oct 22, 2002International Business Machines CorporationInfocenter user interface for applets and componentsUS6483524Oct 1, 1999Nov 19, 2002Global Graphics Software LimitedPrepress workflow method using raster image processorUS6484261 *Dec 11, 1998Nov 19, 2002Cisco Technology, Inc.Graphical network security policy managementUS6487560May 13, 1999Nov 26, 2002Starfish Software, Inc.System and methods for communicating between multiple devices for synchronizationUS6489963Jun 22, 2001Dec 3, 2002Nintendo Co., Ltd.Application program interface for a graphics systemUS6512522Apr 15, 1999Jan 28, 2003Avid Technology, Inc.Animation of three-dimensional characters along a path for motion video sequencesUS6515682May 9, 1996Feb 4, 2003National Instruments CorporationSystem and method for editing a control utilizing a preview window to view changes made to the controlUS6525736Aug 3, 2000Feb 25, 2003Koei Co., LtdMethod for moving grouped characters, recording medium and game deviceUS6526174Feb 28, 2000Feb 25, 2003Next Computer, Inc.Method and apparatus for video compression using block and wavelet techniquesUS6535892May 13, 2002Mar 18, 2003Starfish Software, Inc.System and methods for exchanging messages between a client and a server for synchronizing datasetsUS6542160Jun 18, 1999Apr 1, 2003Phoenix Technologies Ltd.Re-generating a displayed imageUS6542166May 9, 1996Apr 1, 2003National Instruments CorporationSystem and method for editing a controlUS6544295Nov 18, 1996Apr 8, 2003Starfish Software, Inc.Methods for managing preferred internet sites in a computer system having a browserUS6571328Aug 1, 2001May 27, 2003Nintendo Co., Ltd.Method and apparatus for obtaining a scalar value directly from a vector registerUS6573896Jul 8, 1999Jun 3, 2003Dassault SystemesThree-dimensional arrowUS6577317Aug 20, 1999Jun 10, 2003Apple Computer, Inc.Apparatus and method for geometry operations in a 3D-graphics pipelineUS6580430Nov 28, 2000Jun 17, 2003Nintendo Co., Ltd.Method and apparatus for providing improved fog effects in a graphics systemUS6590592Apr 21, 2000Jul 8, 2003Xsides CorporationParallel interfaceUS6609977Nov 28, 2000Aug 26, 2003Nintendo Co., Ltd.External interfaces for a 3D graphics systemUS6614444Aug 20, 1999Sep 2, 2003Apple Computer, Inc.Apparatus and method for fragment operations in a 3D-graphics pipelineUS6618048Nov 28, 2000Sep 9, 2003Nintendo Co., Ltd.3D graphics rendering system for performing Z value clamping in near-Z range to maximize scene resolution of visually important Z componentsUS6636214Nov 28, 2000Oct 21, 2003Nintendo Co., Ltd.Method and apparatus for dynamically reconfiguring the order of hidden surface processing based on rendering modeUS6639595Nov 28, 2000Oct 28, 2003Nintendo Co., Ltd.Achromatic lighting in a graphics system and methodUS6661426Sep 22, 2000Dec 9, 2003Koninklijke Philips Electronics N.V.User interface generationUS6664958Nov 28, 2000Dec 16, 2003Nintendo Co., Ltd.Z-texturingUS6664962Nov 28, 2000Dec 16, 2003Nintendo Co., Ltd.Shadow mapping in a low cost graphics systemUS6664986May 19, 1998Dec 16, 2003Cadent Ltd.Computer user interface for orthodontic useUS6674438Oct 6, 1999Jan 6, 2004Sony Computer Entertainment Inc.Method of and system for adding information and recording mediumUS6697074Jul 30, 2002Feb 24, 2004Nintendo Co., Ltd.Graphics system interfaceUS6707462May 12, 2000Mar 16, 2004Microsoft CorporationMethod and system for implementing graphics control constructsUS6714201Apr 14, 2000Mar 30, 20043D Open Motion, LlcApparatuses, methods, computer programming, and propagated signals for modeling motion in computer applicationsUS6715053Oct 30, 2000Mar 30, 2004Ati International SrlMethod and apparatus for controlling memory client access to address ranges in a memory poolUS6717599Jun 29, 2000Apr 6, 2004Microsoft CorporationMethod, system, and computer program product for implementing derivative operators with graphics hardwareUS6724403Oct 30, 2000Apr 20, 2004Surfcast, Inc.System and method for simultaneous display of multiple information sourcesUS6734864Sep 19, 2002May 11, 2004Phoenix Technologies Ltd.Re-generating a displayed imageUS6738804Sep 15, 2000May 18, 2004Yodlee.Com, Inc.Method and apparatus for enabling sectored data refreshing of Web-site data during sessionUS6741242Jul 17, 2000May 25, 2004Famotik KabushikikaishaMultimedia documents integrating and displaying systemUS6760046Mar 22, 2001Jul 6, 2004Hewlett Packard Development Company, L.P.Location-dependent user interfaceUS6765592Apr 30, 1999Jul 20, 2004Microsoft CorporationUndockable sub-windowsUS6788318May 8, 2001Sep 7, 2004Ulead Systems, Inc.Method for manipulating multiple multimedia objectsUS6806892Dec 20, 1999Oct 19, 2004International Business Machines CorporationLayer viewport for enhanced viewing in layered drawingsUS6882979Jun 18, 1999Apr 19, 2005Onadine, Inc.Generating revenue for the use of softgoods that are freely distributed over a networkUS6892360Aug 5, 1998May 10, 2005Sun Microsystems, Inc.Focus traversal mechanism for graphical user interface widgetsUS6906720Mar 12, 2002Jun 14, 2005Sun Microsystems, Inc.Multipurpose memory system for use in a graphics systemUS6910000Jun 2, 2000Jun 21, 2005Mitsubishi Electric Research Labs, Inc.Generalized belief propagation for probabilistic systemsUS6911984Mar 12, 2003Jun 28, 2005Nvidia CorporationDesktop compositor using copy-on-write semanticsUS6918091Nov 9, 2001Jul 12, 2005Change Tools, Inc.User definable interface system, method and computer program productUS6931633Aug 1, 2000Aug 16, 2005National Instruments CorporationSystem and method of evaluating the performance of an image processing algorithmUS6944829Sep 25, 2001Sep 13, 2005Wind River Systems, Inc.Configurable user-interface component management systemUS6993721Dec 18, 2000Jan 31, 2006Sony CorporationWeb channel guide graphical interface system and methodUS7016011Mar 31, 2003Mar 21, 2006Autodesk Canada Co.Generating image dataUS7027055Apr 30, 2002Apr 11, 2006The Commonwealth Of AustraliaData view of a modelling systemUS7050955Sep 29, 2000May 23, 2006Immersion CorporationSystem, method and data structure for simulated interaction with graphical objectsUS20010030647Jan 11, 2001Oct 18, 2001Sun Microsystems, Inc.Using messaging to manage scene-based renderingUS20010035885Mar 20, 2001Nov 1, 2001Michael IronMethod of graphically presenting network informationUS20020054148Jan 12, 2001May 9, 2002Hidehiko OkadaGUI control method and apparatus and recording mediumUS20020065946Oct 16, 2001May 30, 2002Shankar NarayanSynchronized computing with internet widgetsUS20020067418Dec 5, 2001Jun 6, 2002Nec CorporationApparatus for carrying out translucent-processing to still and moving pictures and method of doing the sameUS20020078453Dec 15, 2000Jun 20, 2002Hanchang KuoHub pages for set top box startup screenUS20020085037Nov 9, 2001Jul 4, 2002Change Tools, Inc.User definable interface system, method and computer program productUS20020089526Dec 29, 1998Jul 11, 2002Jeffrey J. BuxtonInfocenter user interface for applets and componentsUS20020093516Dec 14, 2001Jul 18, 2002Brunner Ralph T.Rendering translucent layers in a display systemUS20020099678Jan 9, 2002Jul 25, 2002Brian AlbrightRetail price and promotion modeling system and methodUS20020105548May 1, 2001Aug 8, 2002Richard HaytonMethods and apparatus for creating a user interface using property pathsUS20020112180Dec 19, 2001Aug 15, 2002Land Michael Z.System and method for multimedia authoring and playbackUS20020118217Mar 29, 2001Aug 29, 2002Masakazu FujikiApparatus, method, program code, and storage medium for image processingUS20020120673May 8, 2001Aug 29, 2002Michael TolsonArchitecture for a system of portable information agentsUS20020123739Feb 27, 2002Sep 5, 2002Claus HaackeUreter drainage deviceUS20020129092May 8, 2001Sep 12, 2002EnvoiiMethod and apparatus for a portable information agentUS20020133508Mar 8, 2002Sep 19, 2002Starfish Software, Inc.System and methods for synchronizing datasets using cooperation among multiple synchronization enginesUS20020140740Aug 9, 2001Oct 3, 2002Chien-An ChenMethod for previewing an effect applied to a multimedia objectUS20020158902 *Apr 30, 2001Oct 31, 2002Hooker Bryce H.Method and apparatus for automatically publishing associate informationUS20020171682May 7, 2002Nov 21, 2002Sun Microsystems, Inc.Method and apparatus for presenting information in a display system using transparent windowsUS20020174003May 15, 2001Nov 21, 2002Redmann William GibbensMethod and apparatus for providing visitors with a personalized itinerary and managed access to attractionsUS20020174181Apr 13, 2001Nov 21, 2002Songxiang WeiSharing OpenGL applications using application based screen samplingUS20020180798May 31, 2001Dec 5, 2002Poor Graham V.System and method for extending a wireless device platform to multiple applicationsUS20020186257Jun 8, 2001Dec 12, 2002Cadiz Jonathan J.System and process for providing dynamic communication access and information awareness in an interactive peripheral displayUS20020196268Jun 22, 2001Dec 26, 2002Wolff Adam G.Systems and methods for providing a dynamically controllable user interface that embraces a variety of mediaUS20030008711Jul 5, 2001Jan 9, 2003Dana CorboMethod and system for providing real time sports betting informationUS20030009267May 1, 2002Jan 9, 2003Ronald DunskyApparatus and method for providing live display of aircraft flight informationUS20030018971Sep 26, 2001Jan 23, 2003Mckenna Thomas P.System and method for providing supplemental information related to a television programUS20030020671Apr 30, 2002Jan 30, 2003Ovid SantoroSystem and method for simultaneous display of multiple information sourcesUS20030046316Apr 18, 2001Mar 6, 2003Jaroslav GergicSystems and methods for providing conversational computing via javaserver pages and javabeansUS20030061482Aug 23, 2002Mar 27, 2003Efunds CorporationSoftware security control system and methodUS20030067489Oct 15, 2002Apr 10, 2003Candy Wong Hoi LeeLayout of platform specific graphical user interface widgets migrated between heterogeneous device platformsUS20030076369Sep 19, 2002Apr 24, 2003Resner Benjamin I.System and method for presentation of remote information in ambient formUS20030080995Apr 3, 2002May 1, 2003United Virtualities, Inc.Contextually adaptive web browserUS20030097659Nov 16, 2001May 22, 2003Goldman Phillip Y.Interrupting the output of media content in response to an eventUS20030101046May 8, 2002May 29, 2003Mark KrasnovWord, expression, and sentence translation management toolUS20030122787Dec 28, 2001Jul 3, 2003Philips Electronics North America CorporationTouch-screen image scrolling system and methodUS20030123739Dec 20, 2002Jul 3, 2003Graffagnino Peter N.Method and apparatus for video compression using microwaveletsUS20030146934Feb 5, 2002Aug 7, 2003Bailey Richard St. ClairSystems and methods for scaling a graphical user interface according to display dimensions and using a tiered sizing schema to define display objectsUS20030154239Jan 10, 2003Aug 14, 2003Davis Andrew ThomasJava application framework for use in a content delivery network (CDN)US20030158975Feb 18, 2003Aug 21, 2003TridiumReal-time data interface and method for browsers and the likeUS20030164862Jun 8, 2001Sep 4, 2003Cadiz Jonathan J.User interface for a system and process for providing dynamic communication access and information awareness in an interactive peripheral displayUS20030169306Mar 7, 2002Sep 11, 2003Nokia CorporationCreating a screen saver from downloadable applications on mobile devicesUS20030174136Mar 12, 2002Sep 18, 2003Emberling Brian D.Multipurpose memory system for use in a graphics systemUS20030174154Apr 4, 2000Sep 18, 2003Satoru YukieUser interface for interfacing with plural real-time data sourcesUS20030184552Mar 26, 2002Oct 2, 2003Sanja ChadhaApparatus and method for graphics display system for markup languagesUS20030184584Mar 29, 2002Oct 2, 2003Thomas VachuskaUser interface framework for integrating user interface elements of independent software componentsUS20030189597Apr 5, 2002Oct 9, 2003Microsoft CorporationVirtual desktop managerUS20030191799Mar 14, 2001Oct 9, 2003Netilla Networks, Inc.Apparatus and accompanying methods for providing, through a centralized server site, a secure, cost-effective, web-enabled, integrated virtual office environment remotely accessible through a network-connected web browserUS20030208685May 1, 2002Nov 6, 2003Abdel-Rahman Hassan E.Multi-platform application installationUS20040012626Jul 22, 2002Jan 22, 2004Brookins Timothy J.Method for creating configurable and customizable web user interfacesUS20040032409Aug 15, 2002Feb 19, 2004Martin GirardGenerating image dataUS20040036711Aug 23, 2002Feb 26, 2004Anderson Thomas G.Force frames in animationUS20040039934Dec 18, 2002Feb 26, 2004Land Michael Z.System and method for multimedia authoring and playbackUS20040070629Aug 18, 2003Apr 15, 2004Hewlett-Packard Development Company, L.P.Graphical user computer interfaceUS20040125128Dec 26, 2002Jul 1, 2004Cheng-Chia ChangGraphical user interface for a slideshow presentationUS20040179019Mar 12, 2003Sep 16, 2004Nvidia CorporationDouble-buffering of pixel data using copy-on-write semanticsUS20040194020Oct 23, 2003Sep 30, 2004Beda Joseph S.Markup language and object model for vector graphicsUS20040205504Dec 5, 2001Oct 14, 2004International Business Machines CorporationSystem and method for navigating graphocal imagesUS20040212640Apr 25, 2003Oct 28, 2004Justin MannSystem and method for providing dynamic user information in an interactive displayUS20040215740Feb 18, 2003Oct 28, 2004Frank Brian S.Real-time data interface and method for browsers and the likeUS20040223003Jun 9, 2004Nov 11, 2004Tandem Computers IncorporatedParallel pipelined merge enginesUS20040225955Apr 29, 2004Nov 11, 2004The Boeing CompanyIntelligent information dashboard system and methodUS20040255253Jun 13, 2003Dec 16, 2004Cezary MarcjanMulti-layer graphical user interfaceUS20040261012Jun 17, 2003Dec 23, 2004Balsiger Fred W.Snaplines for control object positioningUS20040261037Oct 22, 2003Dec 23, 2004Apple Computer, Inc.Computer interface having a virtual single-layer mode for viewing overlapping objectsUS20040261038Jun 20, 2003Dec 23, 2004Apple Computer, Inc.Computer interface having a virtual single-layer mode for viewing overlapping objectsUS20050010419Jul 7, 2003Jan 13, 2005Ahmad PourhamidSystem and Method for On-line Translation of documents and AdvertisementUS20050010634Jun 19, 2003Jan 13, 2005Henderson Roderick C.Methods, systems, and computer program products for portlet aggregation by client applications on a client side of client/server environmentUS20050021935Jun 16, 2004Jan 27, 2005Openwave Systems Inc.Method and system for downloading configurable user interface elements over a data networkUS20050022139Dec 3, 2003Jan 27, 2005David GettmanInformation displayUS20050039144Mar 5, 2004Feb 17, 2005Alan WadaMethod and system of providing customizable buttonsUS20050057497Sep 15, 2003Mar 17, 2005Hideya KawaharaMethod and apparatus for manipulating two-dimensional windows within a three-dimensional display modelUS20050060655Sep 12, 2003Mar 17, 2005UseractiveDistance-learning system with dynamically constructed menu that includes embedded applicationsUS20050060661Nov 14, 2003Mar 17, 2005Hideya KawaharaMethod and apparatus for displaying related two-dimensional windows in a three-dimensional display modelUS20050088447Oct 23, 2003Apr 28, 2005Scott HanggieCompositing desktop window managerUS20050088452Oct 23, 2003Apr 28, 2005Scott HanggieDynamic window anatomyUS20050091571Oct 23, 2003Apr 28, 2005Ivan LeichtlingSynchronized graphics and region data for graphics remoting systemsUS20050114021Dec 3, 2004May 26, 2005Garmin Ltd., A Cayman Islands CorporationPDA with integrated address book and electronic map waypointsUS20050144563Nov 24, 2004Jun 30, 2005Microsoft CorporationMethod for flagging and relating information in a computer systemUS20050144595Jun 3, 2004Jun 30, 2005International Business Machines CorporationGraphical user interface (GUI) script generation and documentationUS20050160368Jan 21, 2004Jul 21, 2005Fuji Xerox Co., Ltd.Systems and methods for authoring a media presentationUS20050168471Dec 18, 2003Aug 4, 2005Paquette Michael J.Composite graphics rendered using multiple frame buffersUS20050168476Oct 30, 2003Aug 4, 2005Sensable Technologies, Inc.Apparatus and methods for stenciling an imageUS20050172239Jan 30, 2004Aug 4, 2005International Business Machines CorporationModeless interaction with GUI widget applicationsUS20050183026Jan 11, 2005Aug 18, 2005Ryoko AmanoInformation processing apparatus and method, and programUS20050193368Feb 26, 2004Sep 1, 2005International Business Machines CorporationRendering GUI widgets with generic look and feelUS20050198584Jan 27, 2004Sep 8, 2005Matthews David A.System and method for controlling manipulation of tiles within a sidebarUS20050215310Mar 15, 2005Sep 29, 2005Scott BoydEvent calendar at electronic gaming deviceUS20050240857Apr 4, 2005Oct 27, 2005Jason BenedictMethods and systems of information portal constructionUS20050243373Jun 23, 2005Nov 3, 2005Sliverbrook Research Pty LtdGraphic design software using an interface surfaceUS20050256940May 4, 2004Nov 17, 2005International Business Machines CorporationMethods, systems, and computer program products for client side prefetching and caching of portletsUS20050278651May 25, 2005Dec 15, 2005Brian CoeMethod and system of launching applications from a button of a browserUS20050282612Aug 14, 2003Dec 22, 2005Marc MathewsSports theme gaming apparatus and method for playing the sameUS20050283734May 27, 2005Dec 22, 2005Surfcast, Inc., A Delaware CorporationSystem and method for simultaneous display of multiple information sourcesUS20060015818Jun 25, 2004Jan 19, 2006Chaudhri Imran AUnified interest layer for user interfaceUS20060075106Sep 1, 2004Apr 6, 2006Roland HochmuthManaging multiple remote computing sessions displayed on a client deviceUS20060075141Dec 3, 2003Apr 6, 2006David BoxenhornNetworked computing using objectsUS20060089840Oct 21, 2004Apr 27, 2006Margaret MayHealth tracking method and apparatusUS20060123356Jan 24, 2006Jun 8, 2006Microsoft CorporationDynamic and updateable computing application panesUS20060218499Mar 22, 2005Sep 28, 2006Microsoft CorporationDetermining and displaying a list of most commonly used itemsUS20060277469Jun 7, 2005Dec 7, 2006Chaudhri Imran APreview and installation of user interface elements in a display environmentUS20070038934Aug 14, 2006Feb 15, 2007Barry FellmanService for generation of customizable display widgetsUS20070044029Aug 18, 2005Feb 22, 2007Microsoft CorporationSidebar engine, object model and schemaUS20070044039Feb 17, 2006Feb 22, 2007Microsoft CorporationSidebar engine, object model and schemaUS20070061724Sep 15, 2006Mar 15, 2007Slothouber Louis PSelf-contained mini-applications system and method for digital televisionUS20070101146Apr 20, 2006May 3, 2007Louch John OSafe distribution and use of contentUS20070101279Feb 16, 2006May 3, 2007Chaudhri Imran ASelection of user interface elements for unified display in a display environmentUS20070101288Nov 16, 2005May 3, 2007Scott ForstallPreview including theme based installation of user interface elements in a display environmentUS20070101291Apr 12, 2006May 3, 2007Scott ForstallLinked widgetsUS20070101297Feb 1, 2006May 3, 2007Scott ForstallMultiple dashboardsUS20070101433May 10, 2006May 3, 2007Louch John OWidget securityUS20070130541Aug 4, 2006Jun 7, 2007Louch John OSynchronization of widgets and dashboardsUS20070162850Jan 6, 2006Jul 12, 2007Darin AdlerSports-related widgetsUS20070203984Sep 9, 2002Aug 30, 2007Meca Communications, Inc.Sharing skinsUS20070209013Mar 2, 2006Sep 6, 2007Microsoft CorporationWidget searching utilizing task frameworkUS20070266093May 10, 2006Nov 15, 2007Scott ForstallWorkflow widgetsUS20080034309Aug 1, 2006Feb 7, 2008Louch John OMultimedia center including widgetsUS20080034314Aug 4, 2006Feb 7, 2008Louch John OManagement and generation of dashboardsUS20080168367Jan 7, 2007Jul 10, 2008Chaudhri Imran ADashboards, Widgets and DevicesUS20080168368Jan 7, 2007Jul 10, 2008Louch John ODashboards, Widgets and DevicesUS20080168382Jan 7, 2007Jul 10, 2008Louch John ODashboards, Widgets and DevicesUS20090005071Mar 24, 2008Jan 1, 2009Apple Inc.Event Triggered Content PresentationUS20090021486Oct 4, 2007Jan 22, 2009Apple Inc.Dashboard SurfacesUS20090024944Dec 13, 2007Jan 22, 2009Apple Inc.User-centric widgets and dashboardsUS20090044138Aug 6, 2007Feb 12, 2009Apple Inc.Web WidgetsUS20090228824May 20, 2009Sep 10, 2009Apple Inc.Multiple dashboardsDE10242378A1Sep 12, 2002Mar 18, 2004Siemens AgSymbol input unit for miniature wrist mobile phone has rotating wheel input scrolling with display screen cursor and selection buttonsEP0694879B1Jul 24, 1995Nov 2, 2005Canon Kabushiki KaishaEfficient methods, apparatus and computer program for the evaluation of a graphical programming languageEP0908835A3Oct 5, 1998Jan 19, 2000Lucent Technologies Inc.Geo-enabled personal information managerEP0972273B1Apr 3, 1998Mar 24, 2004Intergraph Hardware Technologies CompanyApparatus and method for applying effects to graphical imagesEP1237076A3Feb 27, 2002Oct 11, 2006Microsoft CorporationExpert system for generating user interfacesEP1383080A1Apr 7, 2003Jan 21, 2004Microsoft CorporationIntermediate buffers in a graphics system* Cited by examinerNon-Patent CitationsReference1"Desktop Sidebar", [online] [Retrieved on May 11, 2007] Retrieved from the Internet URL: http://web.archive.org/web/20040101160831/http://www.desktopsidebar.com/; 5 pages.2"Portlet Communication: What is application scope, anyway?", Sep. 18, 2002, [online]; Retrieved from the Internet at URL: http://wwwcoderanch.com/t/203244/Portals-Portlets/java/Portlet-Communication-What-application-scope; 3 pages.3"Sidekick", [Online] [Retrieved on Oct. 12, 2009] Retrieved from the Internet at URL: http://en.widipedia.org/wiki/Sidekick; 5 pages.4"Starfish Software Introduces Starfish Internet Sidekick; Starfish Internet Sidekick is the best way for Internet users to manage their calendar, contacts and communications," Business Wire, Sep. 23, 1996, [online] [Retrieved on Dec. 8, 2008]; Retrieved from the Internet URL: http://findarticles.com/articles/mi-mOEIN/is-1996-Sept-23/ai-18704672?tag=rel.resl; 2 pages.5"Starfish Software Introduces Starfish Internet Sidekick; Starfish Internet Sidekick is the best way for Internet users to manage their calendar, contacts and communications," Business Wire, Sep. 23, 1996, [online] [Retrieved on Dec. 8, 2008]; Retrieved from the Internet URL: http://findarticles.com/articles/mi—mOEIN/is—1996—Sept—23/ai—18704672?tag=rel.resl; 2 pages.6"Welcome to the Gigaplex!(TM)", Lazar Productions, Nov. 1996, [online] [Retrieved on Dec. 8, 2008]; Retrieved from the Internet URL: http://web.archive.org/web/19961105081827/www.gigaplex.com/; 4 pages.7"Welcome to the Gigaplex!™", Lazar Productions, Nov. 1996, [online] [Retrieved on Dec. 8, 2008]; Retrieved from the Internet URL: http://web.archive.org/web/19961105081827/www.gigaplex.com/; 4 pages.8"Writing a Desk Accessory," Developer Connection, Apple Computer, Inc. Jul. 3, 1996, [online] [Retrieved on Jan. 3, 2006] Retrieved from the Internet URL: http://developer.apple.com/documentation/mac/devices/devices-16.html>, 3 pages.9Akeley et al., "Real-Time Graphics Architecture," http://www.grahics.stanford.edu/courses/cs448a01-fall, the OpenGL� Graphics System, CS448 Lecture 15, Fall, 2001, pp. 1-20.10Akeley, "Cg- Teaching Cg," Power Point Presentation, NVIDIA Corporation, 2002; 1 page.11Akeley, "Cg— Teaching Cg," Power Point Presentation, NVIDIA Corporation, 2002; 1 page.12Akeley, Kurt, and Hanrahan, Pat, "Real-Time Graphics Architecture," http://www.grahics.stanford.edu/courses/cs448a-01-fall, the OpenGL Graphics System, CS448 Lecture 15, Fall, 2001, pp. 1-20.13Altman, "Visual QuickStart Guide PowerPoint 2000/98, Applying Preset Animations", ProQuest Safari Books, Peachpit Press, May 7, 1999, [online] Retrieved from the Internet: URL: http://proquest.safaribooksonline.com/0201354411; 7 pages.14Altman, R.B., "Visual Quickstart Guide Power Point 2000/98, Applying Preset Animations," ProQuest Safari Books, Peachpit Press, May 7, 1999, 7 pages [online] Retrieved from the Internet: .15Altman, R.B., "Visual Quickstart Guide Power Point 2000/98, Applying Preset Animations," ProQuest Safari Books, Peachpit Press, May 7, 1999, 7 pages [online] Retrieved from the Internet: <URL: http://proquest.safaribooksonline.com/0201354411>.16Archive of "Objects, Images and Applets," W3C Recommendation, Feb. 10, 2003, [online] [Archived by http://archivve.org; Retrieved on Apr. 13, 2006] Retrieved from the Internet URL:http://web.archivve.org/web/20030210154019/http://www.w3.org/TR/REC-html140/struct/objects.html, 21 pages.17BabelFish.com, Inc., Oct. 2003, [online] [Retrieved on Dec. 8, 2008]; Retrieved from the Internet URL: http://web.archive.org/web/20031002115902/www.babelfish.com/en/index.html; 1 page.18Beier et al., "The Bull's-Eye: A Framework for Web Application User Interface Design Guidelines", Proceedings of the Sigchi Conference on Human Factors in Computing Systems, Apr. 2003, pp. 489-496.19Caceres et al., "Widget 1.0 Requirements", [Online] [Downloaded on Sep. 10, 2009]; Retrieved from the Internet at URL: http://www.w3.org/TR/2007/WD-widgets-reqs-20070705; 30 pages.20Cadiz et al., "Slideshow: Providing Peripheral Awareness of Important Information," Technical Report MSR-TR-2001-83, Microsoft Corporation, Redmond, WA; Sep. 14, 2001; 9 pages.21Cadiz, JJ et al., "Slideshow: Providing Peripheral Awareness of Important Information," Technical Report MSR-TR-2001-83, (Sep. 14, 2001), 9 pages. Microsoft Corporation, Redmond, WA.22Carey et al., "Integrating Widget Design Knowledge with User Interface Toolkits", Proceedings of the Fifth International Workshop on Computer-Aided Software Engineering, Jul. 1992, pp. 204-212.23Chen et al., "The Model of Optimum Route Selection in Vehicle Automatic Navigation System Based on Unblocked Reliability Analyses", Intelligent Transportation Systems, 2003, Proceedings, IEEE (2003), vol. 2, 12-15, Oct. 2003, pp. 975-978.24Chinese Notification of First Office Action, Chinese Patent Application No. 200580016349.3, Jul. 25, 2008, 21 pages.25Conner Borookshire D. et al. "Three-Dimensional Widgets" ACM 1992, 8 pages.26Conner et al. "Three-Dimensional Widgets" ACM 1992, pp. 183-188 and 230-231.27Elliott, Conal, "Programming Graphics Processors Functionally," Proceedings of the 2004 Haskell Workshop, Sep. 22, 2004. 11 pages.28Fried, Ina, "Developer Calls Apple's Tiger a Copycat," CNET News.com, Jun. 28, 2004 [online] Retrieved on Jul. 1, 2004 Retrieved from the Internet URL:http://zdnet.com.com/2102-1104-2-250692.html?tag=printthis, 2 pages.29Fried, Ina, "Developer Calls Apple's Tiger a Copycat," CNET News.com, Jun. 28, 2004 [online] Retrieved on Jul. 1, 2004 Retrieved from the Internet URL:http://zdnet.com.com/2102-1104—2-250692.html?tag=printthis, 2 pages.30Fried, Ina, "For Apple's Tiger, the Keyword is Search", CNET News.com, Jun. 28, 2004 [online] Retrieved on Jul. 1, 2004 Retrieved from the Internet URL:http://zdnet.com.com/2102-1103-2-5250346.html?tag=printthis, 2 pages.31Fried, Ina, "For Apple's Tiger, the Keyword is Search", CNET News.com, Jun. 28, 2004 [online] Retrieved on Jul. 1, 2004 Retrieved from the Internet URL:http://zdnet.com.com/2102-1103—2-5250346.html?tag=printthis, 2 pages.32Fried, Ina, "For Apple's Tiger, the kyword is search", CNET News.com, Jun. 28, 2004, [online] [Retrieved on May 5, 2009], Retrieved from the Internet URL: http://archive.org/web20040823135016/http://zdnet.com-com/2102-1103-2-5250346.html; 2 pages.33Fried, Ina, "For Apple's Tiger, the kyword is search", CNET News.com, Jun. 28, 2004, [online] [Retrieved on May 5, 2009], Retrieved from the Internet URL: http://archive.org/web20040823135016/http://zdnet.com-com/2102-1103—2-5250346.html; 2 pages.34Gruber et al., "Dashboard vs. Konfabulator", Jun. 2004; 10 pages.35Guber, John et al., "Dashboard vs. Konfabulator", Jun. 2004, 9 pages.36Haeberli et al., "The Accumulation Buffer: Hardware Support for High-Quality Rendering," Computer Graphics, Aug. 1990, 24(4):309-318.37Haeberli, P. et al., "The Accumulation Buffer: Hardware Support for High-Quality Rendering," Computer Graphics, Aug. 1990, pp. 309-318, vol. 24, No. 4.38Helal et al., "Drishti: An Integrated Navigation System for Visually Impaired and Disabled", Fifth International Symposium on Wearable Computers (ISWC'01), IEEE, 2001, pp. 149-156.39Http://en.wikipedia.org/wiki/Comparison-of-widget-engines, 2007, 6 pages.40Http://en.wikipedia.org/wiki/Comparison—of—widget—engines, 2007, 6 pages.41http://en.wikipedia.org/wiki/Windows-Sidebar, 2007, 7 pages.42http://www.nat.org/dashboard/blog.php3-Dec. 2003, 31 pages.43http://www.nat.org/dashboard/blog.php3—Dec. 2003, 31 pages.44International Search Report , PCT/US2005/008804, Jul. 27, 2005, 3 pages.45International Search Report and the Written Opinion, dated Jan. 27, 2006, issued in International Application No. PCT/US2005/022579; 15 pages.46International Search Report and the Written Opinion, dated May 8, 2008, issued in International Application PCT/US2007/077441; 17 pages.47International Search Report and Writen Opinion, PCT/US2005/022152, Jul. 10, 2006, 8 pages.48International Search Report and Written Opinion, dated Oct. 16, 2009, issued in International Application No. PCT/US2008/070217.49International Search Report and Written Opinion, dated Sep. 3, 2009, issued in International Application No. PCT/US2008/050047; 17 pages.50International Search Report, dated Aug. 8, 2005, issued in International Application PCT/US2005/008805; 3 pages.51International Search Report, dated Jul. 10, 2006, issued in International Application PCT/US2005/022152; 1 page.52International Search Report, dated Jul. 27, 2005, issued in International Application PCT/US2005/008804; 3 pages.53International Search report, PCT/US2005/008805, Aug. 8, 2005, 3 pages.54Invitation to Pay Additional Fees and Communication Relating to the Results of the Partial International Search, dated Jan. 28, 2008, issued in International Application PCT/US2007/077441; 8 pages.55Invitation to Pay Additional Fees and Communication Relating to the Results of the Partial International Search, dated Jul. 29, 2008, issued in International Application PCT/US2008/050295; 10 pages.56Invitation to Pay Additional Fees and Communication Relating to the Results of the Partial International Search, dated May 15, 2009, issued in International Application No. PCT/US2008/050047; 11 pages.57Invitation to Pay Additional Fees and Communication Relating to the Results of the Partial International Search, dated May 8, 2009, issued in International Application PCT/US2008/050038; 19 pages.58JavaBoutique, [online], Retrieved from the Internet URL: http://javaboutique.internet.com/utilities/counter.html; Oct. 1, 2002; 2 pages.59Konfabulator, "Cupertino, Start your Photocopiers!," [online] [Retrieved on Jul. 1, 2004] Retrieved from the Internet , 1 page.60Konfabulator, "Cupertino, Start your Photocopiers!," [online] [Retrieved on Jul. 1, 2004] Retrieved from the Internet <URL: http://www.konfabulator.com>, 1 page.61Konfabulator, "Konfabulator & Widget Basics," [online] [Retrieved on Jul. 1, 2004] Retrieved from the Internet , 3 pages.62Konfabulator, "Konfabulator & Widget Basics," [online] [Retrieved on Jul. 1, 2004] Retrieved from the Internet <URL: http://www.konfabulator.com/info/basics.html>, 3 pages.63Konfabulator, "Screenshots," [online] [Retrieved on Jul. 1, 2004] Retrieved from the Internet , 2 pages.64Konfabulator, "Screenshots," [online] [Retrieved on Jul. 1, 2004] Retrieved from the Internet <URL: http://www.konfabulator.com/info/screenshots.html>, 2 pages.65Konfabulator, "What is Konfabulator?," [online] [Retrieved on Jul. 1, 2004] Retrieved from the Internet <URL: http://www.konfabulator.com/info/, 3 pages.66Lammers, J.., et al., "Maya 4.5 Fundamentals: Particles, "New Riders Publishing, Jan. 14, 2003, 12 pages, [online] [retrieved on Feb. 17, 2007] Retrieved from ProQuest Safari Books Online on the Internet: , 12 pages.67Lammers, J.., et al., "Maya 4.5 Fundamentals: Particles, "New Riders Publishing, Jan. 14, 2003, 12 pages, [online] [retrieved on Feb. 17, 2007] Retrieved from ProQuest Safari Books Online on the Internet: <URL: http://proquest.safaribooksonline.com/0735713278>, 12 pages.68Microsoft Corporation, "Microsoft� Windows(TM) Graphical Environment User's Guide", Version 3.0 for MS-DOS� or PC-DOS Operating System, 1990, Document No. SY06851-0290, pp. Cover-vii, 15-75, 315-353.69Microsoft Corporation, "Microsoft� Windows™ Graphical Environment User's Guide", Version 3.0 for MS-DOS� or PC-DOS Operating System, 1990, Document No. SY06851-0290, pp. Cover-vii, 15-75, 315-353.70Microsoft Corporation, "User's Guide Microsoft� Windows(TM)and MS-DOSs� 6", 1993, pp. Cover-xvi, 112-121.71Microsoft Corporation, "User's Guide Microsoft� Windows™and MS-DOSs� 6", 1993, pp. Cover-xvi, 112-121.72Movies.com, Jan. 2002, [online] [Retrieved on Dec. 8, 2008]; Retrieved from the Internet URL: http://www.archive.org/web/20020118102516/movies.go.com; 1 page.73Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, PCT/US2005/022579, 15 pages.74Nvidia, "CG-Teaching Cg," Power Point Presentation, Author and date unknown, pp. 1-16.75Nvidia, "CG—Teaching Cg," Power Point Presentation, Author and date unknown, pp. 1-16.76Puder, A., "Extending Desktop Applications to the Web," ACM International Conference Proceedings Series, Proceedings of the Jun. 2004 International Symposium on Information and Communication Technologies, 2004, vol. 90, 6 pages.77Rist et al., "Customizing Graphics for Tiny Displays of Mobile Devices", Personal and Ubiquitous Computing, 2002, vol. 6, pp. 260-268.78Rochkind, M. et al., "Common Elements in Today's Graphical User Interfaces: The Good, the Bad, and the Ugly," Interchi '93, AMC, Apr. 24-29, 1993, pp. 470-473.79Segal et al., "The OpenGL� Graphics System: A Specification (Version 1.5)", � 1992-2003 Silicon Graphics, Inc., Oct. 30, 2003, 333 pages.80Segal, Mark and Akeley, Kurt, "The OpenGL Graphics System: A Specification (Version 1.5)," Copyright 1992-2003 Silicon Graphics, Inc., Oct. 30, 2003, 334 pages.81Shantzis, "A Model for Efficient and Flexible Image Computing," Computer Graphics Proceedings, Annual Conference Series, Orlando, Florida, Jul. 24-29, 1994, pp. 147-154.82Shantzis, Michael A., "A Model for Efficient and Flexible Image Computing," Computer Graphics Proceedings, Annual Conference Series, Orlando, Florida, Jul. 24-29, 1994, pp. 147-154.83Shiozawa et al., "Perspective Layered Visualization of Collaborative Workspaces," Proceedings of the International ACM SIGGROUP conference on Supporting Group Work Publisher, Nov. 1999, 10 pages.84Shiozawa, Hidekazu et al., "Perspective Layered Visualization of Collaborative Workspaces," Proceedings of the International ACM SIGGROUP conference on Supporting Group Work Publisher, Nov. 1999, 5 pages.85Siracusa, "Mac OS X 10.4 Tiger: Dashboard", Apr. 28, 2005, [online] [Retrieved on Aug. 1, 2008] Retrieved from the Internet URL: http://arstechnica.com/reviews/os/macosx-10-4.ars/17; 7 pages.86Snippet Software Inc. et al. "Corporate PortaL Newsletter" Oct. 2000, 3 pages.87Snippet Software Inc. et al. "Snippets Software" Jun. 2001, 16 pages.88Snippet Software, "Product Spotlight Non-browser based portal solution from Snippets Software", Corporate Portal Newsletter, Oct. 2000, vol. 1, No. 10, 3 pages.89Snippet Software, "Snippets Infomration Delivery Platform", [online] [Retrieved on Jun. 11, 2001]; Retrieved from the Internet URL: http://www.snippets.com/products/; 19 pages.90Snippets Software, "Products Overview", Feb. 2002, [online] [Retrieved on Feb. 5, 2008] Retrieved from the Internet URL: http://web.archive.org/web/20020206061508/http://www.snippets.com/products/; 2 pages.91Staples, "Representation in Virtual Space: Visual Convention in the Graphical User Interface," Proceedings of the SIGCHI Conference on Human Factors in Computing Systems, Apr. 1993 [online] [Retrieved on Dec. 2003] Retrieved from the Internet URL: http://www.nat.org/dashboard/blog.php3 Dec. 2003; 8 pages.92Staples, Loretta, "Representation in Virtual Space: Visual Convention in the Graphical User Interface," Proceedings of the SIGCHI Conference on Human Factors in Computing Systems, Apr. 1993. http://www.nat.org/dashboard/blog.php3-Dec. 2003, 8 pages.93Staples, Loretta, "Representation in Virtual Space: Visual Convention in the Graphical User Interface," Proceedings of the SIGCHI Conference on Human Factors in Computing Systems, Apr. 1993. http://www.nat.org/dashboard/blog.php3—Dec. 2003, 8 pages.94Stardock, "DesktopX General Guide," Aug. 2000, [online] [Retrieved on Jan. 31, 2008]; Retreived from the Internet URL:htp://www.stardock.com/products/desktopx/docs/; 28 pages.95Stardock, "DesktopX Tutorial", Aug. 2000, [online] [Retrieved on Jan. 31, 2008]; Retrieved from the Internet URLl:http://www.stardock.com/products/desktopx/tutorial.html; 40 pages.96Stardock, "DesktopX WhitePaper", Aug. 2000, [online] [Retrieved on Jan. 31, 2008]; Retrieved from the Internet URL: http://www.stardock.net/media/whitepaper-desktopx.html; 15 pages.97Stardock, "DesktopX WhitePaper", Aug. 2000, [online] [Retrieved on Jan. 31, 2008]; Retrieved from the Internet URL: http://www.stardock.net/media/whitepaper—desktopx.html; 15 pages.98Stardock, "The User Guide-Version 2", DesktopX 2000; 57 pages.99Stardock, "The User Guide—Version 2", DesktopX 2000; 57 pages.100Stardock, "What Can It Do? Making Objects", DesktopX Tutorial, 2001, [online] [Retrieved on Apr. 11, 2008]; Retrieved from the Internet URL: http://web.archive.org/web/20011019222825/http://www.stardock.com/products/desktopx/.... ; 6 pages.101Stardock.com et al. "DesktopX Whitepaper and users Guide" 1999, 72 pages.102Tang et al., "ConNex to Awarenex: Extending Awareness to Mobile Users," SIGCHI '01, AMC, Mar. 31-Apr. 4, 2001, 8 pages.103Tang, J.C. et al., "ConNexus to Awarenex: Extending Awareness to Mobile Users," SIGCHI '01, AMC, Mar. 31-Apr. 4, 2001, 8 pages.104Thomas et al., "Animating Widgets in the InterViews Toolkit", Lecture Notes in Computer Science, pp. 26-44, 1995.105Ullenboom, "Java is auch eine Insel," 2003, [online] [Retrieved on Apr. 13, 2006]; Retrieved from the Internet URL: http://www.galileocomputing.de/openbook/javainse12//java-140000.htm#Xxx998138, 3 pages.106Ullenboom, "Java is auch eine Insel," 2003, [online] [Retrieved on Apr. 13, 2006]; Retrieved from the Internet URL: http://www.galileocomputing.de/openbook/javainse12//java—140000.htm#Xxx998138, 3 pages.107Ullenboom, C., "Java is auch eine Insel," 2003, [online] [Retrieved on Apr. 13, 2006] Retrieved from the Internet URL: http://www.galileocomputing.de/openbook/javainsel2//java-140000.htm#Xxx998138, 3 pages.108Ullenboom, C., "Java is auch eine Insel," 2003, [online] [Retrieved on Apr. 13, 2006] Retrieved from the Internet URL: http://www.galileocomputing.de/openbook/javainsel2//java—140000.htm#Xxx998138, 3 pages.109Van Gelder et al., "Direct Volume Rendering with Shading via Three-Dimensional Textures,"Computer Science Dept., UNiv. of California, Santa, Cruz, CA 95064, Jul. 19, 1996; 17 pages.110Van Gelder, Allen, and Kwansik, Kim, "Direct Volume Rendering with Shading via Three-Dimensional Textures," Computer Science Dept., Univ. of California, Santa Cruz, CA 95064, 9 pages.111VMware(TM), "VMware(TM) Workstation User's Manual, Version 3.2", 2002; cover, pp. 12-13.112VMware™, "VMware™ Workstation User's Manual, Version 3.2", 2002; cover, pp. 12-13.113Wardell, "Apple's Dashboard vs. Konfabulator vs. DesktopX", Skinning the frog, Jul. 1, 2004, [online] [Retrieved on Aug. 1, 2008]; Retrieved from the Internet URL: http://frogboy.joeuser.com/article/19800; 9 pages.114Wardell, "Konfabulator for Windows", Jan. 10, 2004, [online] [Retrieved on Mar. 6, 2006]; Retrieved from the Internet URL: http://www.xpthemes.com/forums.aps?MID=19&CMID=19&AID=4472, 6 pages.115Wardell, Brad, Konfabulator for Windows, Jan. 10, 2004; [online] Retrieved from the Internet Mar. 6, 2006 Retrieved from the Internet: URL: http://www.xpthemes.com/forums.asp?MID=19&CMID=19&AID=4472, 6 pages.Referenced byCiting PatentFiling datePublication dateApplicantTitleUS7853882 *Apr 11, 2006Dec 14, 2010International Business Machines CorporationPortlets having different portlet specific enablement statesUS8104044 *Jan 24, 2012Amazon Technologies, Inc.System and method for client-side widget communicationUS8495511 *Jun 30, 2010Jul 23, 2013International Business Machines CorporationCare label method for a self service dashboard constructionUS8719896Sep 16, 2008May 6, 2014Oracle International CorporationWidget host container component for a rapid application development toolUS8769490Sep 16, 2008Jul 1, 2014Oracle International CorporationDesktop widget engine emulator component for a rapid application development toolUS8949737 *Oct 28, 2009Feb 3, 2015Red Hat, Inc.Centralized application package distributionUS8966385 *Apr 20, 2010Feb 24, 2015Canon Kabushiki KaishaRadiation imaging apparatus, display processing method of the same, and computer-readable storage mediumUS8972533 *Nov 8, 2007Mar 3, 2015Sprint Communications Company L.P.Activating touch-sensitive keys utilizing configuration settingsUS9049261Jun 20, 2013Jun 2, 2015Google Inc.Prioritized management and presentation of notificationsUS9052927 *Aug 24, 2011Jun 9, 2015Lg Electronics Inc.Mobile terminal and method of setting an application indicator thereinUS9063740 *Sep 16, 2008Jun 23, 2015Oracle International CorporationWeb widget component for a rapid application development toolUS9141405Dec 15, 2011Sep 22, 2015International Business Machines CorporationUser interface constructionUS9274679 *Jul 1, 2013Mar 1, 2016International Business Machines CorporationCare label method for a self service dashboard constructionUS20070240063 *Apr 11, 2006Oct 11, 2007International Business Machines CorporationPortlets having different portlet specific enablement statesUS20090049384 *Aug 13, 2008Feb 19, 2009Frank YauComputer desktop multimedia widget applications and methodsUS20090100377 *Oct 14, 2008Apr 16, 2009Asako MiyamotoMethod for providing information by data processing deviceUS20090235149 *Mar 17, 2008Sep 17, 2009Robert FrohweinMethod and Apparatus to Operate Different Widgets From a Single Widget ControllerUS20100023874 *Jul 22, 2009Jan 28, 2010Frohwein Robert JMethod and Apparatus to Operate Different Widgets From a Single Widget ControllerUS20100070886 *Mar 18, 2010Oracle International CorporationWeb widget component for a rapid application development toolUS20100070968 *Mar 18, 2010Oracle International CorporationDesktop widget engine emulator component for a rapid application development toolUS20100071026 *Mar 18, 2010Oracle International CorporationWidget host container component for a rapid application development toolUS20100235750 *Mar 12, 2009Sep 16, 2010Bryce Douglas NolandSystem, method and program product for a graphical interfaceUS20100251174 *Sep 30, 2010Sony CorporationWidget server, method of operating a widget server and method and device for providing a widget recommendationUS20100299622 *Apr 20, 2010Nov 25, 2010Canon Kabushiki KaishaRadiation imaging apparatus, display processing method of the same, and computer-readable storage mediumUS20110099487 *Jan 12, 2007Apr 28, 2011Nokia CorporationEnd-to-end solution for an end-user to obtain desired information in user interfacesUS20110099516 *Oct 28, 2009Apr 28, 2011Red Hat, Inc.Method for centralized application package distributionUS20110296523 *May 26, 2010Dec 1, 2011Microsoft CorporationAccess control management mapping resource/action pairs to principalsUS20120005593 *Jun 30, 2010Jan 5, 2012International Business Machines CorporationCare label method for a self service dashboard constructionUS20120054663 *Aug 24, 2011Mar 1, 2012Lg Electronics Inc.Mobile terminal and method of setting an application indicator thereinUS20120131471 *Nov 18, 2010May 24, 2012Nokia CorporationMethods and apparatuses for protecting privacy of contentUS20120324377 *Jun 15, 2011Dec 20, 2012Microsoft CorporationUser interface extensibility for web application development toolUS20130219313 *Dec 17, 2012Aug 22, 2013Yahoo! Inc.System and Method of Inter-Widget CommunicationUS20130346922 *Jun 20, 2013Dec 26, 2013Google Inc.Insitu actions within presentation of notificationsUS20140059454 *Jul 1, 2013Feb 27, 2014International Business Machines CorporationCare label method for a self service dashboard constructionUS20140298214 *Mar 29, 2013Oct 2, 2014Microsoft CorporationVisual Configuration and ActivationUSD665407 *Aug 14, 2012Microsoft CorporationDisplay screen with graphical user interfaceUSD744519 *Jun 25, 2013Dec 1, 2015Microsoft CorporationDisplay screen with graphical user interfaceUSD744522Jun 25, 2013Dec 1, 2015Microsoft CorporationDisplay screen with graphical user interface* Cited by examinerClassifications U.S. Classification715/810, 715/811, 715/741International ClassificationG06F3/00, G06F3/048Cooperative ClassificationG06F8/61, G06F9/4443, G06F3/0486, G06F3/0488, H04M1/72563, G06F3/04886, H04M1/2477, H04M1/72544, G06F3/04817European ClassificationH04M1/725F2, G06F3/0481H, G06F8/61, G06F3/0488T, G06F3/0488, G06F3/0486, H04M1/725F1G, G06F9/44WLegal EventsDateCodeEventDescriptionMay 5, 2006ASAssignmentOwner name: APPLE COMPUTER, INC., CALIFORNIAFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:FORSTALL, SCOTT;CHAUDHRI, IMRAN A.;LOUCH, JOHN O.;AND OTHERS;REEL/FRAME:017878/0725;SIGNING DATES FROM 20060407 TO 20060428Owner name: APPLE COMPUTER, INC.,CALIFORNIAFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:FORSTALL, SCOTT;CHAUDHRI, IMRAN A.;LOUCH, JOHN O.;AND OTHERS;SIGNING DATES FROM 20060407 TO 20060428;REEL/FRAME:017878/0725Apr 10, 2007ASAssignmentOwner name: APPLE INC., CALIFORNIAFree format text: CHANGE OF NAME;ASSIGNOR:APPLE COMPUTER, INC.;REEL/FRAME:019142/0969Effective date: 20070109Owner name: APPLE INC.,CALIFORNIAFree format text: CHANGE OF NAME;ASSIGNOR:APPLE COMPUTER, INC.;REEL/FRAME:019142/0969Effective date: 20070109Nov 8, 2011CCCertificate of correctionSep 25, 2013FPAYFee paymentYear of fee payment: 4RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services