Abstract: A mobile computing device for measuring self-awareness of a user includes motion sensors and a processor for displaying instructions on how to conduct a whipping gesture, executing a body awareness assessment including receiving sensor data while the user performs multiple whipping gestures, executing an emotional awareness assessment including receiving sensor data while the user performs multiple whipping gestures, executing a self-assessment including receiving sensor data while the user performs multiple whipping gestures, executing a resiliency awareness assessment including receiving a response from the user to a question and generating a final self-awareness score corresponding to the user's self-awareness based on the body awareness assessment, emotional awareness assessment, self-assessment and resiliency awareness assessment.

Abstract: A mobile computing device for measuring somatic response of a user to stimulus includes motion sensors, a volatile memory, and a processor for: executing a baseline calibration process including receiving first and second supervised data from the user, and first and second sensor data from the motion sensors, while the user performs a triple whip gesture, calculating signal strength of the first and second sensor data using a k-means clustering algorithm, and executing a classification process including reading third unsupervised data from the user and third sensor data from the motion sensors while the user performs the triple whip gesture.

Abstract: A mobile computing device for measuring somatic response of a user to stimulus includes motion sensors, a volatile memory, and a processor for: executing a baseline calibration process including receiving first and second supervised data from the user, and first and second sensor data from the motion sensors, while the user performs a triple whip gesture, calculating signal strength of the first and second sensor data using a k-means clustering algorithm, and executing a classification process including reading third unsupervised data from the user and third sensor data from the motion sensors while the user performs the triple whip gesture.

Abstract: An optical flow of depth video of a depth camera imaging a human subject is recognized. An energy field created by motion of the human subject is generated as a function of the optical flow and specified rules of a physical simulation of the virtual environment. The energy field is mapped to a virtual position in the virtual environment. A property of a virtual object in the virtual environment is adjusted based on a plurality of energy elements of the energy field in response to the virtual object interacting with the virtual position of the energy field.

Abstract: An optical flow of depth video of a depth camera imaging a human subject is recognized. An energy field created by motion of the human subject is generated as a function of the optical flow and specified rules of a physical simulation of the virtual environment. The energy field is mapped to a virtual position in the virtual environment. A property of a virtual object in the virtual environment is adjusted based on a plurality of energy elements of the energy field in response to the virtual object interacting with the virtual position of the energy field.

Abstract: The architecture provides development tools for the occasional developer to build a substantial portion of an application interface for accessing and interacting with actual data. The lack in knowledge of the occasional developer to complete the project is then supplemented by a development service provider such that experienced developers complete the interface and integrate the interface into the application environment so the occasional developer can use the application to access data for which the interface was developed. The architecture provides tools that are understandable for building in a guided way the framework and the user experience for the application, and then passes on the more complex pieces to IT because coding may be needed or a model should be generated that is scalable for a large number of users, for example. IT then completes the development process and integrates the final solution into the application environment.

Abstract: The architecture provides development tools for the occasional developer to build a substantial portion of an application interface for accessing and interacting with actual data. The lack in knowledge of the occasional developer to complete the project is then supplemented by a development service provider such that experienced developers complete the interface and integrate the interface into the application environment so the occasional developer can use the application to access data for which the interface was developed. The architecture provides tools that are understandable for building in a guided way the framework and the user experience for the application, and then passes on the more complex pieces to IT because coding may be needed or a model should be generated that is scalable for a large number of users, for example. IT then completes the development process and integrates the final solution into the application environment.

Abstract: User interfaces are defined by metadata for use with productivity suite applications in a wrapped window, a task pain, or some other suitable representation. Data can be bound to a data source in a one-way format such that changes from the data source propagate to property fields in the UI form. Data can also be bound to a data source in a two-way format such that changes from the property field of the UI propagate back to the data source. The data source can be a local cache such as for synchronization between a productivity suite application and a line of business (LOB) application (e.g., CRM applications). A rendering engine is arranged to process the UI and data bindings such that custom event handlers are defined in a code behind assembly format. Productivity suite items are accessible from the code behind assembly through a series of item interfaces.

Abstract: A synchronization method is arranged to permit synchronization between a productivity suite application and a line of business (LOB) application such as a Customer Relation Management or CRM application. Requests are sent from the productivity suite application to the LOB application via a web service call to update, delete, or create a new entity in the LOB application. The LOB application extracts each request from received web service calls, where the request can be provided in an XML data representation. Requests are communicated to the productivity suite application via control messages that are embedded in an email to update, delete, or create an item in the productivity suite application, where the item is associated with a LOB entity. The control messages are hidden from the user, and extracted from the email message for evaluation, conflict resolution, property promotion and binding between the LOB entity and the productivity suite application item.