Abstract: This disclosure provides various embodiments for providing transparently stateful execution of stateless applications. A request associated with an application is received and includes at least one operation to be executed by the application as well as a set of first state information. The application determines if the operations are to be executed statelessly or not. If the application is to be executed statelessly, the first state information is retrieved from the request and used to initialize the application. If not, then the first state of the application is retrieved from a location other than the received request. The operations are then executed by the application in the application's appropriate first state. A response including the relevant information associated with the response as well as an updated set of state information identifying the application's second state is generated and transmitted to the client.

Abstract: A system and method for transmitting data using a data transfer protocol, including receiving, at the first device, a request object from the second device, receiving, at the first device, a response object in response to the request object, transforming the response object by appending a one or more logical expressions for controlling at least one user-interface component of an application hosted at the second device, varying the format of the response object to generate a transformed response object, and sending the transformed response object to the second device.

Abstract: A system and method for transmitting data using a data transfer protocol, including receiving, at the first device, a request object from the second device, receiving, at the first device, a response object in response to the request object, transforming the response object by appending a one or more logical expressions for controlling at least one user-interface component of an application hosted at the second device, varying the format of the response object to generate a transformed response object, and sending the transformed response object to the second device.

Abstract: The present disclosure involves systems, software, and computer implemented methods for modification free UI cutting of components in an application. One process includes operations for identifying a selection of a particular portion of the user interface of the application for cutting. The position of the identified portion of the user interface of the application in a user interface control tree is determined and defined as a root node of the user interface control tree. The identification information of the root node is stored in personalization settings of the application, and user interface elements associated with the root node are rendered.

Abstract: A method is provided for creating and/or utilizing a computer software application. The method may include structuring the application into a first software layer and a second software layer and defining a plurality of data elements used by the application. The method may also include establishing the first software layer based on the data elements for processing the data elements and creating the second software layer including adaptation data to present the plurality of data elements modified by the adaptation data associated with the data elements. Further, the adaptation data may enable plural presentations of the data elements by the second software layer independently from the first software layer.

Abstract: The present disclosure involves systems, software, and computer implemented methods for modification free UI cutting of components in an application. One process includes operations for identifying a selection of a particular portion of the user interface of the application for cutting. The position of the identified portion of the user interface of the application in a user interface control tree is determined and defined as a root node of the user interface control tree. The identification information of the root node is stored in personalization settings of the application, and user interface elements associated with the root node are rendered.

Abstract: The present disclosure involves systems, software, and computer implemented methods for modification free tagging of business application user interfaces. One process includes operations for receiving a selection of a particular user interface element for tagging. If at least one bound data object is associated with the selected user interface element, tagging data for the bound data object is received. The tagging data is stored in the personalization settings of the application, and a listener function associated with the bound data object is defined.

Abstract: The present disclosure involves systems, software, and computer implemented methods for modification free UI injection of a mashup component into a business application. One process includes operations for receiving a selection of a portion of a user interface to be used for injection of a mashup component. A user interface container is generated at the selected portion, and the selected portion and parameters associated with the mashup component are stored in the personalization settings of the application. The process includes executing the mashup component within the user interface container.

Abstract: This disclosure provides various embodiments for providing transparently stateful execution of stateless applications. A request associated with an application is received and includes at least one operation to be executed by the application as well as a set of first state information. The application determines if the operations are to be executed statelessly or not. If the application is to be executed statelessly, the first state information is retrieved from the request and used to initialize the application. If not, then the first state of the application is retrieved from a location other than the received request. The operations are then executed by the application in the application's appropriate first state. A response including the relevant information associated with the response as well as an updated set of state information identifying the application's second state is generated and transmitted to the client.

Abstract: Methods and apparatus, including computer program products, implement techniques for navigating user interface elements of a computer program application. A navigation key press of a navigation key is detected, where the navigation key has a group identifier. A selected group of user interface elements associated with the group identifier is identified. Input focus is shifted to a user interface element in the selected group based on the navigation key.

Abstract: Methods and apparatus, including computer program products, for navigating user interface elements of a computer program application. In one aspect, a method includes grouping user interface elements of an application into groups based on a hierarchical arrangement of the elements, detecting a navigation key press of a sibling or a parent navigation key, and if it is a sibling navigation key, shifting input focus to a next sibling group in the hierarchy, and if it is a parent navigation key, shifting input focus to a parent group in the hierarchy. In another aspect, a method for navigating editable cells of a table includes detecting a forward or a backward navigation key; if it is a forward navigation key, shifting input focus to a next editable cell of the table; and if it is a backward navigation key, shifting input focus to a previous editable cell of the table.

Abstract: Methods, computer systems and apparatus, including computer program products, for handling events in an event-driven software application. An event request specifying an event and values for one or more event parameters is received in a system event handler. The system event handler identifies an action associated with the specified event. The action specifies a required set of parameters and an event handling function specifying one or more operations that can be performed on data. The system event handler generates an instance of the identified action by mapping the event parameter values to the required set of parameters. The event handling function is called in an application event handler with the generated instance of the identified action to invoke application code.

Abstract: A method is provided for creating and/or utilizing a computer software application. The method may include structuring the application into a first software layer and a second software layer and defining a plurality of data elements used by the application. The method may also include establishing the first software layer based on the data elements for processing the data elements and creating the second software layer including adaptation data to present the plurality of data elements modified by the adaptation data associated with the data elements. Further, the adaptation data may enable plural presentations of the data elements by the second software layer independently from the first software layer.

Abstract: Methods and apparatus, including computer program products, for rendering objects. According to one aspect, a program has instructions to receive at run time, in a render manager, a request for rendering a first object and an output destination for rendering the first object, which is an object in a graph of objects; instructions to select a first renderer appropriate to the object and the output destination; and instructions to invoke the selected first renderer to render the first object. Advantageous implementations include instructions in the selected first renderer to call back the render manager when the selected first renderer encounters a second object to be rendered in rendering the first object, where the second object cannot be rendered by the selected renderer; and instructions in the render manager to select and use a second renderer to render the second object.

Abstract: Methods and apparatus, including computer program products, for navigating user interface elements of a computer program application. In one aspect, a method includes grouping user interface elements of an application into groups based on a hierarchical arrangement of the elements, detecting a navigation key press of a sibling or a parent navigation key, and if it is a sibling navigation key, shifting input focus to a next sibling group in the hierarchy, and if it is a parent navigation key, shifting input focus to a parent group in the hierarchy. In another aspect, a method for navigating editable cells of a table includes detecting a forward or a backward navigation key; if it is a forward navigation key, shifting input focus to a next editable cell of the table; and if it is a backward navigation key, shifting input focus to a previous editable cell of the table.

Abstract: Methods, computer systems and apparatus, including computer program products, for handling events in an event-driven software application. An event request specifying an event and values for one or more event parameters is received in a system event handler. The system event handler identifies an action associated with the specified event. The action specifies a required set of parameters and an event handling function specifying one or more operations that can be performed on data. The system event handler generates an instance of the identified action by mapping the event parameter values to the required set of parameters. The event handling function is called in an application event handler with the generated instance of the identified action to invoke application code.

Abstract: Methods and apparatus, including computer program products, for rendering objects. According to one aspect, a program has instructions to receive at run time, in a render manager, a request for rendering a first object and an output destination for rendering the first object, which is an object in a graph of objects; instructions to select a first renderer appropriate to the object and the output destination; and instructions to invoke the selected first renderer to render the first object. Advantageous implementations include instructions in the selected first renderer to call back the render manager when the selected first renderer encounters a second object to be rendered in rendering the first object, where the second object cannot be rendered by the selected renderer; and instructions in the render manager to select and use a second renderer to render the second object.