Abstract: A touch input mode may be entered and exited automatically and/or manually. When the touch input mode is entered, user interface (UI) elements are optimized for touch input. When the touch input mode is exited, the user interface (UI) elements are optimized for hardware based input. A user may enter the touch input mode by manually selecting a user interface element and/or by entering touch input. Settings may be configured that specify conditions upon which the touch input mode is entered/exited. For example, the touch input mode may be configured to be automatically entered upon undocking a computing device, receiving touch input when in the hardware based input mode, and the like. Similarly, the touch input mode may be configured to be automatically exited upon docking a computing device, receiving hardware based input when in the touch input mode, and the like.

Abstract: A touch input mode may be entered and exited automatically and/or manually. When the touch input mode is entered, user interface (UI) elements are optimized for touch input. When the touch input mode is exited, the user interface (UI) elements are optimized for hardware based input. A user may enter the touch input mode by manually selecting a user interface element and/or by entering touch input. Settings may be configured that specify conditions upon which the touch input mode is entered/exited. For example, the touch input mode may be configured to be automatically entered upon undocking a computing device, receiving touch input when in the hardware based input mode, and the like. Similarly, the touch input mode may be configured to be automatically exited upon docking a computing device, receiving hardware based input when in the touch input mode, and the like.

Abstract: A touch input mode may be entered and exited automatically and/or manually. When the touch input mode is entered, user interface (UI) elements are optimized for touch input. When the touch input mode is exited, the user interface (UI) elements are optimized for hardware based input. A user may enter the touch input mode by manually selecting a user interface element and/or by entering touch input. Settings may be configured that specify conditions upon which the touch input mode is entered/exited. For example, the touch input mode may be configured to be automatically entered upon undocking a computing device, receiving touch input when in the hardware based input mode, and the like. Similarly, the touch input mode may be configured to be automatically exited upon docking a computing device, receiving hardware based input when in the touch input mode, and the like.

Abstract: A touch input mode may be entered and exited automatically and/or manually. When the touch input mode is entered, user interface (UI) elements are optimized for touch input. When the touch input mode is exited, the user interface (UI) elements are optimized for hardware based input. A user may enter the touch input mode by manually selecting a user interface element and/or by entering touch input. Settings may be configured that specify conditions upon which the touch input mode is entered/exited. For example, the touch input mode may be configured to be automatically entered upon undocking a computing device, receiving touch input when in the hardware based input mode, and the like. Similarly, the touch input mode may be configured to be automatically exited upon docking a computing device, receiving hardware based input when in the touch input mode, and the like.

Abstract: A database tier maintains and provides access to a database. An application tier receives and responds to requests for a form. The form includes data defining a first UI control for displaying a first value from the database and a second UI control for displaying a second value from the database that is dependent upon the first value. A client tier renders the form to show the first value in the first UI control and to show the second value in the second UI control. The client tier also detects a modification to the first value and causes an updated second value to be generated in response to detecting the modification to the first value. The updated second value is displayed by way of the second UI control. The updated second value is generated at the client tier, the application tier, the database tier, or at a combined application/database tier.

Abstract: Animation for the expansion and collapse of content in a user interface may be provided. The user interface may be displayed by a computer and may contain a content surface for editing content. The content may include a top data row and data items in rows below the top data row on the content surface. The computer may then receive an input to expand/collapse the data items into the top data row. The computer may then animate a display of the data items expanding/collapsing into the top data row. Animation for the sorting of content in a user interface may also be provided. The user interface may be displayed by a computer and may contain a content surface for editing a plurality of rows containing content. The computer may then receive a request to sort the content. The computer may then animate a sort of the content.

Abstract: A touch input mode may be entered and exited automatically and/or manually. When the touch input mode is entered, user interface (UI) elements are optimized for touch input. When the touch input mode is exited, the user interface (UI) elements are optimized for hardware based input. A user may enter the touch input mode by manually selecting a user interface element and/or by entering touch input. Settings may be configured that specify conditions upon which the touch input mode is entered/exited. For example, the touch input mode may be configured to be automatically entered upon undocking a computing device, receiving touch input when in the hardware based input mode, and the like. Similarly, the touch input mode may be configured to be automatically exited upon docking a computing device, receiving hardware based input when in the touch input mode, and the like.

Abstract: Technologies are described herein for generating a platform-independent data application. In one method, a definition of a data schema is received for defining data types. A definition of a user interface is also received for access data stored in the data types. Further, a definition of business logic is received for enforcing validation rules and actions associated with the data types. The definitions of the data schema, the user interface, and the business logic are each received in a platform-independent format and used to generate the platform-independent data application.

Abstract: When a user uses touch to interact with an application, a contextual touch user interface (UI) element may be displayed that includes a display of commands that are arranged in sections on a tool panel that appears to float over an area of the display. The sections include a C/C/P/D section, an object specific section and may include a contextual trigger/section and an additional UI trigger. The C/C/P/D section may comprise one or more of: cut, copy, paste and delete commands. The object specific section displays commands relating to a current user interaction with an application. The contextual trigger/section displays contextual commands and the alternative trigger section displays another UI element comprising more commands when triggered.

Abstract: An improved user interface is provided for displaying selectable software functionality controls of a database application. When a task-based functionality tab is selected from the user interface, selectable functionality controls provided by the associated database application for performing aspects of a task related to the selected tab are presented in a ribbon-shaped user interface above a workspace in which a user is entering or editing data. Upon selection of a different task-based functionality tab, the presentation of functionality controls associated with the first task is removed, and selectable functionality controls associated with the second selected task-based functionality tab are presented in the user interface. The selectable functionality controls presented in the user interface are grouped into logical groupings for more efficient utilization.

Abstract: User interface elements are configured for touch input and hardware based input. When using touch input, the user interface (UI) elements are optimized for touch input. For example, UI elements may be displayed: using formatting configured for touch input (e.g. changing a size, spacing); using a layout configured for touch input; displaying more/fewer options; changing/removing hover actions, and the like. When using hardware based input, the user interface elements are optimized for the hardware based input. For example, formatting configured for hardware based input may be used (e.g. hover based input may be used, text may be displayed smaller), more/fewer options displayed, and the like.

Abstract: When a user uses touch to interact with an application, a contextual touch user interface (UI) element may be displayed that includes a display of commands that are arranged in sections on a tool panel that appears to float over an area of the display. The sections include a C/C/P/D section, an object specific section and may include a contextual trigger/section and an additional UI trigger. The C/C/P/D section may comprise one or more of: cut, copy, paste and delete commands. The object specific section displays commands relating to a current user interaction with an application. The contextual trigger/section displays contextual commands and the alternative trigger section displays another UI element comprising more commands when triggered.

Abstract: A touch input mode may be entered and exited automatically and/or manually. When the touch input mode is entered, user interface (UI) elements are optimized for touch input. When the touch input mode is exited, the user interface (UI) elements are optimized for hardware based input. A user may enter the touch input mode by manually selecting a user interface element and/or by entering touch input. Settings may be configured that specify conditions upon which the touch input mode is entered/exited. For example, the touch input mode may be configured to be automatically entered upon undocking a computing device, receiving touch input when in the hardware based input mode, and the like. Similarly, the touch input mode may be configured to be automatically exited upon docking a computing device, receiving hardware based input when in the touch input mode, and the like.