Abstract: A method for optimizing customer scheduling, the method may comprise receiving a request to make an appointment for the customer, scheduling an appointment time for the customer, and recording the appointment time; recording an arrival time for the customer when the customer arrives for their appointment and calculating the amount of time the customer is tardy based on the appointment time; associating the amount of time the customer is tardy with the user account for the customer and saving it in memory as tardiness data; generating an anticipated amount of time the customer will arrive after their appointment time for a next appointment based on the tardiness data; receiving a request to make a second appointment for the customer, and notifying a user of the anticipated amount of time the customer will arrive after their appointment time; and scheduling the second appointment time for the customer and recording the appointment time.

Abstract: A computer can be configured to execute event-driven applications by programming the computer with software that provides an event-driven execution environment including an event dispatcher. The event dispatcher can be used to relay events by receiving and dispatching the events from software components of an event-driven application during execution thereof. While the event-driven application is executing, the event dispatcher can be monitored in order to generate and store a log or other record(s) identifying one or more events that occur during execution. The log can be stored in a computer-readable medium accessible by the computing apparatus and used to provide information about at least some of the one or more events. As an example, the log data may be used to generate a timeline showing the relative order of events and the components that generated and listened to the events.

Abstract: A selective outline view is described in an application development environment that allows viewing an outline of an application in either a procedural code outline view or a declarative tree-view. The application is written, at least in part, in a tag-based declarative language. The declarative language has a representational relationship to a procedural language that defines the logic of application. The choice of views is presented in a selection indicator. On selection of the procedural code outline view, the application is processed to obtain a procedural code representation of the application using the relationship between the declarative and procedural languages. The procedural code outline view is generated from the procedural code representation. On selection of the declarative tree-view of the application, the ADE parses the application to obtain a declarative object model of the application. The declarative tree-view of the application is created using the declarative object model.