Event-Based Programming
Events are by no means a new idea in the software world. They’ve been around at least since the early 1980s. Smalltalk’s Model View Controller paradigm is one of the earliest to use event notifications to keep different parts of a system synchronized with each other. Later graphical user interface...
Đã lưu trong:
| Tác giả chính: | |
|---|---|
| Định dạng: | Sách |
| Ngôn ngữ: | English |
| Được phát hành: |
Apress
2012
|
| Những chủ đề: | |
| Truy cập trực tuyến: | http://scholar.dlu.edu.vn/thuvienso/handle/DLU123456789/31015 |
| Các nhãn: |
Thêm thẻ
Không có thẻ, Là người đầu tiên thẻ bản ghi này!
|
| Thư viện lưu trữ: | Thư viện Trường Đại học Đà Lạt |
|---|
| Tóm tắt: | Events are by no means a new idea in the software world. They’ve been around at least since the
early 1980s. Smalltalk’s Model View Controller paradigm is one of the earliest to use event notifications
to keep different parts of a system synchronized with each other. Later graphical user interface
(GUI) operating systems, such as Microsoft Windows, are based on an event-driven model, in which
applications run passively instead of using their own code to scan the input devices for activity. The
operating system uses an event mechanism to notify applications of operator input or other occurrences.
Publish-subscribe systems have since become popular, allowing subscribers to sign up to a
notification service and get information back using a push interaction style. Events really started to
go mainstream at the programming language level with the release of Microsoft Visual Basic in the
early 1990s. The programming paradigm was based on a window called a form, on which programmers
could place UI widgets selected from a toolbox. Programmers could customize the widgets by
wiring their events to handlers in the parent form. Borland Delphi, released in early 1995, incorporated
the event idea and also added events as new types to Object Pascal, the native Delphi programming
language.t |
|---|