Generation of an Application from Template

• US 20170131974A1
• Filed: 11/09/2015
• Published: 05/11/2017
• Est. Priority Date: 11/09/2015
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Colle, Olivier, Staples, William James, Balasubramanian, Barath, Cohen, Evan Bjorn-Thomas
• Granted Patent: US 9,891,890 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 3/0482 Interaction with lists of selectable items, e.g. menus
• CPC Class Codes: G06F 3/04842 Selection of displayed objects or displayed text elements G06F3/0482 takes precedence
• CPC Class Codes: G06F 8/20 Software design
• CPC Class Codes: G06F 8/30 Creation or generation of source code
• CPC Class Codes: G06F 8/34 Graphical or visual programming
• CPC Class Codes: G06F 9/5072 Grid computing

Abstract

Examples of the disclosure provide for receiving a template at a design surface, the template representing a visual layout, logic, and data schema for an application. Received source data is bound to the template based on the data schema. At least one data storage location is selected from identified data storage locations. Based on the selection of the one data storage location, at least a portion of the source data is extracted and sent to the data storage location for storage. The extracted data is rewired to bind the extracted data at the data storage location to the template such that access of the application generated using the template provides access to the extracted data at the data storage location.

Claims

1. A method for generating an application, the method comprising:

receiving a selection of a template at a design surface implemented on a user interface, the template including a data schema;

receiving a set of data for the template;

binding the set of data to the template based on the data schema;

identifying at least a portion of the set of data for extraction;

inferring a location for the identified portion of the set of data;

extracting the identified portion of the set of data;

storing the extracted data at the inferred location; and

binding the extracted data at the inferred location to the template, such that access to the template provides access to the extracted data at the inferred location.

2. The method of claim 1, wherein identifying the portion of the set of data for extraction further comprises:

identifying one or more data types of the set of data, the one or more data types including at least one of local data, dynamic data, or remote data.

3. The method of claim 1, wherein the portion of the set of data for extraction is identified based at least in part on a set of policies.

4. The method of claim 1, wherein the portion of the set of data for extraction is identified based at least in part on telemetry data.

5. The method of claim 1, wherein receiving the location for the identified portion of the set of data further comprises:

receiving a first location for a first subset of the portion of the set of data;

receiving a second location for a second subset of the portion of the set of data; and

storing the first subset at the first location and the second subset at the second location.

6. The method of claim 1, wherein identifying the portion of the set of data for extraction further comprises:

identifying one or more locations for data storage;

providing the one or more locations as a connections list; and

receiving the selection of the location from the one or more locations of the connections list.

7. The method of claim 6, wherein providing the one or more locations as the connections list further comprises:

identifying a default location from the one or more locations, the default location identified based at least in part on a set of policies; and

providing the default location as a suggested location in the connections list.

8. A system for generating an application, the system comprising:

a design surface implemented on a processor, the design surface receiving a template and source data;

a data binding mechanism, coupled to the design surface, that binds the source data to the template based on a schema and a set of policies;

a data storage location mechanism, coupled to the design surface, that identifies one or more data storage locations; and

a data extraction mechanism, coupled to the design surface, that identifies at least a portion of the source data to extract from the template, infers at least one data storage location of the identified one or more data storage locations for storage of the extracted portion of the source data, and sends the extracted portion of the source data to the at least one inferred data storage location for storage based at least in part on the set of policies, the data binding mechanism re-binding the extracted portion of the source data stored at the at least one inferred data storage location to the template.

9. The system of claim 8, wherein the data storage location mechanism provides a connections list to the design surface.

10. The system of claim 9, wherein the data storage location mechanism identifies a default storage location from the one or more identified data storage locations and provides the default storage location as a suggested storage location in the connections list.

11. The system of claim 8, wherein the design surface is coupled to a template library, the template library having a number of templates, an individual template of the number of templates comprising a document and a schema.

12. The system of claim 8, wherein the source data comprises at least one of local data, dynamic data, and remote data.

13. The system of claim 12, wherein the data extraction mechanism identifies the local data and maintains storage of the local data at the template.

14. The system of claim 12, wherein the data extraction mechanism identifies the remote data as a subset of the source data that is stored at a remote location and maintains the storage of the remote data at the remote location.

15. The system of claim 12, wherein the data extraction mechanism identifies the dynamic data as a subset of the source data that is to be stored at another data storage location, and extracts the dynamic data to send to the other data storage location.

16. One or more computer storage devices having computer-executable instructions stored thereon for generating an application, which, on execution by a computer, cause the computer to perform operations comprising:

a design surface for receiving a template and source data;

a data binding mechanism for binding the source data to the template based on a schema and a set of policies;

a data storage location mechanism for identifying one or more data storage locations based at least in part on user credentials; and

a data extraction mechanism for identifying at least a portion of the source data to extract from the template, inferring at least one data storage location of the identified one or more data storage locations for storage of the extracted portion of the source data, and sending the extracted portion of the source data to the at least one inferred data storage location for storage based at least in part on the set of policies, the data binding mechanism re-binding the extracted portion of the source data stored at the at least one inferred data storage location to the template.

17. The one or more computer storage devices of claim 16, wherein the data extraction mechanism identifies one or more data types of the source data, the one or more data types including at least one of local data, dynamic data, or remote data.

18. The one or more computer storage devices of claim 16, wherein the portion of the source data for extraction is identified based at least in part on the set of policies.

19. The one or more computer storage devices of claim 16, wherein the data storage location mechanism provides the one or more identified storage locations as a connections list to the design surface.

20. The one or more computer storage devices of claim 19, wherein the design surface receives the at least one identified location for storage of the extracted portion of the source data as a user selection from the connections list.