Workflow widgets

Abstract

Systems, methods, computer-readable mediums, user interfaces and other implementations are disclosed for workflow widgets. In some implementations, a widget workflow method includes: launching a widget at a first device; and updating the widget with content created at a second device.

Description

TECHNICAL FIELD

The disclosed implementations relate generally to graphical user interfaces.

BACKGROUND

A hallmark of modern graphical user interfaces is that they allow a large number of graphical objects or items to be displayed on a display screen at the same time. Leading personal computer operating systems, such as Apple Mac OS®, provide user interfaces in which a number of windows can be displayed, overlapped, resized, moved, configured, and reformatted according to the needs of the user or application. Taskbars, menus, virtual buttons and other user interface elements provide mechanisms for accessing and activating windows even when they are hidden behind other windows.

Although users appreciate interfaces that can present information on a screen via multiple windows, the result can be overwhelming. For example, users may find it difficult to navigate to a particular user interface element or to locate a desired element among a large number of onscreen elements. The problem is further compounded when user interfaces allow users to position elements in a desired arrangement, including overlapping, minimizing, maximizing, and the like. Although such flexibility may be useful to the user, it can result in a cluttered display screen. Having too many elements displayed on the screen can lead to “information overload,” thus inhibiting the user to efficiently use the computer equipment.

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 and accessed through a user interface, such as a “dashboard layer,” which is also referred to 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.”

The simplicity and utility of widgets and dashboards make them suitable alternatives or improvements to traditional workflow technologies (e.g., email, Instant Messaging, etc.)

SUMMARY

Systems, methods, computer-readable mediums, user interfaces and other implementations are disclosed for incorporating widgets into workflows.

In some implementations, a widget workflow method includes: launching a widget at a first device; and updating the widget with content created at a second device.

In some implementations, a widget workflow method includes: making a widget available to one or more subscribing devices, wherein the widget includes content at least some of which can be modified; receiving content updates from the one or more subscribing devices; if more than one content update is received, aggregating the content updates; and making the aggregated content updates available to at least one of the one or more subscribing devices.

In some implementations, a widget workflow method includes: receiving a request associated with a widget, the request including one or more commands and data; and executing the commands using at least some of the data.

In some implementations, a widget workflow system includes a workflow communication manager configured to facilitate workflow communications between a plurality of devices. A repository is coupled to the workflow communication manager and is configured to store workflow information received from devices.

Other implementations are disclosed which are directed to systems, methods, apparatuses, computer-readable mediums and user interfaces.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a hardware architecture for implementing dashboards.

FIG. 2 is a flow diagram of a process for activating and using a dashboard.

FIG. 3 is a block diagram of a software architecture for implementing dashboards.

FIG. 4A is a screen shot depicting a desktop user interface prior to activation of a dashboard.

FIG. 4B is a screen shot depicting an initial state for a dashboard.

FIG. 4C is a screen shot depicting a configuration bar for a dashboard.

FIG. 4D is a screen shot depicting user selection of a widget from the configuration bar.

FIG. 5 is a screen shot depicting an exemplary workflow widget as an attachment to an email application.

FIG. 6 is a screen shot depicting an exemplary user interface for a workflow widget.

FIG. 7 is a screen shot depicting an exemplary application for managing workflow widgets.

FIG. 8 is a block diagram depicting an exemplary workflow communication system for workflow widgets.

FIG. 9 is a block diagram of an exemplary software architecture for workflow widgets.

FIG. 10 is a flow diagram of an exemplary widget workflow process for a publishing device or server system.

FIG. 11 is a flow diagram of an exemplary widget workflow process for a subscribing device.

FIGS. 12A-12C illustrates communication with widgets using URL requests.

DETAILED DESCRIPTION

Hardware Architecture

FIG. 1 is a block diagram of a hardware architecture 100 for implementing workflow widgets. The architecture 100 includes a personal computer 102 coupled to a remote server 107 via a network interface 116 and a network connection 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.

The computer 102 also includes a local storage device 106 and a graphics module 113 (e.g., graphics card) for storing information and generating graphical objects, respectively. The local storage device 106 can be a computer-readable medium. The term “computer-readable medium” refers to any medium that participates in providing instructions to a processor for execution, including without limitation, non-volatile media (e.g., optical or magnetic disks), volatile media (e.g., memory) and transmission media. Transmission media includes, without limitation, coaxial cables, copper wire, fiber optics, and computer buses. Transmission media can also take the form of acoustic, light or radio frequency waves.

While workflow 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), televisions, etc.

A dashboard system and method for managing and displaying dashboards and workflow widgets 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 and widget functions, as described with respect of FIGS. 2-8. A dashboard system and method can also be implemented as one or more software applications running on the computer 102. In some implementations, a dashboard system can be another widget that is configurable to communicate with other widgets, applications and/or operating systems. A dashboard 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, widgets (including linked widgets) are described as a feature of an operating system. Workflow widgets, however, can be implemented in other contexts as well, including e-mail environments, desktop environments, application environments, hand-held display environments, and any other display environments.

Dashboard Overview

FIG. 2 is a flow diagram of an implementation of a process for activating and using one or more dashboard layers. A dashboard layer (also referred to herein as a “unified interest layer” or “dashboard”) is used to manage and display widgets (including linked 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. Alternatively, a dashboard layer can be invoked programmatically by another system, such as an application or an operating system, etc.

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.

In some implementations, the dashboard is overlaid on an existing user interface (UI) (e.g., a desktop UI). When the dashboard is activated, the existing UI may be faded, darkened, brightened, blurred, distorted, or otherwise altered to emphasize that it is temporarily inactivated. The existing UI may or may not be visible behind the dashboard. The UI can also be shrunk to a small portion of the display screen while the dashboard is active, and can be re-activated by clicking on it. In some implementations, the UI is shrunk and presented as a widget. The UI can be re-activated by clicking on the widget. In some implementations the UI remains active when the dashboard is active.

The user interacts with and/or configures widgets as desired (207). In some implementations, the user can move widgets around the screen, and can resize widgets if applicable. Some widgets are resizable and some have a fixed size. A widget author can specify whether a widget can be resized. Some widgets automatically resize themselves based on the amount or nature of the data being displayed. Widgets can overlap and or repel one another. For example, if the user attempts to move one widget to a screen position occupied by another widget, one of the widgets is automatically moved out of the way or repelled by the other widget.

In some implementations, the user dismisses the dashboard (208) by invoking a dismissal command, which causes the UI layer to return or re-present itself to the display screen. In some implementations, the dashboard is dismissed when the user presses a function key or key combination (which may be the same or different than the key or combination used to activate the dashboard), or clicks on a close box or other icon, or clicks on negative space within the dashboard (e.g., a space between widgets), or moves an onscreen cursor to a predefined corner of the screen.

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 can be 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.) is 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 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. 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 can 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. 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 an icon tray or menu system.

It should be apparent that there are many ways in which dashboards and widgets can be displayed other than those implementations described herein. For example, widgets can be displayed on any user interface or user interface element, including but not limited to desktops, browser or application windows, menu systems, trays, multi-touch sensitive displays and other widgets.

Software Architecture

FIG. 3 is a block diagram of a software architecture 300 for implementing dashboards for installing, displaying and launching workflow widgets. The software architecture 300 generally includes a dashboard server 301, one or more dashboard clients 302, 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 manages and launches the dashboard client 302 processes. 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. The dashboard clients 302 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 the dashboard layer that can be overlaid on a desktop user interface. In some implementations, the widgets 303 are rendered into the dashboard layer, which is drawn on top of the desktop user interface, so as to partially or completely obscure the desktop user interface while the dashboard layer is active.

Dashboard Server

The dashboard server 301 can be a stand-alone process or embedded in another process. 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: widget workflow, 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.”

Dashboard Client

In some implementations, a dashboard client 302 is a process that uses, for example, objects that are defined as part of a development environment, such as Apple Computer's Cocoa Application Framework (also referred to as the Application Kit, or AppKit) for the Mac OS® operating system. In some implementations, the dashboard clients 302 can be implemented as simplified browser screens that omit conventional interface features such as a menu bar, window frame, and the like.

Widget Format

In one implementation, each widget 303 is implemented as an HTML file. The HTML file can reference other local and remote resources such as style sheets (e.g., Cascading Style Sheets), other HTML files, JavaScript files, images, and the like. Widgets 303 can be implemented using, for example, a flat bundle file format or a packaged HTML file format. In some implementations, the Flat Bundle format includes an info.plist file.

The Info.plist files describes a widget 303 and provides an identifier for a widget 303. Table I provides an example of Info.plist file contents.

TABLE I
Example of Info.plist File Contents
Key	Type	Description/Value
CFBundleIdentifier	CFString	com.apple.widget
		<widget name>
CFBundleName	CFString	Name of the widget.
MainHTML	CFString	Name of main HTML
		resource.
Width	CFNumber	Default width of the
		widget.
Height	CFNumber	Default height of the
		widget.
DefaultImage	CFString	Resource name of
		default PNG file.
Plugin (optional)	CFString	Resource name of
		native plug-in.
AllowFileAccessOutsideofWidget	Boolean	Access to files across
		the file system; limited
		by the users
		permissions.
AllowFullAccess	Boolean	Access to the file
		system, Web Kit and
		standard browser
		plug-ins, Java applets,
		network resources,
		and command-line
		utilities.
AllowInternetPlugins	Boolean	Access to Web Kit and
		standard browser
		plug-ins.
AllowJava	Boolean	Access to Java applets.
AllowNetworkAccess	Boolean	Access to any
		resources that are not
		file based.
AllowSystem	Boolean	Access to command-
		line utilities using
		widget script object.

The keys AllowFileAccessOutsideofWidget, AllowFullAccess AllowlnternetPlugins, AllowJava, AllowNetworkAccess, and AllowSystem are Boolean types that can be set by a widget author to enable certain levels of resource access.

Dashboard Invocation

FIG. 4A 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. A dashboard does not have to be activated on a desktop; rather the dashboard can be activated and displayed on any display screen with or without a desktop.

FIG. 4B 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. 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.

In some implementations, the user can drag the icon 403 to any location on the screen, and the position of the icon 403 will remain persistent from one invocation of the dashboard layer 402 to the next. The user can click on the icon 403 to activate the configuration bar 408, as shown in FIG. 4C. The configuration bar 408 provides access to various widgets that can be placed on the dashboard. In some implementations, a text label is shown for each available widget (e.g., calculator, stocks, iTunes®, etc.). In some implementations, an icon is shown for each available widget (e.g., calculator icon 410). If many widgets are available, the widgets may be arranged hierarchically by type (e.g., game widgets, utility widgets, etc.), or alphabetically, or by any other categorization methodology. For example, a number of categories may be displayed, and clicking on one of the categories causes a pull-down menu to be displayed, listing a number of widgets in that category. In some implementations, a buy widget 406 is also available, allowing the user to select widgets from an online store or website.

Note that the particular configuration and appearance of configuration bar 408 in FIG. 4C is merely exemplary, and that many other arrangements are possible. For example, widgets can be installed from other locations, other applications or other environments, without requiring that they first be part of the configuration bar 408. The user can dismiss the configuration bar 408 by clicking on dismissal button or icon 404.

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 as is discussed below. 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.

FIG. 4D depicts the selection of the calculator widget icon 410 from the configuration bar 408. The calculator icon 410 which is 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, widgets in the configuration bar 408 are smaller than their actual size when installed. When the user clicks on a widget and begins to drag it into a dashboard or other display environment, the widget is animated to its actual or installed size to assist the user in the real-time layout of the dashboard. By animating the widget to its actual size, the user will know the actual size of the widget prior to its installation.

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 layer 402 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 dashboard layers (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 created 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 and installing widgets in a display environment. For example, a widget received as an email attachment can be launched by a user from directly within a user interface of the email application.

Widgets can be created 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 and installing 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.

In general, an installer process is used to provide additional functionality to the creation/instantiation process, beyond the simple drag and drop operation describe above. Additional functionality can include preview, security and deletion functionality in a singular interface. The installer process can be a separate process or combined in another process. The installer process can itself be a separate application that is executable to install widgets (or other elements) in a display environment. As used herein, the term “process” refers to a combination of functions that can be implemented in hardware, software, firmware or the like.

Workflow Widgets

FIG. 5 is a screen shot depicting an exemplary workflow widget as an attachment to an email application. Generally, workflow widgets can be used to simplify workflows that exist in every day life. Workflows are processes or procedures for accomplishing a task where two or more individuals interact to accomplish the task. Workflow widgets do not have to be related to work. Any process can benefit from workflow widgets, including processes that are performed solely for entertainment or enjoyment.

In some implementations, an email message window 506 is generated by an email application and displayed in a user interface 504 for presentation on a display device (e.g., computer, mobile phone, PDA, etc.). Attached to the email is a workflow widget 508. When a user clicks on the workflow widget 508, or otherwise interacts with it (e.g., mouse rollover), the workflow widget 508 is launched from within the email. Alternatively, the workflow widget 508 can launch itself when the user opens the email. In some implementations, the widget can be dragged from the email message window 506 and dropped into another display area (e.g., a dashboard, a desktop UI, etc.) or a configuration bar before it is launched. When the widget 508 is launched from within the email application it can register with one or more dashboards and become part of a dashboard even after the application is closed without further interaction with the user. In some implementations, the email includes a link, which when clicked by a user causes one or more widgets to be launched. The link can be a URL or Uniform Resource Identifier (URI), which contains information that can be used by a dashboard layer or operating system to launch a widget and populate the widget with data, as described with respect to FIGS. 12A-12C.

Although the implementation described above includes an email application, workflow widgets can be delivered using any known communication applications or techniques, including but not limited: instant messaging, Internet conferencing and the like. Generally, workflow widgets are widgets that are capable of receiving data from users, other widgets, URL Requests or any other information source for purposes of simplifying or accomplishing a work-related process. An exemplary operation of a workflow widget 508 will now be described through the perspective of four individuals (Greg, Scott, Imran and Eric) who are throwing a party for a mutual friend (John).

Greg decides to throw a potluck party for his colleague John. He composes an email to Scott on his desktop computer, attaches a party planning widget 508 using attachment mechanisms included with known email applications (e.g., Apple Computer's Mail application, Microsoft's Outlook® application, etc.), and sends the email to Scott using a known email protocol (e.g., Post Office Protocol (POP), Internet Message Access Protocol (IMAP), etc.). Scott receives the email on his PDA device and launches the attached party planning widget 508. The party planning widget 508 presents a user interface, which includes information about the party and a list of items that people are bringing to the party. FIG. 6 is a screen shot depicting an exemplary user interface 600 for the party planning widget 508.

In some implementations, the email includes a link (e.g., a URL or URI), which when opened will cause an instance of one or more widgets associated with the link to be generated by, for example, a dashboard server or other process, as described with respect to FIGS. 12A-12C.

Referring to FIG. 6, the user interface 600 is shown displayed in the desktop UI 504. The user interface 600 can be minimized, closed or resized like a conventional user interface or window using various control mechanisms (e.g., a button). In a first pane 604 of the UI 600, Greg has typed a message to Imran, Scott and Eric, requesting that they each bring an item to the party. In a second pane 606 of the UI 600, the names of the workflow participants (Greg Imran, Scott, Eric) are listed. Next to each name is the item that they will bring to the party or a text box that can be filled in by the participant. In this example, Greg is bringing hot dogs, Imran is bringing condiments and Eric is bringing apple pie. Each of these individual had previously received the party widget 508 on their respective devices (e.g., mobile, phone, PDA, portable computer, etc.) and have selected an item.

Since Scott has not yet selected an item, his name is highlighted or otherwise altered to indicate his pending status. Scott elects to bring soda pop, so he types in the words “Soda Pop.” When Scott is finished selecting his item, he clicks a send button 608 or other input mechanism to complete the process. When the send button 608 is clicked, the widget sends the updated list back to Greg's device. The updated list can be sent using known email or instant messaging protocols (e.g., POP3, IMAP, Session Initiation Protocol (SIP), Extensible Messaging and Presence Protocol (XMPP), etc.).

Upon receipt of the updated list, Greg can further change the item list and/or push the updated list to the other party planners, as described with respect to FIGS. 9-11. The updated list appears in the user interface 600 for each party planner. Therefore, Greg was able to create a party workflow widget, send the widget to each party planner, collect and aggregate updates received from each of the party planners through the party planning widget 508, incorporate the updates into an aggregated update and push the update back to the party planning widgets 508 residing at the respective devices of the workflow participants. The push can be accomplished using known software push technologies (e.g., PointCast™, Astound™, Marimba™, BackWeb™, Intermind™, InterAgent™, etc.) and/or known instant messaging protocols (e.g., SIP, XMPP, etc.).

The party planning widget 508 described above is exemplary. There are many other workflows that could benefit from the use of a workflow widget. Other examples of workflow widgets include but are not limited to: a calendar workflow widget that allows participants to modify timelines, schedules, milestones and other time-based events for a project; an auction widget that allows participants to auction items or services and place bids; a polling widget that allows participants to cast votes or provide commentary which can be shared with other participants in an opinion poll or election; a purchase order widget that facilitates the procurement and supply of products or services, including the exchange of offers, acknowledgments, bids, change orders, return material authorizations and the like; and a chat widget that allows participants to discuss a topic of their choosing.

Managing Workflow Widgets

FIG. 7 is a screen shot depicting an exemplary application for managing workflow widgets. Some users may receive large numbers of workflow widgets from a variety of sources. Many of these widgets may required a response or information from the user. For such users, a workflow widget management application can be invoked for organizing and managing workflow widgets. In some implementations, workflow widgets are managed by a management application that can be invoked by a user through a menu bar 502, button or other input mechanism. Alternatively, the management application can be invoked or launched automatically when workflow widgets are received or programmatically by other applications (e.g., word processors, browsers, etc.). In some implementations, the management application can be launched by the user clicking on an associated icon 714 in a configuration bar 718.

In some implementations, when the management application is launched a user interface 708 is displayed. For example, the user interface 708 can be displayed in a dashboard layer 706 overlaying a desktop UI 504. The UI 708 can include a navigation pane 710 for displaying a file structure that includes folders for organizing workflow widgets. Similar to conventional email file structures, there can be an inbox folder, outbox, sent item folder, follow-up folder, quarantine folder, search folder, junk widget folder, and other suitable folder for storing widgets in an organized manner. The UI 708 can also include a reading pane 716 for displaying the contents of the various folders listed in the navigation pane 710. For example, when the inbox folder is selected, then the reading pane 716 displays the contents of the user's inbox. In this example, icons 712 associated with workflow widgets are displayed in the reading pane 716. In some implementations, the user can click on the widget icons 712 and the associated widgets will launch and display a user interface 600, as described with respect FIG. 6.

It should be apparent that the UI 708 is exemplary and other UIs are possible, which can include various features for organizing workflow widgets, including features found in conventional email applications (e.g., rules and alerts, out of office assistants, requests for receipts, etc.).

Workflow Communication System

FIG. 8 is a block diagram depicting an exemplary workflow communication system 800 for workflow widgets. The system 800 provides a peer-to-peer or client/server infrastructure for workflow widgets. The system 800 generally includes a publishing device 802, one or more subscriber devices 804 and a server system 808. The server system 808 is coupled to a repository 806. The publishing device 802 and the subscribing devices 804 can communicate with the server system 808 (client/server implementations) and/or with each other (peer-to-peer). For a peer-to-peer topology, the workflow information repository 806 can be included as part of the publishing device 802 (e.g., a computer hard drive). An advantage of the peer-to-peer topology is that any subscriber device 804 can be a publishing device 802 and can maintain a workflow information repository 806. The workflow can continue even if one of the subscriber devices 804 is offline. In some implementations, the system 800 operates with a client/server topology under normal operating conditions, but can reconfigure into a peer-to-peer topology if the server system 808 is down.

In some implementations, the publishing device 802 belongs to the original author of the workflow widget. Using the previous example, Greg was the original author of the party planning widget 508 (FIG. 5). In some implementations, the party planning widget 508 can be authored by Greg at the publishing device 802 (e.g., a desktop computer) using a widget authoring and editing environment, such as the environment described in co-pending U.S. patent application Ser. No. 11/145,577, entitled “Widget Authoring and Editing Environment,” filed Jun. 3, 2005. Alternatively, the party planning widget 508 can by created by another individual or entity and simply customized by Greg. For example, the party planning widget 508 could be included with an operating system or downloaded from a third party website. In some implementations, the party planning widget 508 can be provided by a third party service provider, which allows Greg to select from a library of widgets and to customize the widget over a network connection (e.g., the Internet, wireless, etc.). In such an implementation, the third party service provider can maintain the widget authoring and editing environment, and also establish and maintain network connections with one or more subscribing devices (e.g., PDA, portable computer, mobile phone, etc.).

After creating the party planning widget 508, Greg sends the widget to each of the subscribing devices 804 as an attachment to email or by other known communication means. Alternatively, Greg can push the party planning widget 508 to each subscriber device 804 using a push technology (e.g., PointCast™, Intermind™, etc.). The party planning widget 508 can be received at the subscribing devices 804 by, for example, the management application described with respect to FIG. 7. A subscribing device 804 can be any device capable of receiving information over a communication link or channel, including but not limited to: portable and desktop computers, servers, electronics, media players, game devices, mobile phones, email devices, personal digital assistants (PDAs), televisions, etc. For example, Imran can receive the party planning widget 508 on a portable PC 804a, Scott can receive the party planning widget 508 on a PDA 804b and Eric can receive the party planning widget 508 on a mobile phone. Once the party planning widget 508 is received, it can be interacted with as described with respect to FIGS. 5 and 6. If the party planning widget 508 is already installed on a subscribing device 804, then Greg could send an email with a link that can be used to launch the party planning widget 508 at the subscriber device 804, as described with respect to FIGS. 5 and 6. Other methods or systems for distributing a workflow widget to subscriber devices are possible. For example, each subscriber device 804 could download or otherwise obtain a copy of the workflow widget (or link) directly from the server system 808 or from a third party distributor.

Software Architecture

FIG. 9 is a block diagram of an exemplary software architecture 900 for workflow widgets. The architecture 900 can be a stand-alone application or part of an operating system process, component and/or plug-in. The software architecture can also be characterized as a framework or model that can be implemented on various platforms and/or networks (e.g., peer-to-peer or 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.).

The architecture 900 includes a dashboard server 906, dashboard clients 902, widgets 904, operating system 914 and a workflow information repository 912. The architecture 900 is similar to the dashboard architecture 300 shown in FIG. 3 and operates in a similar manner. In the architecture 900, however, the dashboard server 906 also includes a workflow communication manager 908 and a workflow environment manager 910. In a publishing device or server system (e.g., publishing device 802 or server system 808), the workflow communication manager 908 is responsible for establishing connectivity, establishing sessions and managing the transfer of information to subscribing devices 804. In a subscribing device (e.g., a subscribing device 804), the workflow communication manager 908 performs a similar function with respect to the publishing device 802 or server system 808. Depending upon the status of the device (i.e., publishing or subscribing), the workflow communication manager 908 includes one or more software components for transmitting workflow widgets, collecting updates from subscribing devices, publishing widgets, pushing updates to subscribing devices and any other tasks related to workflow communication.

Depending upon the status of the device, the workflow environment manager 910 is responsible for managing workflow widgets, authoring or editing workflow widgets, and any other tasks associated with the installation, previewing, launching, updating, operation or interaction with workflow widgets, including generating and displaying the user interfaces described with respect to FIGS. 6 and 7.

The workflow information repository 912 is coupled to the dashboard server 906, and can be used to store information regarding the workflow widgets, publishing devices and subscribing devices, etc. In subscribing devices, it can be used to store a log or history of interactions with a workflow widget. The repository 912 can also store various configuration data associated with workflow widgets, dashboards, security information, etc.

The workflow communication manager 908 and the workflow environment manger 910 do not have to be part of the dashboard server 906. Rather, these components can be standalone applications or an operating system component, process, and/or plugin.

Widget Workflow Process

FIG. 10 is a flow diagram of an exemplary widget workflow process 1000 for the publisher device or server system depending on the topology employed. The steps of process 1000 does not have to occur in any specific order and at least some steps can be performed in parallel in a multithreading and/or multiprocessing environment.

Workflow widgets can operate in a variety of networks including but not limited to peer-to-peer networks and client/server networks. These networks can include publishing widgets and subscribing widgets. In a peer-to-peer network each device can be both a publishing device and a subscribing device. In such a network, the device that starts the workflow can be referred to as a publishing device. In some implementations, the publishing device will keep track of the workflow information (e.g., number of subscribing devices, updates from subscribing devices, etc.) and the workflow state (e.g., phase of completion, etc.).

In a client/server network, a server system maintains workflow information and status for subscribing devices. The server system can be operated by a service provider that charges a subscription fee. In some implementations, workflow widgets can be bundled with other services (e.g., email, Internet access, etc.). Users of subscribing devices can generate workflow widgets by interacting with the server system. For example, a user can use a browser to search a library of workflow widgets for a suitable workflow widget, then configure the widget as desired by, for example, adding or modifying content and specifying one or more subscribing devices that will receive the widget. The server system then establishes connections with subscribing devices and sends the workflow widget to each subscribing device (e.g., via email). Any updates to the content of the workflow widget made at the subscribing devices can be aggregated by the server system and stored in a workflow information repository (e.g., the repository 912).

Process Flow at the Publishing Device/Server System

The widget workflow process 1000 can begin when a workflow widget is created and sent to one or more subscribing devices (1002). In some implementations, the widget can be created using a widget authoring and editing application, as described in U.S. patent application Ser. No. 11/145,577, entitled “Widget Authoring and Editing Environment,” filed Jun. 3, 2005. Alternatively, an existing workflow widget can be modified to include content, such as files, documents, text messages, instructions, images, music, video, audio, software, URLs or URIs and any other information or materials for carrying out a workflow. For example, a workflow widget can include a URL to a website containing additional information or materials (e.g., documents or other widgets) for carrying out the workflow. In some implementations, a link is sent to the subscribing devices. The link can be used to launch existing workflow widgets at the subscribed device or steer the subscriber device to a third party website for downloading a workflow widget. Other distribution methods and systems are possible.

After the workflow widget (or link) is created and sent to the subscribing devices, any content included with the workflow widget can be periodically updated by the subscribing devices and/or the publishing device or server system and made available to all the devices (1004). The content can be updated using known technologies and protocols (e.g., email, Internet conferencing, push technology, etc.), and the updates can be transmitted over a variety of transmission mediums (e.g., copper, radio frequency (RF), optical, acoustic, etc.).

When the subscribing devices receive the workflow widget, users of the subscribing devices can interact with the widget and update its contents. An exemplary interaction with a workflow widget was described with respect to FIGS. 2 and 3. Any updates to the widget contents made by users of subscribing devices can be reported back to the publishing device or a server system and stored in a workflow information repository (FIG. 8). In some implementations, the publishing device or server system requests update reports from subscribing devices using a polling scheme. Alternatively, the subscribing devices can report back updates to the publishing device or server system based on a trigger event (e.g., the user presses the send button shown in FIG. 6), or according to a schedule (e.g., once a day, Friday at 5:00 PM, etc.). In some implementations, the publishing device or server system publishes the content updates and notifies the subscribing devices when content updates are available. The subscribing devices can then seek out the content updates which can be stored, for example, in a workflow information repository (e.g., repository 912) at the publishing device or server system.

When the publishing device or server system receives the content update reports from the subscriber devices (1006), the publishing device or server system can aggregate the content update reports into a single update for that can be made available to one or more subscribing devices (1008). In some implementations, the content update reports are aggregated by comparing the content update reports to a current state of the content stored and maintained at the publishing device or server system, then aggregating the content based on the results of the comparisons. For example, the publishing device or server system can determine any differences between the content update reports and the current state of the content stored at the publishing device or server system, and then aggregate the differences into a single content update that can be made available to one or more subscribing devices (1004), and the state of the content stored at the publishing device or server system can be updated to reflect the differences. In the party planning example, Greg receives a content update report from Scott, including an updated item list that now includes soda pop (FIG. 6). The publishing device or server system, can then aggregate Scott's content update report with any other content update reports from other subscribing devices (including any updates that Greg may have made using the publishing device), and publish the updates and/or push the updates to the subscribing devices, so that Imran, Scott and Eric have a complete item list and know the item that each friend will bring to the party.

The implementations described above enable the content of a workflow widget to be periodically updated on subscribing devices and the publishing device or server system, so that the subscribing devices and the publishing device or server system can provide their respective users with current content while allowing each device to asynchronously change the content. Thus, the workflow widget can simplify a workflow process by providing the current content to multiple participants in the workflow process, allowing the participants to update or modify the content, and then ensuring that any changes to the content are provided to the participants in a timely manner (e.g., real-time or near real-time).

In some implementations, the publishing device or server system tracks the progress of the workflow and will communicate with subscribing devices to manage the workflow process to ensure its completion. For example, if Scott does not interact with the workflow widget for a predetermined period of time, the publishing device or server system can send a message (e.g., email, instant message, telephone call, etc.) to the subscribing device requesting a response. In some implementations, the publishing device or server system monitors the presence of the subscribing devices and sends messages only when the subscribing device is present (i.e., available for receiving communications). The various features associated with the publishing device or server system can be configured by a user (e.g., Greg) through a preference pane or other input mechanism. For example, Greg can set the publishing device or server system to notify him when updates are received or if a subscribing device has failed to respond.

FIG. 11 is a flow diagram of an exemplary widget workflow process 1100 for the subscriber devices. The process 1100 begins when a subscribing device receives a workflow widget from a publishing device or server system (1102). In some implementations, when the workflow widget is received it is automatically installed and launched on the subscribing device (1104). Alternatively, the subscribing device can request authorization to install prior to installing. In some implementations, the user can preview the contents of the workflow widget, as described in co-pending U.S. patent application Ser. No. 11/282,110, for “Preview Including Theme Based Installation of User Interface Elements In A Display Environment.”

In some implementations, the workflow widget is authenticated or subjected to other security procedures before being installed or launched. For example, the workflow widget can be signed by the publishing device or server system and authenticated by the subscribing devices using known authentication techniques (e.g., asymmetric public key encryption, elliptic encryption, etc.)

When the workflow widget is installed and launched, the users of the subscribing devices can interact with the widget and update its contents (1106). The updates are then sent back to the publishing device or server system (1108) where they are aggregated and used to prepare updates for the subscribing devices participating in the workflow, as described with respect to FIG. 10. In some implementations, applications that are local to the subscribing devices can be updated using the updated content of the workflow widget (1110). For example, Scott's Outlook® calendar can be updated by the workflow widget with the date and time of the party, and a task can be created in an Outlook® task list for reminding Scott to bring the soda pop.

In addition to sending updates to the publishing device or server system, the subscribing devices also periodically receive or seek published updates from the publishing device or server system. The updates can be made available to all subscribing devices in parallel (e.g., multicasting) or to individual subscribing devices serially in accordance with a predetermined order. If updates are received or retrieved from the publishing device or server system, then the subscribing device will update itself with the updates and notify the user that an update has occurred (1112). For example, after Scott's update report is received by the publishing device or server system, the publishing device or server system aggregates Scott's updates with any other updates from other subscribing devices (including the publishing device or server system) and pushes (or publishes) the updates to the subscribing devices participating in the workflow, as described with respect to FIG. 10.

It should be apparent that the communication between publishing devices and subscribing devices can be implemented using a variety of known network topologies and technologies.

Communicating with Widgets Using URL Requests

As described with respect to FIGS. 5 and 6, links associated with workflow widgets can be included in user interfaces (e.g., email). When a link is selected one or more widgets associated with the link can be instantiated or launched and displayed. In some implementations, the link can be a URL request which can be used to facilitate the communication of information between a workflow widget and a web page, another widget, a dashboard or any other information resource. Generally, URL Requests can include a message body which can be used to communicate any information (e.g., files, images, data, etc.) to widgets. Widgets can use URL Requests to communicate directly with each other or indirectly through other processes or systems (e.g., a dashboard server), as described more fully in U.S. patent application Ser. No. 11/403,644, entitled “Linked Widgets.”

A process can be a widget or application and can communicate with one or more application or operating system processes (e.g., Word, email, Mac OS, etc.). In some implementations, URL Requests are handled by a dedicated process, which receives messages, data and other information from URLs, and distributes it or otherwise makes it available to one or more client processes (e.g., widgets, applications, other processes, etc.).

An exemplary URL Request for communicating between a process (e.g., a web page) and a widget can have the following format:

“dashboard-widget:new=com.apple.widget.helloweb?message=New.”

The various components of this exemplary URL Request are described in Table I below.

TABLE I
Exemplary URL Request Format
Field                     Function
dashboard-widget:         Notifies the browser that the link is
                          directed towards a dashboard.
new=                      A command that informs a dashboard to
                          provide a new widget. In this example,
                          there are six commands to choose from:
                          “new=” - Provides a new widget
                          based on a bundle identifier.
                          “newWithPath=” - Provides a
                          new widget based on a path.
                          “open=” - Provides a new
                          widget if it does not exist, based
                          on a bundle identifier.
                          “openWithPath=” - Provides a
                          new widget if it does not exist,
                          based on a path.
                          “send=” - Sends data to an
                          existing widget. If the widget does
                          not exist, then nothing happens.
                          “sendWidthID =” - Sends data
                          to an existing widget based on its
                          widget.identifier.value. If the widget
                          does not exist, then nothing happens.
com.apple.widget.helloweb A bundle identifier for a target widget
                          named “Hello Web.”
?                         Anything after ? is a query stream.
                          Separates the identification portion of
                          the URL Request from the data to be
                          passed to the widget “Hello Web.”
message                   An arbitrary key for the next bit of
                          data that is passed to the target widget.
                          Inside of the widget “Hello Web,” this
                          key can be accessed through an array.
=                         Separates a key from its corresponding
                          value in a key = value pair.
new                       An arbitrary string. This value is
                          returned when the previous key in the
                          widget is requested.
@                         Separates key-value pairs to allow
                          multiple key-value pairs to be sent to
                          a widget in a single URL Request.

Examples Commands

It should be apparent that many types of commands and data can be used with a URL Request. Examples of three commands will now be described with respect to FIGS. 12A-12C.

The “new=” command opens a new widget based on a supplied bundle identifier (new=) or a supplied path (newWithPath=). The new widget can include a property that contains an associative array in which one or more key-value pairs can be parsed and stored for use by the widget “Hello Web.” For example, dashboard-widgetnew=com.apple.widget.helloweb?message=New,” would open a new “Hello Web” widget. FIG. 12A illustrates how the widget would be displayed.

The “send=&sendWithIdentifier=” command sends data to an existing widget based on a supplied bundle identifier (send=) or a widget identifier (sendWithldentifier=). A property in the widget can be assigned to a handler. The handler can be passed an associative array containing key-value pairs found in the data portion of a URL Request. For example, “dashboard-widget:send=com.apple.widget.helloweb?message=Send” would send a message to an existing instance of the “Hello Web” widget. FIG. 12B illustrates how the widget would be displayed.

The command “open=&openWithPath=” acts like a “send=” command if a widget of the specified bundle identifier or path already exists, and acts like a “new=” command if a widget of the specified bundle identifier or path does not already exist. For example, “dashboard-widget:Open=com.apple. widget.helloweb?message=Open” either sends a message to an existing instance of the Hello Web widget or creates a new instance if none exists. FIG. 12C illustrates how the widget would be displayed.

It will be understood by those skilled in the relevant art that the above-described implementations are merely exemplary, and many changes can be made without departing from the true spirit and scope of the present invention. Therefore, it is intended by the appended claims to cover all such changes and modifications that come within the true spirit and scope of this invention.

Claims

1. A method comprising: executing a first widget on a first device, the first widget including information and an executable application, executing the first widget including presenting the information of the first widget on the first device;sending the first widget to a second device;updating the first widget with content created using a second widget on the second device, wherein the second widget is launched on the second device using the information in the first widget sent by the first device, the updating including updating the information of the first widget;pushing the updated information from the first device or the second device to a publishing device or a server system; andpresenting the updated information within the first widget.

2. The method of claim 1, wherein executing the first widget comprises: determining if the first widget is installed; andif the widget is not installed, installing the widget in a display environment.

3. The method of claim 2, where the display environment is a layer that is drawn on top of a user interface using an effect or animation.

4. The method of claim 2, where installing the widget includes: previewing the widget in the display environment.

5. The method of claim 2, where installing the widget includes authenticating the widget.

6. The method of claim 5, where a state of the first widget is preserved when the display environment is inactive.

7. The method of claim 1, where the information is referenced by a uniform resource identifier (URI).

8. A system comprising: one or more processors;memory coupled to the one or more processors and configured to store instructions, which, when executed by the one or more processors, causes the one or more processors to perform operations comprising: executing a first widget on a first device, the first widget including information and an executable application, executing the first widget including presenting the information of the first widget; sending the first widget to a second device;updating the first widget with content created using a second widget on the second device, wherein the second widget is launched on the second device using the information in the first widget sent by the first device, the updating including updating the information of the first widget; andpushing the updated information from the first device to a publishing device or a server system.

9. The system of claim 8, wherein executing the first widget comprises: determining if the widget is installed; andif the widget is not installed, installing the widget in a display environment.

10. The system of claim 9, where the display environment is a layer that is drawn on top of a user interface using an effect or animation.

11. The system of claim 9, where installing the widget includes: previewing the widget in the display environment.

12. The system of claim 9, where installing the widget includes authenticating the widget.

13. The system of claim 12, where a state of the first widget is preserved when the display environment is inactive.

14. The system of claim 8, where the information is referenced by a uniform resource identifier (URI).

15. The system of claim 8, wherein each of the publishing device and the one or more subscribing devices is a computing device, and the publishing device communicates with the one or more subscribing devices through a peer-to-peer network.

16. The system of claim 8, wherein each of the publishing device and the one or more subscribing devices is a computing device, and the publishing device communicates with the one or more subscribing devices through the server system.

17. The system of claim 8, wherein each of the one or more subscribing devices is configured to present the information to a respective user.

18. A non-transitory, computer-readable storage medium having stored thereon instructions, which, when executed by one or more processors, causes the one or more processors to perform operations comprising: executing a first widget on a first device, the first widget including information and an executable application, executing the first widget including presenting information referenced by the first widget; sending the first widget to a second device;updating the first widget with content created using a second widget on the second device, wherein the second widget is launched on the second device using the information in the first widget sent by the first device, the updating including updating the information of the first widget; andpushing the updated information from the first device to a publishing device or a server system.