Event-driven Programming can be Simple Enough for CS

ACM SIGCSE Bulletin, 2001

We have recently designed a CS 1 course that integrates event-driven programming from the very start. Our experience teaching this course runs counter to the prevailing sense that these techniques would add complexity to the content of CS 1. Instead, we found that they were simple to present and that they also simplified the presentation of other material in the course. In this paper, we explain the approach we used to introduce event-driven methods and discuss the factors underlying our success.

2004

Abstract We have designed a CS 1 course that integrates event-driven programming from the very start. In cite BDMITiCSE1 we argued that event-driven programming is simple enough for CS 1 when introduced with the aid of a library that we have developed. In this paper we argue that early use of event-driven programming makes many of the standard topics of CS 1 much easier for students to learn by breaking them into smaller, more understandable concepts.

2012

The present paper consists of a didactic model and methodology of teaching for the organization and carrying out of specialized training in Informatics on high school level in secondary schools teaching the module "Event-driven programming in graphical user interface environment (IDE)". Step- by-step methodological tools for teaching the Informatics curriculum have been developed considering the module.

Proceedings of the 2nd ACM SIGPLAN international …, 2000

Events play an important role in the construction of most software that involves interaction or simulation. Typically, programmers make use of a fixed set of low level events supplied by a window system, possibly augmented with timers and UI components. Event handling generally involves some interpretation of these event occurrences, followed by external actions or modifications to program state.

2006

The real world works according to events. People make unique choices according to the conditions they are put in. In this pap er, an event driven approach is talked about and the impacts it has had on various fields with its evolution. Three of which have been discussed in the paper. At the lower level, basic sequences are coded in elementary software objects called function blocks which prove their functionality when called or used. At the upper level, the execution of such blocks is carried out according to the desired sequences forced by a controller. The interaction of the user with the computer used to be limited to the sequential file, this all changed with the arrival of event driven programs the user can now engage the computer while it is running ot her tasks.

This paper discusses several possibilities of implementing the behavior of an object-oriented application. It assesses the use of the callback or inverse-control programming paradigm, and opposes it to a direct programming style. It presents two examples of the common approach, namely a Motif program using the main event loop, and a Java program using active objects. It then proposes a new approach, based on a limited extension to C++, that is close to Java, but that avoids some limitations of its synchronization means, discussed in the text.

2014

The understanding of the context in which the software applications are developed is highly influenced by events. In fact, any organizational process is intended to be triggered by an event and sometimes is related to certain eventual-type results. Managing and modeling events is one of the most important tasks of the analyst during the software development process, since the behavior of the future software application is revealed by the event interaction. In the traditional way of teaching software engineering, events are commonly taught by means of lectures and “toy” practical projects. However, events are commonly misunderstood in this way of teaching, since they are often mistaken for operations. Also, the way in which an event interacts with each other is not completely understood by the students. Games are student-centered strategies for teaching software engineering concepts. Following a similar strategy to other software engineering games, we propose in this paper the ev...

Proceedings of the 10th workshop on ACM SIGOPS European workshop: beyond the PC - EW10, 2002

Events are a better means of managing I/O concurrency in server software than threads: events help avoid bugs caused by the unnecessary CPU concurrency introduced by threads. Event-based programs also tend to have more stable performance under heavy load than threaded programs. We argue that our libasync non-blocking I/O library makes event-based programming convenient and evaluate extensions to the library that allow event-based programs to take advantage of multi-processors. We conclude that events provide all the benefits of threads, with substantially less complexity; the result is more robust software.

1996

Event-based software architectures are commonly used to solve a variety of problems. These architectures are complex to design and implement, however, especially with conventional, textual programming languages. We describe our recent work in developing visual languages and support environments for the design and implementation of a range of event-based software architectures. A synthesis of this work to produce a more general architecture description language and support environment is described.

2004