English (United Kingdom)

https://curated-unify.zendy.io/wp-json/zendy-region/v1/featured_content/oa?rat=en

https://curated-unify.zendy.io/wp-json/zendy-region/v1/highlighted_journal/

Global: Zendy Plus annual

Presents the access of premium content as premium feature

Premium Content

Presents the keyphrase highlighting as premium feature

Keyphrase Highlighting

Presents the summarisation as premium feature

Summarisation

Insights

Presents the pdf analysis as premium feature

PDF Analysis

Presents the zaia usage as premium feature

ZAIA

Global: Zendy Tools annual

Global: Zendy Free Plan

Global: Zendy Tools monthly

Global: Zendy Plus monthly

This book attempts to tackle the difficult task of creating programs in the Microsoft Windows environment that execute quickly while minimizing memory usage. The author states that poor performance is not inherent in Windows, but is a result of the way programmers write their Windows programs. Instead of haphazardly slapping code fragments together, Krell presents an overall program architecture and design methodology based on software engineering principles. The architecture is designed to overcome the difficulties of task scheduling in a non-preemptive multitasking environment. The design methodology focuses on complete specification of the user inputs and message traffic within the program. The author provides a working example to illustrate the application of his ideas and develops a number of software "templates" to ease system construction. The architecture Krell presents is a reflection of the non-preemptive nature of the Windows tasking system. Windows relies on the cooperation its programs to moderate CPU usage, and lacks protocols for efficient task synchronization. The author's architecture overcomes these deficiencies by dividing an application into schedulable code segments and using a software task scheduler to direct execution of the code segments. There are four parts to the architecture: a master controller task, a scheduler task, the application tasks and a global shared memory manager. The master controller provides an entry point for user inputs and functions as a centralized control for the other tasks. The scheduler maintains a detailed task schedule and uses a timer to schedule the application code segments for execution. The application proper is composed of a set of tasks, each of which is divided into equitable, schedulable code segments. Finally, a global shared memory structure is maintained to allow data transmission between tasks. The design methodology is made up of four major steps which tailor the architecture to the specific problem at hand. The first Step is to create an application model by describing the application's behavior in terms of activities and software tasks that will perform these activities. The specific tasks and global memory structures are defined. Next, an operational model is fabricated that describes the message flow generated by the user interface, system resources and other tasks. The third step, a requirements model, defines the functions that will process the message traffic. A process specification must be made for each function and a data dictionary is used to summarize the message components and variable definitions. Up to this point, all …

Book Review: High-Speed Windows Applications: Multitasking Design Methods by Bruce E. Krell