BCGControlBar软件(VC++源代码编写)，功能介绍就不多说了，Microsoft 都采用的界面库。<br> 如果您不...

================================================================================ MICROSOFT FOUNDATION CLASS LIBRARY : [!output PROJECT_NAME] Project Overview =============================================================================== The application wizard has created this [!output PROJECT_NAME] 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 [!output PROJECT_NAME] application. [!output PROJECT_NAME].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. [!output APP_HEADER] This is the main header file for the application. It includes other project specific headers (including Resource.h) and declares the [!output APP_CLASS] application class. [!output APP_IMPL] This is the main application source file that contains the application class [!output APP_CLASS]. [!output PROJECT_NAME].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 [!output LCID]. res\[!output PROJECT_NAME].ico This is an icon file, which is used as the application's icon. This icon is included by the main resource file [!output PROJECT_NAME].rc. res\[!output RC2_FILE_NAME].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. [!if CONTAINER_SERVER || FULL_SERVER || MINI_SERVER || AUTOMATION || HAS_SUFFIX] [!if !HTML_EDITVIEW] [!output PROJECT_NAME].reg This is an example .reg file that shows you the kind of registration settings the framework will set for you. You can use this as a .reg [!if APP_TYPE_DLG] file to go along with your application. [!else] file to go along with your application or just delete it and rely on the default RegisterShellFileTypes registration. [!endif] [!if AUTOMATION] [!output SAFE_IDL_NAME].idl This file contains the Interface Description Language source code for the type library of your application. [!endif] [!endif] [!endif] [!if !APP_TYPE_DLG] ///////////////////////////////////////////////////////////////////////////// For the main frame window: [!if PROJECT_STYLE_EXPLORER] Windows Explorer Style: The project will include a Windows Explorer-like interface, with two frames. [!else] The project includes a standard MFC interface. [!endif] [!output MAIN_FRAME_HEADER], [!output MAIN_FRAME_IMPL] These files contain the frame class [!output MAIN_FRAME_CLASS], which is derived from [!if APP_TYPE_MDI] CMDIFrameWnd and controls all MDI frame features. [!else] CFrameWnd and controls all SDI frame features. [!endif] [!if PROJECT_STYLE_EXPLORER] [!output TREE_VIEW_HEADER], [!output TREE_VIEW_IMPL] These files contain the left frame class [!output TREE_VIEW_CLASS], which is derived from CTreeView. [!endif] [!if DOCKING_TOOLBAR] 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 [!output MAIN_FRAME_CLASS] class. Edit this toolbar bitmap using the resource editor, and update the IDR_MAINFRAME TOOLBAR array in [!output PROJECT_NAME].rc to add toolbar buttons. [!if MINI_SERVER || FULL_SERVER || CONTAINER_SERVER] res\IToolbar.bmp This bitmap file is used to create tiled images for the toolbar when your server application is in-place activated inside another container. This toolbar is constructed in the [!output INPLACE_FRAME_CLASS] class. This bitmap is similar to the bitmap in res\Toolbar.bmp except that it has many nonserver commands removed. [!endif] [!endif] [!if APP_TYPE_MDI] ///////////////////////////////////////////////////////////////////////////// For the child frame window: ChildFrm.h, ChildFrm.cpp These files define and implement the [!output CHILD_FRAME_CLASS] class, which supports the child windows in an MDI application. [!endif] ///////////////////////////////////////////////////////////////////////////// [!if DOCVIEW] [!if !DB_VIEW_NO_FILE] The application wizard creates one document type and one view: [!output DOC_HEADER], [!output DOC_IMPL] - the document These files contain your [!output DOC_CLASS] class. Edit these files to add your special document data and to implement file saving and loading (via [!output DOC_CLASS]::Serialize). [!if HAS_SUFFIX && !HTML_EDITVIEW] The Document will have the following strings: File extension: [!output FILE_EXTENSION] File type ID: [!output FILE_TYPE_ID] Main frame caption: [!output MAIN_FRAME_CAPTION] Doc type name: [!output DOC_TYPE_NAME] Filter name: [!output FILTER_NAME] File new short name: [!output FILE_NEW_NAME_SHORT] File type long name: [!output FILE_NEW_NAME_LONG] [!endif] [!else] The application wizard creates one view: [!endif] [!output VIEW_HEADER], [!output VIEW_IMPL] - the view of the document These files contain your [!output VIEW_CLASS] class. [!if !DB_VIEW_NO_FILE] [!output VIEW_CLASS] objects are used to view [!output DOC_CLASS] objects. [!endif] [!if APP_TYPE_MDI] res\[!output PROJECT_NAME]Doc.ico This is an icon file, which is used as the icon for MDI child windows for the [!output DOC_CLASS] class. This icon is included by the main resource file [!output PROJECT_NAME].rc. [!endif] [!endif] [!if DB_VIEW_NO_FILE || DB_VIEW_WITH_FILE] ///////////////////////////////////////////////////////////////////////////// Database support: [!output ROWSET_HEADER], [!output ROWSET_IMPL] These files contain your [!output ROWSET_CLASS] class. This class is used to access the data source you selected in the wizard. [!if DB_VIEW_NO_FILE] No serialization support will be added. [!else] Serialization support has been added. [!endif] [!endif] [!if CONTAINER || FULL_SERVER || MINI_SERVER || CONTAINER_SERVER] ///////////////////////////////////////////////////////////////////////////// The application wizard has also created classes specific to OLE [!if CONTAINER || CONTAINER_SERVER] [!output CONTAINER_ITEM_HEADER], [!output CONTAINER_ITEM_IMPL] These files contain your [!output CONTAINER_ITEM_CLASS] class. This class is used to manipulate OLE objects. OLE objects are usually displayed by your [!output VIEW_CLASS] class and serialized as part of your [!output DOC_CLASS] class. [!if ACTIVE_DOC_CONTAINER] The program includes support to contain Active documents within its frame. [!endif] [!endif] [!if MINI_SERVER || FULL_SERVER || CONTAINER_SERVER] [!output SERVER_ITEM_HEADER], [!output SERVER_ITEM_IMPL] These files contain your [!output SERVER_ITEM_CLASS]. This class is used to connect your [!output DOC_CLASS] class to the OLE system, and optionally provide links to your document. [!if ACTIVE_DOC_SERVER] The project has support to create and manage Active documents. [!endif] [!output INPLACE_FRAME_HEADER], [!output INPLACE_FRAME_IMPL] These files contain your [!output INPLACE_FRAME_CLASS]. This class is derived from COleIPFrameWnd and controls all frame features during in-place activation. [!endif