Abstract: Embodiments described herein are directed to providing enhanced database editing and reporting capabilities. In one scenario, a computer system receives a data item request that identifies which data items are to be reported. The computer system accesses a relational data store to determine which information sets are to be used for reporting the requested data items. Based on the determination, the computer system accesses those information sets that are to be used in the reporting the requested data items. The computer system then determines that metadata has been provided for at least one of the accessed information sets. The metadata includes instructions at least partially indicating how the data items are to be reported. The computer system also reports the data items according to the instructions in the provided metadata, regardless of how the data items are to be reported using the existing information sets.

Abstract: A two-dimensional canvas onto which heterogenic objects of various types may be arranged side-by-side. Each type of object has an associated set of control(s), the control(s) at least partially differing from one type to the next. The two-dimensional canvas is fixed in one dimension, but extensible in a second dimension. The canvas may be displayed in miniaturized for with a view box superimposed upon the canvas. As the view box is moved over the miniaturized canvas, the enlarged editable portion of the corresponding canvas is displayed in an edit view. The canvas may also display clusters of objects that are arranged in dashboards. In that case, the display might include a dashboard review area that allows a user to select the appropriate dashboard to display.

Abstract: A two-dimensional canvas onto which heterogenic objects of various types may be arranged side-by-side. Each type of object has an associated set of control(s), the control(s) at least partially differing from one type to the next. The two-dimensional canvas is fixed in one dimension, but extensible in a second dimension. The canvas may be displayed in miniaturized for with a view box superimposed upon the canvas. As the view box is moved over the miniaturized canvas, the enlarged editable portion of the corresponding canvas is displayed in an edit view. The canvas may also display clusters of objects that are arranged in dashboards. In that case, the display might include a dashboard review area that allows a user to select the appropriate dashboard to display.

Abstract: A two-dimensional canvas onto which heterogenic objects of various types may be arranged side-by-side. Each type of object has an associated set of control(s), the control(s) at least partially differing from one type to the next. The two-dimensional canvas is fixed in one dimension, but extensible in a second dimension. The canvas may be displayed in miniaturized for with a view box superimposed upon the canvas. As the view box is moved over the miniaturized canvas, the enlarged editable portion of the corresponding canvas is displayed in an edit view. The canvas may also display clusters of objects that are arranged in dashboards. In that case, the display might include a dashboard review area that allows a user to select the appropriate dashboard to display.

Abstract: The subject disclosure relates to annotating data based on gestures. Gestures include user interaction with a client device or client software. Gestures are tracked and associated with data. In an aspect, client context associated with a gesture is also tracked. The gestures are then employed to determine a global term to associate with the data. In an aspect, a look-up table comprising a pre-defined relationship between gestures and a global term can be employed. In another aspect, an inference component employ context information in conjunction with the tracked gestures to determine a global term to assign to data. After a global term is determined for data based on a gesture, an annotation file for the data can be created associating the data with the global term.

Abstract: The subject disclosure relates to one or more computer-implemented processes for collecting, analyzing, and employing annotations of data sources. In particular, an annotation component is configured to receive annotations of data for a data source, wherein the respective annotations comprise different associations of a global terms with the data of the data source, a data store configured to store the annotations, and an interface component configured to render the data based on the annotations in response to a request for the data. In an aspect, storing information, the data also stores descriptions of the data sources and definitions of the global terms, and the interface component determines a subset of the information in the data store based on the annotations. A method is further provided comprising receiving a global term and determining data sources that have the global term associated with the data thereof based on the information in the data store.

Abstract: A method and system for creating and modifying computer applications using an application description language based on a markup language is provided. An engine creates, connects, and initializes objects corresponding to entities, and specified by entity tags. A factory may be specified by an entity tag and used to create a plurality of entities. Applications are specified in a plaintext descriptive language using a markup language such as XML, enabling applications to be easily developed using object oriented techniques and abstraction. Altering preexisting applications is also simplified. Finally, an application may be dynamically reconfigured when the application's data changes. Type checking and conditional creation of entities is supported.

Abstract: Indexing domains of a declarative application with view state information for the domain to enable persisting the view state of the declarative application. The domains are organized in a tree. Each domain is built by a configuration builder. The method includes indexing a domain of a declarative application by indexing a path name in an index. The path name includes a path name of the parent domain of the domain; an identifier of the configuration builder used to build the domain; and an identifier of one or more local decisions made by the configuration builder when creating the domain. The method further includes correlating a unique identifier key to the path name in the index and correlating view state information for the domain to the unique key identifier.

Abstract: In an embodiment, a generic database application of a computer system receives a portion of input data from a database. The generic database application can communicate with the database using a variety of different database schemas. The generic database application of the computer system infers a portion of ORM metadata associated with the received input data. The computer system accesses a generic ORM query where the ORM query is configured to provide mapping information to map the input data into a graph of objects according to the database object properties included in the ORM metadata. The computer system maps the input data into a graph of objects using the database object properties included in the ORM metadata and displays an ORM object view which includes the graph of objects.

Abstract: A two-dimensional canvas onto which heterogenic objects of various types may be arranged side-by-side. Each type of object has an associated set of control(s), the control(s) at least partially differing from one type to the next. The two-dimensional canvas is fixed in one dimension, but extensible in a second dimension. The canvas may be displayed in miniaturized for with a view box superimposed upon the canvas. As the view box is moved over the miniaturized canvas, the enlarged editable portion of the corresponding canvas is displayed in an edit view. The canvas may also display clusters of objects that are arranged in dashboards. In that case, the display might include a dashboard review area that allows a user to select the appropriate dashboard to display.

Abstract: One embodiment is directed to a method that may be practiced in a declarative application with composites organized hierarchically, including composites in the same hierarchy, but not directly related by direct intervening child/parent relationships. The method includes acts for providing a link between composites unrelated by direct intervening child/parent relationships. The method includes rendering data at a user interface. The data is associated with a first composite in a declarative application. The method further includes detecting, at the user interface, user interaction with the rendered data. As a result of detecting user interaction with the rendered data, the method further includes defining a composite path to the first composite. The method further includes providing the name of the path as a local variable to a second composite such that the second composite can interact with the data.

Abstract: Embodiments are directed to dynamically building software applications and dynamically updating software applications based on changed data values. In one embodiment, a computer system receives an indication that a software application is to be initiated. The computer system also receives an application description including tags describing software objects that are to be included in the software application, automatically maps portions of the application description identified by the tags to software objects using reflection, where the reflecting includes accessing properties associated with the software objects, and automatically binds properties of the software objects to the portions of the application description based declarative rules included in the software object properties associated with the software object.

Abstract: A two-dimensional canvas onto which heterogenic objects of various types may be arranged side-by-side. Each type of object has an associated set of control(s), the control(s) at least partially differing from one type to the next. The two-dimensional canvas is fixed in one dimension, but extensible in a second dimension. The canvas may be displayed in miniaturized for with a view box superimposed upon the canvas. As the view box is moved over the miniaturized canvas, the enlarged editable portion of the corresponding canvas is displayed in an edit view. The canvas may also display clusters of objects that are arranged in dashboards. In that case, the display might include a dashboard review area that allows a user to select the appropriate dashboard to display.

Abstract: Data-driven configuration of various views on data models. A framework may be provided that offers one or more parameterized view generation components, each aimed at generating a particular view type in response to configuration data that populates the parameters of the associated component. A user or other computing entity merely provides configuration data to an appropriate view generation component to generate a custom view. That custom view may then optionally perhaps be applied to any number of data models, or perhaps not applied to any data model at all and just saved for perhaps some future use. This view generation may generate composite views on a data model, or even hierarchical views on a data model.

Abstract: Embodiments described herein are directed to generating a customized data viewer, where the viewer is configured to display data at any level in a data model. In one embodiment, a computer system receives a user request indicating that portions of data are to be displayed in a user-customized manner using a data viewer. The computer system accesses the requested data portions that are to be displayed with the data viewer. The computer system generates a dynamic data viewer configured to display the accessed data portions in the user-customized manner indicated in the received user request. The computer system also applies the generated dynamic data viewer to the accessed data portions, such that the generated viewer displays the requested data portions in the user-customized manner.

Abstract: A database integration viewer that allows additional properties to be associated with a record as viewed in a single record or table, even though those additional properties are not owned by the record in the underlying source record or table in the database. Using this integration view, a viewed version of record or table may be different than the actual structure of the source record or table. In the viewed version of the record or table, the viewed record or table or may include some or all of the properties for the records of the subject record or table, while incorporating one or more additional properties for the record into the viewed table. The properties may be scalars, or may be computed to populate the viewed version of the record or table.

Abstract: A framework is implemented. The framework is configured to execute an application within the framework, the application includes instantiated runtime objects. New instantiated runtime objects may be created and instantiated runtime objects destroyed while the application is executing. The framework is further configured to implement a debugger within the framework. At the debugger, instantiated runtime objects are correlated with lines of code of the application. Some embodiments allow users to debug executing applications. This can be accomplished by a user interacting with the executing application which then causes indications in the debugger or interacting with the debugger and which causes indications on instantiated runtime objects in the application.

Abstract: In an embodiment, a computer system defines a generic relational meta-schema (GRMS), where the GRMS describes a generic representation for relational schemas and where the GRMS includes metadata indicating how a relational schema is to be stored as data in the data store. The computer system also defines describes a generic relational data schema (GRDS), where the GRDS describes a generic representation for relational data and where the GRDS includes metadata that indicates how relational data is to be stored in the data store in a generic fashion not necessarily complying with the relational schema for the data. Next, the computer system stores data in the data store according to the generic relational data schema and stores metadata as data in the data store according to the generic relational meta-schema.

Abstract: In an embodiment, a computer system instantiates a real-time incremental editor configured to receive editing inputs that are to be applied to data of a data model, where the data model data declaratively defines a UI model that drives the behavior of a corresponding UI based on the UI model. The computer system receives an editing input from a user indicating one or more desired edits that are to be made to the UI and determines, based on the received editing inputs, which changes are to be made to the data model data to enact the desired changes in the UI. The computer system updates the UI in real-time based on the determined edits to the data model data and presents the updated UI in real-time without losing state information in the resultant UI.

Abstract: Indexing domains of a declarative application with view state information for the domain to enable persisting the view state of the declarative application. The domains are organized in a tree. Each domain is built by a configuration builder. The method includes indexing a domain of a declarative application by indexing a path name in an index. The path name includes a path name of the parent domain of the domain; an identifier of the configuration builder used to build the domain; and an identifier of one or more local decisions made by the configuration builder when creating the domain. The method further includes correlating a unique identifier key to the path name in the index and correlating view state information for the domain to the unique key identifier.