SVDI: a "Single View, Multiple Documents" MFC Architecture

================================================================================
    MICROSOFT FOUNDATION CLASS LIBRARY : SplitSVDI Project Overview
===============================================================================

The application wizard has created this SplitSVDI application for 
you.  This application not only demonstrates the basics of using the Microsoft 
Foundation Classes but is also a starting point for writing your application.

This file contains a summary of what you will find in each of the files that
make up your SplitSVDI application.

SplitSVDI.vcproj
    This is the main project file for VC++ projects generated using an application wizard. 
    It contains information about the version of Visual C++ that generated the file, and 
    information about the platforms, configurations, and project features selected with the
    application wizard.

SplitSVDI.h
    This is the main header file for the application.  It includes other
    project specific headers (including Resource.h) and declares the
    CSplitSVDIApp application class.

SplitSVDI.cpp
    This is the main application source file that contains the application
    class CSplitSVDIApp.

SplitSVDI.rc
    This is a listing of all of the Microsoft Windows resources that the
    program uses.  It includes the icons, bitmaps, and cursors that are stored
    in the RES subdirectory.  This file can be directly edited in Microsoft
    Visual C++. Your project resources are in 1033.

res\SplitSVDI.ico
    This is an icon file, which is used as the application's icon.  This
    icon is included by the main resource file SplitSVDI.rc.

res\SplitSVDI.rc2
    This file contains resources that are not edited by Microsoft 
    Visual C++. You should place all resources not editable by
    the resource editor in this file.
/////////////////////////////////////////////////////////////////////////////

For the main frame window:
    The project includes a standard MFC interface.
MainFrm.h, MainFrm.cpp
    These files contain the frame class CMainFrame, which is derived from
    CFrameWnd and controls all SDI frame features.
res\Toolbar.bmp
    This bitmap file is used to create tiled images for the toolbar.
    The initial toolbar and status bar are constructed in the CMainFrame
    class. Edit this toolbar bitmap using the resource editor, and
    update the IDR_MAINFRAME TOOLBAR array in SplitSVDI.rc to add
    toolbar buttons.
/////////////////////////////////////////////////////////////////////////////

The application wizard creates one document type and one view:

SplitSVDIDoc.h, SplitSVDIDoc.cpp - the document
    These files contain your CSplitSVDIDoc class.  Edit these files to
    add your special document data and to implement file saving and loading
    (via CSplitSVDIDoc::Serialize).
SplitSVDIView.h, SplitSVDIView.cpp - the view of the document
    These files contain your CSplitSVDIView class.
    CSplitSVDIView objects are used to view CSplitSVDIDoc objects.
/////////////////////////////////////////////////////////////////////////////

Other Features:

ActiveX Controls
    The application includes support to use ActiveX controls.

Printing and Print Preview support
    The application wizard has generated code to handle the print, print setup, and print preview
    commands by calling member functions in the CView class from the MFC library.

Split Window
    The application wizard has added support for splitter windows for your application documents.
/////////////////////////////////////////////////////////////////////////////

Other standard files:

StdAfx.h, StdAfx.cpp
    These files are used to build a precompiled header (PCH) file
    named SplitSVDI.pch and a precompiled types file named StdAfx.obj.

Resource.h
    This is the standard header file, which defines new resource IDs.
    Microsoft Visual C++ reads and updates this file.

SplitSVDI.manifest
	Application manifest files are used by Windows XP to describe an applications 
	dependency on specific versions of Side-by-Side assemblies. The loader uses this 
	information to load the appropriate assembly from the assembly cache or private 
	from the application. The Application manifest  maybe included for redistribution 
	as an external .manifest file that is installed in the same folder as the application 
	executable or it may be included in the executable in the form of a resource. 
/////////////////////////////////////////////////////////////////////////////

Other notes:

The application wizard uses "TODO:" to indicate parts of the source code you
should add to or customize.

/////////////////////////////////////////////////////////////////////////////