Lines Matching refs:to
20 can dramatically simplify the code required to build many kinds of application.
22 The idea is that you can model your application primarily in terms of {\it documents} to store data
23 and provide interface-independent operations upon it, and {\it views} to visualise and manipulate
24 the data. Documents know how to do input and output given stream objects, and views are responsible
26 If a document's data changes, all views should be updated to reflect the change.
30 of popping up file selectors, opening and closing files, asking the user to save
31 modifications, routing menu commands to appropriate (possibly default) code, even
34 and objects to achieve more than the default behaviour.
42 (such as a scrolled window) that are needed for the view(s). You may need to route some events
43 to views or documents, for example OnPaint needs to be routed to wxView::OnDraw.
51 as many wxDocTemplate instances as necessary to define relationships between documents and
55 If you wish to implement Undo/Redo, you need to derive your own class(es) from wxCommand
60 Here are a few examples of the tailoring you can do to go beyond the default framework
64 \item Override wxDocument::OnCreateCommandProcessor to define a different Do/Undo strategy,
66 \item Override wxView::OnCreatePrintout to create an instance of a derived \helpref{wxPrintout}{wxprintout}\rtfsp
67 class, to provide multi-page document facilities.
68 \item Override wxDocManager::SelectDocumentPath to provide a different file selector.
72 Note that to activate framework functionality, you need to use some or all of
90 The wxDocument class can be used to model an application's file-based
97 The programmer just needs to define a minimal set of classes and member functions
98 for the framework to call when necessary. Data, and the means to view and edit
104 may be no call for {\it views} on {\it documents} or the ability to open, edit and save
109 To use the abstract wxDocument class, you need to derive a new class and override
111 LoadObject will be called by the framework when the document needs to be saved
115 to allow the framework to create document objects on demand. When you create
117 should pass CLASSINFO(YourDocumentClass) to the wxDocTemplate constructor
118 so that it knows how to create an instance of this class.
120 If you do not wish to use the wxWidgets method of creating document
122 to return an instance of the appropriate class.
130 The wxView class can be used to model the viewing and editing component of
137 To use the abstract wxView class, you need to derive a new class and override
139 want to respond to menu commands from the frame containing the view.
142 to allow the framework to create view objects on demand. When you create
144 should pass CLASSINFO(YourViewClass) to the wxDocTemplate constructor
145 so that it knows how to create an instance of this class.
147 If you do not wish to use the wxWidgets method of creating view
149 to return an instance of the appropriate class.
157 The wxDocTemplate class is used to model the relationship between a
160 templates managed by the wxDocManager instance is used to create
163 and how to create a document or view.
170 list view. You would pass the same document class and default file extension to both
188 To use the wxDocTemplate class, you do not need to derive a new class.
189 Just pass relevant information to the constructor including CLASSINFO(YourDocumentClass) and
190 CLASSINFO(YourViewClass) to allow dynamic instance creation.
191 If you do not wish to use the wxWidgets method of creating document
193 and wxDocTemplate::CreateView to return instances of the appropriate class.
195 {\it NOTE}: the document template has nothing to do with the C++ template construct.
210 derive a class and override some members to extend or change the functionality.
226 a toolbar button or any other means provided by the application to
230 switch statements and functions in a way that may be hard to
234 to a \helpref{wxCommandProcessor}{wxcommandprocessoroverview} object to execute and
261 wxFileHistory encapsulates functionality to record the last few files visited, and
262 to allow the user to quickly load these files using the list appended to the File menu.
265 to derive from it to allow different behaviour, such as popping up a scrolling
270 appending filenames that are added to the history. Please notice that currently
273 initialized with the existing filenames in the history and so you need to call
275 explicitly in order to initialize the menu with the existing list of MRU files.
278 \texttt{wxID\_FILE1} to \texttt{wxID\_FILE9}.
280 In order to respond to a file load command from one of these identifiers,
281 you need to handle them using an event handler, for example:
308 to use in menus.