Abstract: Deferred formula computation executes software containing a set of programmed formulas, wherein the set includes a first programmed formula defined in an associated dependency graph to be dependent on a result of a second programmed formula. A method may encounter a reference to the first programmed formula during execution of the software, wherein the reference is associated with deferred formula computation request program code in the executing software to obtain a result of the first programmed formula; identify during execution of the software the second programmed formula based on traversal within the associated dependency graph of the first programmed formula; compute a result of the second programmed formula during execution of the software; compute the result of the first programmed formula during execution of the software, and return the computed result of the first programmed formula in association with the reference to the first programmed formula.

Abstract: Examples of the disclosure provide for receiving a data set at a design surface from a data source, and inferring a first data type from the data set. A first control type is generated for the inferred first data type. A second data type is inferred from the data set and a second control type is generated for the inferred second data type, with the first control type and the second control type being different. A layout is generated for an application document that includes the first control type and the second control type.

Abstract: According to examples, an apparatus may include at least one processor and a memory on which is stored machine readable instructions that are to cause the at least one processor to receive a first database object in a declarative application, determine an entity-relationship graph with a neighbor within n-degrees of separation from the first database object in a database, receive a selection of a second database object based on the entity-relationship graph, and generate a query including the first database object and the second database object. The instructions may also cause the processor to determine an expected type for the database value that matches the query.

Abstract: In-application customization is provided where users can both use and customize the application. Within a graphical user interface of an application developed by an original author, an interaction from a customizer user of the application can be received to make a modification to the application from a set of available modifications that the original author did not create for the application. The modification can be performed using functionality made available through a developer program service.

Abstract: Examples of the disclosure provide for receiving a data set at a design surface from a data source, and inferring a first data type from the data set. A first control type is generated for the inferred first data type. A second data type is inferred from the data set and a second control type is generated for the inferred second data type, with the first control type and the second control type being different. A layout is generated for an application document that includes the first control type and the second control type.

Abstract: Displaying data of a particular data type. A set of data to visualize is identified. Once the set of data is identified, a general type of data associated with the identified set of data is determined. Then based at least upon the determined general type of data, a specific type of data associated with the set of data is determined. Determining the specific type of data also comprises identifying a plurality of visualizations associated with the specific type of data. A visualization from the plurality of visualizations is then selected to thereby present the set of data.

Abstract: Examples of the disclosure provide for receiving a data set at a design surface from a data source, and inferring a first data type from the data set. A first control type is generated for the inferred first data type. A second data type is inferred from the data set and a second control type is generated for the inferred second data type, with the first control type and the second control type being different. A layout is generated for an application document that includes the first control type and the second control type.

Abstract: Examples of the disclosure provide for receiving a data set at a design surface from a data source, and inferring a first data type from the data set. A first control type is generated for the inferred first data type. A second data type is inferred from the data set and a second control type is generated for the inferred second data type, with the first control type and the second control type being different. A layout is generated for an application document that includes the first control type and the second control type.

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: In-application customization is provided where users can both use and customize the application. Within a graphical user interface of an application developed by an original author, an interaction from a customizer user of the application can be received to make a modification to the application from a set of available modifications that the original author did not create for the application. The modification can be performed using functionality made available through a developer program service.

Abstract: An application module generates a query that may involve retrieving data from a local data storage source or from an external data storage source. The application module retrieves metadata to form a query tree stored in the local data storage source and uses the query tree to ascertain one or more sub-queries necessary to complete the query and whether the necessary data for each sub-query is stored locally or externally. Based on the location of the data to complete a sub-query, the application module uses the services of an internal query processing layer if external data is involved for the sub-query. The application module uses the services of a query processing layer in the local data storage source if the data is local. Once all the sub-queries associated with the query tree are performed, then the overall query results are returned to the application module.

Abstract: Techniques for programming using a model based spreadsheet scripting language are disclosed herein, where procedural aspects may be incorporated along with the model based aspects therein. In particular, techniques for performing calculations of a value, and recalculation of interdependent formulas using programs written with the model based spreadsheet scripting language are disclosed.

Abstract: An application module generates a query that may involve retrieving data from a local data storage source or from an external data storage source. The application module retrieves metadata to form a query tree stored in the local data storage source and uses the query tree to ascertain one or more sub-queries necessary to complete the query and whether the necessary data for each sub-query is stored locally or externally. Based on the location of the data to complete a sub-query, the application module uses the services of an internal query processing layer if external data is involved for the sub-query. The application module uses the services of a query processing layer in the local data storage source if the data is local. Once all the sub-queries associated with the query tree are performed, then the overall query results are returned to the application module.

Abstract: Technologies are presented herein for self-describing re-usable software components. Metadata is generated and published with a re-usable software component that identifies the capabilities of the software component, identifies other software components that the re-usable software component may be integrated with, and identifies mechanisms for integrating the re-usable software component with other software components. The metadata can then be used to discover re-usable software components and to integrate the re-usable software components with other software components.

Abstract: An environment for developing clientside/serverside code is disclosed. The environment supports programming in an event-driven paradigm while the execution of the resultant programs are executed in a serial execution paradigm. Through shielding the developer from complex scripting segments, the environment provides the developer with the suggestion that that resultant execution model is event-driven.

Abstract: An environment for developing clientside/serverside code is disclosed. The environment supports the perception that the server space and client space are seamlessly joined into a single program execution space. An outgrowth of the single execution space includes effective event handling on the server through enabling created objects to migrate effectively between the server and client.

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: Technologies are presented herein for self-describing re-usable software components. Metadata is generated and published with a re-usable software component that identifies the capabilities of the software component, identifies other software components that the re-usable software component may be integrated with, and identifies mechanisms for integrating the re-usable software component with other software components. The metadata can then be used to discover re-usable software components and to integrate the re-usable software components with other software components.

Abstract: An environment for developing clientside/serverside code is disclosed. The environment supports programming in an event-driven paradigm while the execution of the resultant programs are executed in a serial execution paradigm. Through shielding the developer from complex scripting segments, the environment provides the developer with the suggestion that that resultant execution model is event-driven. By treating scripts as later-definable objects, the designing phase of a page may be lessened, as the appropriate codings needed to implement a page are determined at a later date. In one example, the codings may be preliminary set as server side or client side, with the environment later adding the appropriate scripting language to complete the developed page.

Abstract: Techniques for programming using a model based spreadsheet scripting language are disclosed herein, where procedural aspects may be incorporated along with the model based aspects therein. In particular, techniques for performing calculations of a value, and recalculation of interdependent formulas using programs written with the model based spreadsheet scripting language are disclosed.