In contrasting the read-evaluation loop and the notification-based paradigm for inter- active programs, construction of a pre-emptive dialog was discussed. How would a programmer describe a pre-emptive dialog by purely graphical means? (Hint: Refer to the discussion in Sec- tion 8.5 concerning the shift from external and independent dialog management to presentation control of the dialog)

In an illustrations based communication, it is expected that the client can just associate with parts of the framework that are obvious. In a windowing framework, for instance, the client can just direct contribution to a solitary, at present chosen window, and the main methods for changing the chose window would be by demonstrating with some signal inside that window. To make a preemptive exchange, the framework can create a window that covers the whole screen and make it the right now chosen window. All client information would then be coordinated to that window and the client would have no methods for choosing another window. The 'covering' window in this way preempts some other client activity with the exception of that which it is characterized to help

answer:

ask me the quest

explanation: