[100] | 1 | ========================================================================
|
---|
| 2 | MICROSOFT FOUNDATION CLASS LIBRARY : LispEditor
|
---|
| 3 | ========================================================================
|
---|
| 4 |
|
---|
| 5 |
|
---|
| 6 | AppWizard has created this LispEditor application for you. This application
|
---|
| 7 | not only demonstrates the basics of using the Microsoft Foundation classes
|
---|
| 8 | but is also a starting point for writing your application.
|
---|
| 9 |
|
---|
| 10 | This file contains a summary of what you will find in each of the files that
|
---|
| 11 | make up your LispEditor application.
|
---|
| 12 |
|
---|
| 13 | LispEditor.dsp
|
---|
| 14 | This file (the project file) contains information at the project level and
|
---|
| 15 | is used to build a single project or subproject. Other users can share the
|
---|
| 16 | project (.dsp) file, but they should export the makefiles locally.
|
---|
| 17 |
|
---|
| 18 | LispEditor.h
|
---|
| 19 | This is the main header file for the application. It includes other
|
---|
| 20 | project specific headers (including Resource.h) and declares the
|
---|
| 21 | CLispEditorApp application class.
|
---|
| 22 |
|
---|
| 23 | LispEditor.cpp
|
---|
| 24 | This is the main application source file that contains the application
|
---|
| 25 | class CLispEditorApp.
|
---|
| 26 |
|
---|
| 27 | LispEditor.rc
|
---|
| 28 | This is a listing of all of the Microsoft Windows resources that the
|
---|
| 29 | program uses. It includes the icons, bitmaps, and cursors that are stored
|
---|
| 30 | in the RES subdirectory. This file can be directly edited in Microsoft
|
---|
| 31 | Visual C++.
|
---|
| 32 |
|
---|
| 33 | LispEditor.clw
|
---|
| 34 | This file contains information used by ClassWizard to edit existing
|
---|
| 35 | classes or add new classes. ClassWizard also uses this file to store
|
---|
| 36 | information needed to create and edit message maps and dialog data
|
---|
| 37 | maps and to create prototype member functions.
|
---|
| 38 |
|
---|
| 39 | res\LispEditor.ico
|
---|
| 40 | This is an icon file, which is used as the application's icon. This
|
---|
| 41 | icon is included by the main resource file LispEditor.rc.
|
---|
| 42 |
|
---|
| 43 | res\LispEditor.rc2
|
---|
| 44 | This file contains resources that are not edited by Microsoft
|
---|
| 45 | Visual C++. You should place all resources not editable by
|
---|
| 46 | the resource editor in this file.
|
---|
| 47 |
|
---|
| 48 | LispEditor.reg
|
---|
| 49 | This is an example .REG file that shows you the kind of registration
|
---|
| 50 | settings the framework will set for you. You can use this as a .REG
|
---|
| 51 | file to go along with your application or just delete it and rely
|
---|
| 52 | on the default RegisterShellFileTypes registration.
|
---|
| 53 |
|
---|
| 54 |
|
---|
| 55 |
|
---|
| 56 | /////////////////////////////////////////////////////////////////////////////
|
---|
| 57 |
|
---|
| 58 | For the main frame window:
|
---|
| 59 |
|
---|
| 60 | MainFrm.h, MainFrm.cpp
|
---|
| 61 | These files contain the frame class CMainFrame, which is derived from
|
---|
| 62 | CMDIFrameWnd and controls all MDI frame features.
|
---|
| 63 |
|
---|
| 64 | res\Toolbar.bmp
|
---|
| 65 | This bitmap file is used to create tiled images for the toolbar.
|
---|
| 66 | The initial toolbar and status bar are constructed in the CMainFrame
|
---|
| 67 | class. Edit this toolbar bitmap using the resource editor, and
|
---|
| 68 | update the IDR_MAINFRAME TOOLBAR array in LispEditor.rc to add
|
---|
| 69 | toolbar buttons.
|
---|
| 70 | /////////////////////////////////////////////////////////////////////////////
|
---|
| 71 |
|
---|
| 72 | For the child frame window:
|
---|
| 73 |
|
---|
| 74 | ChildFrm.h, ChildFrm.cpp
|
---|
| 75 | These files define and implement the CChildFrame class, which
|
---|
| 76 | supports the child windows in an MDI application.
|
---|
| 77 |
|
---|
| 78 | /////////////////////////////////////////////////////////////////////////////
|
---|
| 79 |
|
---|
| 80 | AppWizard creates one document type and one view:
|
---|
| 81 |
|
---|
| 82 | LispEditorDoc.h, LispEditorDoc.cpp - the document
|
---|
| 83 | These files contain your CLispEditorDoc class. Edit these files to
|
---|
| 84 | add your special document data and to implement file saving and loading
|
---|
| 85 | (via CLispEditorDoc::Serialize).
|
---|
| 86 |
|
---|
| 87 | LispEditorView.h, LispEditorView.cpp - the view of the document
|
---|
| 88 | These files contain your CLispEditorView class.
|
---|
| 89 | CLispEditorView objects are used to view CLispEditorDoc objects.
|
---|
| 90 |
|
---|
| 91 | res\LispEditorDoc.ico
|
---|
| 92 | This is an icon file, which is used as the icon for MDI child windows
|
---|
| 93 | for the CLispEditorDoc class. This icon is included by the main
|
---|
| 94 | resource file LispEditor.rc.
|
---|
| 95 |
|
---|
| 96 | /////////////////////////////////////////////////////////////////////////////
|
---|
| 97 |
|
---|
| 98 | AppWizard has also created classes specific to OLE
|
---|
| 99 |
|
---|
| 100 | CntrItem.h, CntrItem.cpp - this class is used to
|
---|
| 101 | manipulate OLE objects. OLE objects are usually displayed by your
|
---|
| 102 | CLispEditorView class and serialized as part of your CLispEditorDoc class.
|
---|
| 103 |
|
---|
| 104 |
|
---|
| 105 | /////////////////////////////////////////////////////////////////////////////
|
---|
| 106 | Other standard files:
|
---|
| 107 |
|
---|
| 108 | StdAfx.h, StdAfx.cpp
|
---|
| 109 | These files are used to build a precompiled header (PCH) file
|
---|
| 110 | named LispEditor.pch and a precompiled types file named StdAfx.obj.
|
---|
| 111 |
|
---|
| 112 | Resource.h
|
---|
| 113 | This is the standard header file, which defines new resource IDs.
|
---|
| 114 | Microsoft Visual C++ reads and updates this file.
|
---|
| 115 |
|
---|
| 116 | /////////////////////////////////////////////////////////////////////////////
|
---|
| 117 | Other notes:
|
---|
| 118 |
|
---|
| 119 | AppWizard uses "TODO:" to indicate parts of the source code you
|
---|
| 120 | should add to or customize.
|
---|
| 121 |
|
---|
| 122 | If your application uses MFC in a shared DLL, and your application is
|
---|
| 123 | in a language other than the operating system's current language, you
|
---|
| 124 | will need to copy the corresponding localized resources MFC42XXX.DLL
|
---|
| 125 | from the Microsoft Visual C++ CD-ROM onto the system or system32 directory,
|
---|
| 126 | and rename it to be MFCLOC.DLL. ("XXX" stands for the language abbreviation.
|
---|
| 127 | For example, MFC42DEU.DLL contains resources translated to German.) If you
|
---|
| 128 | don't do this, some of the UI elements of your application will remain in the
|
---|
| 129 | language of the operating system.
|
---|
| 130 |
|
---|
| 131 | /////////////////////////////////////////////////////////////////////////////
|
---|