Abstract: Optimized execution order results (e.g., from a Rete algorithm graph) are correlated with a production ordering selected by a user, thereby more accurately modeling the user's understanding of how productions relate to one another during execution in a rule system. An execution report shows in the user-selected order for each of the rules, whether the rule was executed, the inputs matched to partial conditions of the rule, and partial condition evaluation results. User rule management experience is also enhanced in other ways. For example, a graphical user interface permits user selection of a schema xpath, bulk selection of XML schema nodes to define vocabulary used in rules, if-then-else rules, rules with embedded SQL, marking rules as active or not, receiving multiple kinds of input from a single text input box, locally executing rules, importing rules authored elsewhere, iterating over a collection of objects, and validating rules against vocabulary data types.

Abstract: Optimized execution order results (e.g., from a Rete algorithm graph) are correlated with a production ordering selected by a user, thereby more accurately modeling the user's understanding of how productions relate to one another during execution in a rule system. An execution report shows in the user-selected order for each of the rules, whether the rule was executed, the inputs matched to partial conditions of the rule, and partial condition evaluation results. User rule management experience is also enhanced in other ways. For example, a graphical user interface permits user selection of a schema xpath, bulk selection of XML schema nodes to define vocabulary used in rules, if-then-else rules, rules with embedded SQL, marking rules as active or not, receiving multiple kinds of input from a single text input box, locally executing rules, importing rules authored elsewhere, iterating over a collection of objects, and validating rules against vocabulary data types.

Abstract: A development environment provides warnings based on one or more application categories set for an application. Each warning has a trigger threshold and a warning action. Different application categories have different warnings. The development environment proactively tests for trigger conditions and provides triggered warnings within a workflow that includes application designing, code editing, building, and running. For instance, a Social Networking application whose start-up time is greater than desired for Social Networking applications will trigger a warning. Password Manager or Finance applications that should use a more secure approach to store user data will trigger a warning not given to applications in other categories. A News application may trigger a warning from the development environment that application content is not easily readable if a user switches to a light color theme on a device. The application category is selected by the developer or set proactively by the development environment.

Abstract: A development environment simulates conditions combining device states, events, hardware configurations, and usage scenarios, and applies specific rating criteria to arrive at individual quality parameter ratings. Ratings are provided for quality parameters such as user experience, cost awareness, battery friendliness, responsiveness, global readiness, device independence, application stability. For example, battery friendliness depends on criteria such as battery life in a specified usage scenario, whether unused peripherals are powered, whether application program interfaces designated as power-hungry are avoided, whether darker color themes can be chosen over lighter colors, and whether batching is used for network data communications. Some rating criteria are application-category-specific. For example, security is rated differently for a Finance application than a Music application.

Abstract: A development environment provides warnings based on one or more application categories set for an application. Each warning has a trigger threshold and a warning action. Different application categories have different warnings. The development environment proactively tests for trigger conditions and provides triggered warnings within a workflow that includes application designing, code editing, building, and running. For instance, a Social Networking application whose start-up time is greater than desired for Social Networking applications will trigger a warning. Password Manager or Finance applications that should use a more secure approach to store user data will trigger a warning not given to applications in other categories. A News application may trigger a warning from the development environment that application content is not easily readable if a user switches to a light color theme on a device. The application category is selected by the developer or set proactively by the development environment.

Abstract: Techniques are provided for compiling source code. A first code portion is generated that corresponds to the source code and is included in an application program. An attribute setting is received indicating an execution environment for the application program. A second code portion included in the application program is conditionally generated in accordance with the attribute setting. A determination is made as to whether the attribute setting is a first value indicating a first execution environment. If the attribute setting is the first value, a deployment manifest file and an application manifest filed are generated. The manifest files are used in connection with installation of the application program for execution in the first execution environment.

Abstract: A system and method for validating arguments in a request to activate an application is provided. An application may include declarations with information for validating arguments provided with a request to activate the application. A compiler may then compile the source code of the application to generate an assembly with information for validating the arguments and may also generate an entry in a manifest with information identifying the assembly with the information for validating the arguments. The compiler may also generate an activation executable with executable code used for validating the arguments before the application may be executed. When a request may be received with arguments for activation of the application, activation code may validate the arguments and then execute the application code which may access the validated arguments.