Each of the popular GUI environments draws on the strengths of its base operating system, and, in some cases, builds on it.
Windows3.
x: Two of the strengths of Microsoft's Windows operating environment and its Dynamic Data Exchange protocol, which supports hot links between programs.
Windows uses two memory pools.
The local pool is specific to the applications.
The global pool can be accessed by any program in the system.
Local memory is faster and more efficient but limited to chunks of 64-Kb, a DOS limitation.
Windows 3.
x relies on DOS as its base operating system and inherits some of its limitations, such as the 64-Kb segments.
Applications that require a great deal of systems resources (in Windows terms), such as text-intensive or data-entry applications, are limited to storing these system resources in 64-Kb areas.
The amount of physical memory on the machine has no bearing on this limitation.
Companies that have designed systems to overcome this technical obstacle admit that it is doable but not easy.
Dynamic Link Libraries: Dynamic link libraries allow coded routines to be modularized and improve the execution performance and maintainability of an application.
Code can be packaged according to functionality and performance considerations.
However, poor packaging decisions will result in poor performance.
A change in any module requires re-linking the libraries of which it was a part.
Dynamic link libraries can be loaded with the application or as needed.
Both Windows and OS/2 Presentation Manager support Dynamic link libraries.
Dynamic Data Exchange: Dynamic Data Exchange provides automatic information exchange between applications.
These data exchange can be used to link a group of cells between two programs, such as Microsoft's Excel and Word for Windows.
If part of the spreadsheet or a graph of the spreadsheet data is loaded into a document and the spreadsheet numbers change, the corresponding area of the document is automatically updated.
304 The Windows 3.
1 alternatives to Dynamic Data Exchange that Microsoft is promoting are OLE and Dynamic Data Exchange Management Library.
It is a Dynamic link library that provides a higher-level interface than the bare bones data exchange specification.
Instead of setting up a window to receive data exchange messages, with this Library a callback procedure is registered and used by conversation, calls to Library functions are made.
These Libraries makes some aspects of managing a data exchange conversation easier, although an API with 26 functions can hardly be called uncomplicated.
Probably the best motivation for switching to Management Library is future compatibility.
The documentation hints that Management Library may, in the future, take advantage of better inter-process communication methods available in Windows NT.
Windows3.
x: Two of the strengths of Microsoft's Windows operating environment and its Dynamic Data Exchange protocol, which supports hot links between programs.
Windows uses two memory pools.
The local pool is specific to the applications.
The global pool can be accessed by any program in the system.
Local memory is faster and more efficient but limited to chunks of 64-Kb, a DOS limitation.
Windows 3.
x relies on DOS as its base operating system and inherits some of its limitations, such as the 64-Kb segments.
Applications that require a great deal of systems resources (in Windows terms), such as text-intensive or data-entry applications, are limited to storing these system resources in 64-Kb areas.
The amount of physical memory on the machine has no bearing on this limitation.
Companies that have designed systems to overcome this technical obstacle admit that it is doable but not easy.
Dynamic Link Libraries: Dynamic link libraries allow coded routines to be modularized and improve the execution performance and maintainability of an application.
Code can be packaged according to functionality and performance considerations.
However, poor packaging decisions will result in poor performance.
A change in any module requires re-linking the libraries of which it was a part.
Dynamic link libraries can be loaded with the application or as needed.
Both Windows and OS/2 Presentation Manager support Dynamic link libraries.
Dynamic Data Exchange: Dynamic Data Exchange provides automatic information exchange between applications.
These data exchange can be used to link a group of cells between two programs, such as Microsoft's Excel and Word for Windows.
If part of the spreadsheet or a graph of the spreadsheet data is loaded into a document and the spreadsheet numbers change, the corresponding area of the document is automatically updated.
304 The Windows 3.
1 alternatives to Dynamic Data Exchange that Microsoft is promoting are OLE and Dynamic Data Exchange Management Library.
It is a Dynamic link library that provides a higher-level interface than the bare bones data exchange specification.
Instead of setting up a window to receive data exchange messages, with this Library a callback procedure is registered and used by conversation, calls to Library functions are made.
These Libraries makes some aspects of managing a data exchange conversation easier, although an API with 26 functions can hardly be called uncomplicated.
Probably the best motivation for switching to Management Library is future compatibility.
The documentation hints that Management Library may, in the future, take advantage of better inter-process communication methods available in Windows NT.
Source...