Behavior-first event programming model
AssigneeMicrosoft Corporation
InventorsAdam D. Nathan, Chi Wai Wong
Life of this patent
Estimating the term…
Abstract
Traditional programming environments that support event-driven programming typically expose a model where the developer chooses an event to handle on a given object, and then writes the code for that event handler. In contrast, as described herein, the traditional flow of program development is reversed. A (configurable) event-handler (“behavior”) is selected. Upon selection of one of the behaviors, the event triggering the behavior is selected. This is a “what-then-when” approach rather than the traditional “when-then-what” approach for event-driven programming.
Claims18
A system for exposing a behavior-first event programming model comprising:
- a behavior-first component executed by a processor of a software development computer, the behavior-first component exposing a behavior-first programming model for software development via at least one user interface, wherein a behavior comprising a configurable event-handler is selected before an event is selected for the behavior.
A method for creating an event-driven program comprising:
- receiving a behavior comprising a configurable event-handler based on input received from a user of a behavior-first programming model executed by a processor via at least one user interface;
- in response to receiving the behavior, providing a list of a plurality of events associated with the behavior via the at least user interface;
- receiving an event of the plurality of events on the list to trigger the behavior via the at least one user interface;
- transforming the received behavior and event into an executable program.
A computer-readable storage medium comprising computer-executable instructions which when executed cause a computing environment to:
- receive a behavior comprising a configurable event-handler based on input received from a user of a behavior-first programming model executed by a processor via at least one user interface;
- in response to receiving the behavior, provide a list of a plurality of events associated with the behavior via the at least user interface;
- and
- receive an event of the plurality of events on the list to trigger the behavior via the at least one user interface.
Dependencies are inferred from the claim text.