Abstract: Personalized task management is provided. A “doodling” zone or pane is provided in association with an electronic task interface that allows for entry of sketches, notes, the playing of games, and the like in association with entry, editing and use of task or list items in the task interface. In addition, task items entered into the task interface may be associated with other information, including previously entered or accomplished tasks, third party task content, enterprise task content, or other content. As tasks are completed, a completing user may be rewarded with a variety of on-display animations, gifts, reward items and/or other positive feedback.

Abstract: An electronic personal assistant that uses task information to obtain task performance assistance and help content is provided. Tasks from an electronic tasks application may be utilized by the personal assistant application to search a variety of information sources for task performance functionality and help content related to the tasks. The personal assistant may provide functionality to help a user actually perform a given task. Alternatively, once help content is obtained, a new task may be generated or the related task may be modified to provide the help content or to provide a link to the help content. The personal assistant application may provide the help content in a separate user interface or cause an application from which the help content is obtained to be launched.

Abstract: Generation of a task or reminder in an electronic task list authoring surface from a variety of data or information locations or media without the need for launching a separate task or reminder application and without the need for moving focus away from an information location or media presently in use is provided. Generation of a task or task reminder may be accomplished from a variety of information locations or media. When an information item is flagged or captured and a task/reminder is generated, one or more pieces of metadata may be applied to the flagged information item for enhancing the subsequent use of the associated generated task or reminder.

Abstract: A triggering mechanism for generating task reminders based on contextual information associated with the tasks is provided. Contextual information may be extracted from a variety of sources and may be related to one or more tasks. Based on the contextual information, task reminders may be generated and may be presented in a manner that makes the task reminders more useful to an end user.

Abstract: A list authoring surface (LAS) is provided that includes a lightweight user interface component for entering, displaying, manipulating, and providing reminders for one or more tasks that takes the place of hand-written notes, scraps of paper, or “sticky” notes. The list authoring surface may be deployed across a multitude of software applications and may be readily accessed anywhere on a stationary or mobile desktop or display screen. Information may be manually or automatically entered into the list authoring surface user interface. An event timeline that uses a “fuzzy” reminder method allows for reminders to be associated with tasks where some tasks must be accomplished or must occur at hard dates/times, but where other tasks may be accomplished or may occur during soft or “fuzzy” date/time ranges.

Abstract: Tools and techniques are described for multi-threaded processing for opening and saving documents. These tools may provide load processes for reading documents from storage devices, and for loading the documents into applications. These tools may spawn a load process thread for executing a given load process on a first processing unit, and an application thread may execute a given application on a second processing unit. A first pipeline may be created for executing the load process thread, with the first pipeline performing tasks associated with loading the document into the application. A second pipeline may be created for executing the application process thread, with the second pipeline performing tasks associated with operating on the documents. The tasks in the first pipeline are configured to pass tokens as input to the tasks in the second pipeline.

Abstract: Tools and techniques are described for multi-threaded processing for opening and saving documents. These tools may provide load processes for reading documents from storage devices, and for loading the documents into applications. These tools may spawn a load process thread for executing a given load process on a first processing unit, and an application thread may execute a given application on a second processing unit. A first pipeline may be created for executing the load process thread, with the first pipeline performing tasks associated with loading the document into the application. A second pipeline may be created for executing the application process thread, with the second pipeline performing tasks associated with operating on the documents. The tasks in the first pipeline are configured to pass tokens as input to the tasks in the second pipeline.

Abstract: Tools and techniques are described for multi-threaded processing for opening and saving documents. These tools may provide load processes for reading documents from storage devices, and for loading the documents into applications. These tools may spawn a load process thread for executing a given load process on a first processing unit, and an application thread may execute a given application on a second processing unit. A first pipeline may be created for executing the load process thread, with the first pipeline performing tasks associated with loading the document into the application. A second pipeline may be created for executing the application process thread, with the second pipeline performing tasks associated with operating on the documents. The tasks in the first pipeline are configured to pass tokens as input to the tasks in the second pipeline.

Abstract: Automatic capture and population of task and list items in an electronic task or list surface via voice or audio input through an audio recording-capable mobile computing device is provided. A voice or audio task or list item may be captured for entry into a task application interface or into a list authoring surface interface for subsequent use as task items, reminders, “to do” items, list items, agenda items, work organization outlines, and the like. Captured voice or audio content may be transcribed locally or remotely, and transcribed content may be populated into a task or list authoring surface user interface that may be displayed on the capturing device (e.g., mobile telephone), or that may be stored remotely and subsequently displayed in association with a number of applications on a number of different computing devices.

Abstract: An electronic personal assistant that uses task information to obtain task performance assistance and help content is provided. Tasks from an electronic tasks application may be utilized by the personal assistant application to search a variety of information sources for task performance functionality and help content related to the tasks. The personal assistant may provide functionality to help a user actually perform a given task. Alternatively, once help content is obtained, a new task may be generated or the related task may be modified to provide the help content or to provide a link to the help content. The personal assistant application may provide the help content in a separate user interface or cause an application from which the help content is obtained to be launched.

Abstract: A triggering mechanism for generating task reminders based on contextual information associated with the tasks is provided. Contextual information may be extracted from a variety of sources and may be related to one or more tasks. Based on the contextual information, task reminders may be generated and may be presented in a manner that makes the task reminders more useful to an end user.

Abstract: Generation of a task or reminder in an electronic task list authoring surface from a variety of data or information locations or media without the need for launching a separate task or reminder application and without the need for moving focus away from an information location or media presently in use is provided. Generation of a task or task reminder may be accomplished from a variety of information locations or media. When an information item is flagged or captured and a task/reminder is generated, one or more pieces of metadata may be applied to the flagged information item for enhancing the subsequent use of the associated generated task or reminder.

Abstract: A list authoring surface (LAS) is provided that includes a lightweight user interface component for entering, displaying, manipulating, and providing reminders for one or more tasks that takes the place of hand-written notes, scraps of paper, or “sticky” notes. The list authoring surface may be deployed across a multitude of software applications and may be readily accessed anywhere on a stationary or mobile desktop or display screen. Information may be manually or automatically entered into the list authoring surface user interface. An event timeline that uses a “fuzzy” reminder method allows for reminders to be associated with tasks where some tasks must be accomplished or must occur at hard dates/times, but where other tasks may be accomplished or may occur during soft or “fuzzy” date/time ranges.

Abstract: Providing access to task lists via social communications systems is provided. A user may expose a list authoring surface and associated task lists to other users via one or more social communications systems. When another user attempts to access contents of the list authoring surface, the user attempting access may be required to provide permissions credentials, or the attempting user's social communications account may be designated as a permissioned account from which access to the contents of the list authoring surface may be obtained. Version control management may be applied to the accessed task lists to ensure accessing users receive access to most up-to-date versions of accessed task lists. Once an accessing user obtains access to a given task list, the accessing user may comment on accessed tasks, make changes to accessed tasks and/or collaborate on accessed tasks.

Abstract: A method and system for specifying alternate layouts of a user interface element of a display description is provided. In one embodiment, a display system provides a display description language that separates the definition of content of a user interface element from the layout of the user interface element. This separation allows alternate layouts to be specified that are conditionally applied to content of the user interface element without having to repeat the content. In another embodiment, the display system allows each element of a table to be positioned within a specific cell within the table.

Abstract: Tools and techniques are described for multi-threaded processing for opening and saving documents. These tools may provide load processes for reading documents from storage devices, and for loading the documents into applications. These tools may spawn a load process thread for executing a given load process on a first processing unit, and an application thread may execute a given application on a second processing unit. A first pipeline may be created for executing the load process thread, with the first pipeline performing tasks associated with loading the document into the application. A second pipeline may be created for executing the application process thread, with the second pipeline performing tasks associated with operating on the documents. The tasks in the first pipeline are configured to pass tokens as input to the tasks in the second pipeline.

Abstract: Technologies are described herein for improving a user experience during the rendering, or repainting, of a graphical interface. A user interface related transaction can be initiated in response to a requested user operation. One or more windows associated with the requested operation can be identified. User interface updates associated with the one or more identified windows can be double buffered. Completion of the requested operation can be detected. The transaction can be terminated in response to detecting completion of the requested operation. The double buffered user interface updates can be committed to a computer display after terminating the transaction.

Abstract: A method and system is generally directed to retrieving data from an external source and binding the data to a structure used in executing a UI script. The external source may be on a local machine located across a network. The UI script is transformed to a tree structure. The relevant portions of the tree structure are cloned and manipulated to insert the data from the external source. The cloned portions of the tree structure are then grafted back into the tree. The tree structure is then used to display the UI corresponding to the UI script that includes the data from the external source.

Abstract: A method and system for specifying alternate layouts of a user interface element of a display description is provided. In one embodiment, a display system provides a display description language that separates the definition of content of a user interface element from the layout of the user interface element. This separation allows alternate layouts to be specified that are conditionally applied to content of the user interface element without having to repeat the content. In another embodiment, the display system allows each element of a table to be positioned within a specific cell within the table.

Abstract: A “UI producer” is used to automatically instantiate extensible user interface (UI) windows. The automatically instantiated UI windows are based on dynamic definitions of those UI's. These UI definitions, which include descriptions of controls or other elements used to populate one or more UI windows, are read and interpreted by the UI producer prior to rendering the UI windows. In addition, these UI definitions may also define or reference one or more event handlers or “listeners” that are to be associated with particular controls, groups of controls, or entire UI windows so that the controls or UI windows are capable of interacting with an associated application. After reading the UI definitions, the UI descriptions are acted upon to automatically instantiate each UI window using at least one database of predefined controls and custom elements, with automatic layout rules being used to organize controls and elements within each UI window.