Sap Ag

Uwe Reeder

Markus Cherdron

Stephan Ritter

Frank Weigel

Jens C Ittel

Johannes Lauterbach

Timo Lakner

Methods, systems and computer program products implementing techniques for using interrelated data at run time. The techniques include establishing a model, the model implementing application logic of an application; establishing at least one view for presenting the model; establishing at least one controller for manipulating the model; and establishing at least one storage area, the storage area relating to the controller and storing an instance of a first data structure, the instance of the first data structure comprising application data having been stored in the storage area by an access method, the first data structure having been declared prior to execution of the application.

Using interrelated data at run time

Methods, apparatus, and computer program products that implement techniques for extending the MVC design pattern by structuring data of an application into application contexts. The techniques feature accessing a predetermined structure for a storage area, modifying the predetermined structure and creating an instance of the storage area according to the predetermined structure. The storage area relates to a controller. The controller is operable to manipulate a model and a view. The view includes multiple UI elements for presenting data from the model. The predetermined structure includes multiple design-time context elements and relationships between the design time-context elements. At least one of the UI elements is bound to one of the design-time context elements. The instance of the storage area includes multiple run-time context elements. Each run-time context element corresponds to one of the design-time context elements.

Dynamic contexts

Methods and apparatus, including computer program products, for storing and using customization data. A repository contains one or more repository objects, one or more variants for each repository object, and one or more layers for each variant. Each repository object has one or more model entities. The variants for each repository object are arranged in a first hierarchy, and the layers for each variant are arranged in a second hierarchy. Each layer includes a set of customization values, each customization value corresponding to one of the model entities. Customization values can be (but need not be) provided for each model entity in each layer and in each variant. The variants and layers can be arranged in order of specificity. A customization value for a model entity can be retrieved by locating the most specific variant and the most specific layer that contains a customization value for the model entity.

Customizing application programs

Methods and apparatus, including computer program products, for developing and executing applications include using an extended version of the model-view-controller (MVC) paradigm. The techniques include a model for an application, the model including multiple model elements, at least one view for presenting data from the model, the view including multiple user interface (UI) elements, and at least one controller for manipulating the model and the view. The techniques also can include a structure for storing application data according to a predetermined structure for at least one storage area relating to the controller. The predetermined structure can include multiple context elements and directed relationships connecting the context elements, the directed relationships forming at least one cycle between the context elements. The techniques further can include and at least one binding between one of the UI elements and one of the context elements.

Creating and using nested context structures

Methods and apparatus, including computer program products, for implementing a computer system that provides a model, a first view and at least a second view for presenting the model, a first controller and at least a second controller for manipulating the model. The first and second views relate to the first and second controllers, respectively. The computer system further comprises at least a first context, a second context and a third context. A user interface element of the first view binds to a first structure element of the first context and a user interface element of the second view binds to a second structure element of the second context. The first structure element and the second structure element reference a third structure element of the third context.

Using relationships between contexts in model view controller design pattern

Methods and apparatus, including computer program products, implementing techniques for declaring application data. The techniques include establishing a model, the model implementing application logic of an application; establishing at least one view for presenting the model; establishing at least one controller for manipulating the model; establishing at least one storage area, the storage area relating to the controller; and establishing at least one access method for storing and accessing application data in the storage area according to a predetermined structure.

Growing community of inventors

Riegelsberg, Germany

Uwe Reeder