Adobe, Inc.

Jesper Storm Bache

Bradee Rae Evans

Joel Richard Brandt

David Tristram

John K Fitzgerald

Ian A Wehrman

Barkin Aygun

John N Fitzgerald

Timeline creation of electronic document creation states is described. In one or more implementations, document creation states are created responsive to performing editing operations on a document. Document creation state snapshots are then generated for respective document creation states responsive to the document creation states meeting at least one criterion. The at least one criterion may be based on an amount of change in the document, completion of an editing operation, specific alterations to the document, a user request to create a document creation state snapshot, and so on. The resulting document creation state snapshots along with visual representations of metadata associated with the respective document creation states are compiled into a single timeline in a chronological order of when the respective document creation states occurred.

Timeline creation of electronic document creation states

Systems and methods provide for a visual history of state changes for content of a document that is being modified within a content editing application. When modifications are made to the content within the content editing application, the modifications are recorded as state changes, and a graphical representation is generated for the modified content at each state change. The graphical representations with associated state changes are presented in a visual history area allowing the user to visually identify the state of the content corresponding to each graphical representation. The user can select a particular graphical representation from the visual history area and the content is transformed to the state corresponding to the selected graphical representation.

Visual history for content state changes

Techniques for providing enhanced graphics in a user interface by efficiently using enhanced graphics resources. A computing device displays the enhanced graphics in an upper view of the user interface and the enhanced graphics resources identify a visual region in which the enhanced graphics are positioned. The computing device accesses the enhanced graphics resources to identify and store a hit test region based on the visual region. The hit test region is stored separately from the enhanced graphics resources for hit testing. When a hit is received in the user interface, the computing device determines whether the upper view or lower view will respond to the hit based on the hit test region that is stored separately from the enhanced graphics resources.

Graphics performance for complex user interfaces

Inter-context coordination to facilitate synchronized presentation of image content is described. In example embodiments, an application includes multiple execution contexts that coordinate handling user interaction with a coordination policy established using an inter-context communication mechanism. The application produces first and second execution contexts that are responsible for user interaction with first and second image content, respectively. Generally, the second execution context provides a stipulation for the coordination policy to indicate which execution context is to handle a response to a given user input event. With an event routing policy, an event routing rule informs the first execution context if a user input event should be routed to the second execution context. With a pixel authorization policy, a pixel authorization grant informs the first execution context of an authorization to manipulate pixels of the second image content in response to a user input event affecting pixels of the first image content.

Inter-context coordination to facilitate synchronized presentation of image content

A customized configuration of controls on a dynamic keyboard is provided for an application using a control configuration file separate from the application. The control configuration file includes a control configuration for each custom control and a layout description. Each control configuration includes a visual description and a command description for a corresponding custom control. The visual description provides data regarding visual aspects of the custom control, while the command description includes data regarding behavioral aspects of the custom control. The layout description includes data for positioning visual representations of the custom controls on a dynamic keyboard. When the application is launched, a storage location is scanned to identify the control configuration file, and the control configuration file is used to configure the custom controls on the dynamic keyboard.

Growing community of inventors

Menlo Park, CA, United States of America

Jesper Storm Bache