Add Output Pane for Logs and Messages

[sdottaka]

This PR adds an Output Pane for displaying logs and messages.

The Output Pane can be shown in two ways:

1. Manually, by selecting View -> Output Pane from the menu.
2. Automatically, when a log message with ERROR level is output.

To fix the problem, we need to ensure that CHexMergeDoc conforms to the restricted form of multiple inheritance. This means:

• Inheriting from only one protected base class.
• Inheriting from multiple interfaces (pure virtual classes).
• Inheriting from multiple private implementations if needed.

In this case, we should:

1. Ensure that IMergeDoc and IMDITab are pure virtual classes (interfaces).
2. Change the inheritance of IMergeDoc and IMDITab to public to indicate they are interfaces.
3. Ensure CDocument is the only class providing implementation and is inherited as protected.

To fix the problem, we need to refactor the CImgMergeFrame class to conform to the restricted form of multiple inheritance. This involves:

• Ensuring that the class inherits from only one protected base class.
• Inheriting from multiple interfaces (pure virtual classes) if needed.
• Using private inheritance for any implementation classes.

In this case, we can make IMergeDoc and IMDITab interfaces (pure virtual classes) and inherit from them publicly. We will keep CMergeFrameCommon as the single protected base class.

To fix the problem, we need to ensure that CMergeDoc conforms to the restricted form of multiple inheritance. This means:

• Inheriting from only one protected base class.
• Inheriting from multiple interfaces (pure virtual classes).
• Inheriting from multiple private implementations.

In this case, we can assume that IMergeDoc and IMDITab are interfaces (pure virtual classes). We should change the inheritance of IMDITab to private to conform to the restricted form of multiple inheritance.

To fix the problem, we need to ensure that CWebPageDiffFrame conforms to the restricted form of multiple inheritance. This means it should inherit from only one public/protected class and any number of pure virtual interfaces.

The best way to fix this without changing existing functionality is to:

1. Identify which of the inherited classes (CMergeFrameCommon, IMergeDoc, IMDITab) are pure virtual interfaces.
2. Change the inheritance of CWebPageDiffFrame to inherit from only one public/protected class and the rest as pure virtual interfaces.

To fix the problem, we need to refactor the code to include only header files. This involves creating corresponding header files for each .cpp file included and then including these header files instead. The header files should contain the declarations of the classes, functions, and other entities defined in the .cpp files.

1. Create header files (*.h) for each of the .cpp files included in Foundation.cpp.
2. Move the declarations from the .cpp files to the corresponding header files.
3. Include the newly created header files in Foundation.cpp instead of the .cpp files.

To fix the problem, we need to refactor the code to include only header files. This involves the following steps:

1. Create corresponding header files (*.h) for each of the included .cpp files if they do not already exist.
2. Move the declarations (class declarations, function prototypes, etc.) from the .cpp files to the newly created header files.
3. Ensure that the .cpp files include their corresponding header files.
4. Replace the #include directives for the .cpp files in Foundation.cpp with #include directives for the corresponding header files.

To fix the problem, we need to refactor the code to include only header files. This involves:

1. Creating corresponding header files (.h or .hpp) for each of the .cpp files included.
2. Moving the class declarations and function prototypes to these header files.
3. Ensuring that the .cpp files include their corresponding header files.
4. Updating the Foundation.cpp file to include the new header files instead of the .cpp files.

To fix the problem, we need to refactor the code to include only header files. This involves:

1. Creating corresponding header files (.h or .hpp) for each of the .cpp files included.
2. Moving the declarations of classes, functions, and other necessary elements to these header files.
3. Including these header files in the Foundation.cpp file instead of the .cpp files.

To fix the problem, we need to refactor the code to include only header files. This involves creating header files for each of the .cpp files included and then including these header files instead. The header files should contain the declarations of the classes and functions, while the .cpp files should contain the definitions.

1. Create a header file for each .cpp file included in Foundation.cpp.
2. Move the declarations from the .cpp files to the corresponding header files.
3. Replace the #include directives in Foundation.cpp to include the new header files instead of the .cpp files.

To fix the problem, we need to refactor the code to include only header files. This involves the following steps:

1. Create corresponding header files (.h or .hpp) for each of the .cpp files included in Foundation.cpp.
2. Move the declarations of classes, functions, and other necessary elements from the .cpp files to the newly created header files.
3. Include these header files in Foundation.cpp instead of the .cpp files.

To fix the problem, we need to refactor the code to include only header files. This involves the following steps:

1. Create corresponding header files (*.h) for each of the included .cpp files if they do not already exist.
2. Move the declarations of classes, functions, and other necessary interfaces from the .cpp files to the newly created header files.
3. Replace the #include directives for the .cpp files with #include directives for the corresponding header files.