Always use wxFULL_REPAINT_ON_RESIZE for generic status bar.

[wxWidgets.git] / docs / latex / wx / tprint.tex

diff --git a/docs/latex/wx/tprint.tex b/docs/latex/wx/tprint.tex
index b6f031cc26a50bdc50a72127ba44e467feda785b..e22b0c5b8cb162e2ca4e448f9e4e23d7e669bd1d 100644 (file)
--- a/docs/latex/wx/tprint.tex
+++ b/docs/latex/wx/tprint.tex
@@ -1,21 +1,25 @@
 \section{Printing overview}\label{printingoverview}
 
 \section{Printing overview}\label{printingoverview}
 

-Classes: \helpref{wxPrintout}{wxprintout}, \helpref{wxPrinter}{wxprinter},\rtfsp
-\helpref{wxPrintPreview}{wxprintpreview}, \helpref{wxPrinterDC}{wxprinterdc},\rtfsp
-\helpref{wxPrintDialog}{wxprintdialog}.
+Classes: \helpref{wxPrintout}{wxprintout}, 
+\helpref{wxPrinter}{wxprinter}, 
+\helpref{wxPrintPreview}{wxprintpreview}, 
+\helpref{wxPrinterDC}{wxprinterdc}, 
+\helpref{wxPrintDialog}{wxprintdialog}, 
+\helpref{wxPrintData}{wxprintdata}, 
+\helpref{wxPrintDialogData}{wxprintdialogdata}, 
+\helpref{wxPageSetupDialog}{wxpagesetupdialog}, 
+\helpref{wxPageSetupDialogData}{wxpagesetupdialogdata}

 
 The printing framework relies on the application to provide classes
 whose member functions can respond to particular requests, such
 as `print this page' or `does this page exist in the document?'.
 
 The printing framework relies on the application to provide classes
 whose member functions can respond to particular requests, such
 as `print this page' or `does this page exist in the document?'.

-This method allows wxWindows to take over the housekeeping duties of
+This method allows wxWidgets to take over the housekeeping duties of

 turning preview pages, calling the print dialog box, creating
 the printer device context, and so on: the application can concentrate
 on the rendering of the information onto a device context.
 turning preview pages, calling the print dialog box, creating
 the printer device context, and so on: the application can concentrate
 on the rendering of the information onto a device context.

-The printing framework is mainly a Windows feature; PostScript
-support under non-Windows platforms is emerging but has not been rigorously tested.

 
 

-The \helpref{document/view framework}{docviewoverview} creates a default wxPrintout
-object for every view, calling wxView::OnDraw to achieve a
+The \helpref{document/view framework}{docviewoverview} creates a default
+wxPrintout object for every view, calling wxView::OnDraw to achieve a

 prepackaged print/preview facility.
 
 A document's printing ability is represented in an application by a
 prepackaged print/preview facility.
 
 A document's printing ability is represented in an application by a


@@ -26,7 +30,7 @@ previewing. The following code (from the printing sample) shows how easy
 it is to initiate printing, previewing and the print setup dialog, once the wxPrintout
 functionality has been defined. Notice the use of MyPrintout for
 both printing and previewing. All the preview user interface functionality
 it is to initiate printing, previewing and the print setup dialog, once the wxPrintout
 functionality has been defined. Notice the use of MyPrintout for
 both printing and previewing. All the preview user interface functionality

-is taken care of by wxWindows. For details on how MyPrintout is defined,
+is taken care of by wxWidgets. For details on how MyPrintout is defined,

 please look at the printout sample code.
 
 \begin{verbatim}
 please look at the printout sample code.
 
 \begin{verbatim}


@@ -34,26 +38,48 @@ please look at the printout sample code.
     {
       wxPrinter printer;
       MyPrintout printout("My printout");
     {
       wxPrinter printer;
       MyPrintout printout("My printout");

-      printer.Print(this, &printout, TRUE);
+      printer.Print(this, &printout, true);

       break;
     }
     case WXPRINT_PREVIEW:
     {
       // Pass two printout objects: for preview, and possible printing.
       wxPrintPreview *preview = new wxPrintPreview(new MyPrintout, new MyPrintout);
       break;
     }
     case WXPRINT_PREVIEW:
     {
       // Pass two printout objects: for preview, and possible printing.
       wxPrintPreview *preview = new wxPrintPreview(new MyPrintout, new MyPrintout);

-      wxPreviewFrame *frame = new wxPreviewFrame(preview, this, "Demo Print Preview", 100, 100, 600, 650);
+      wxPreviewFrame *frame = new wxPreviewFrame(preview, this, "Demo Print Preview", wxPoint(100, 100), wxSize(600, 650));

       frame->Centre(wxBOTH);
       frame->Initialize();
       frame->Centre(wxBOTH);
       frame->Initialize();

-      frame->Show(TRUE);
-      break;
-    }
-    case WXPRINT_PRINT_SETUP:
-    {
-      wxPrintDialog printerDialog(this);
-      printerDialog.GetPrintData().SetSetupDialog(TRUE);
-      printerDialog.Show(TRUE);
+      frame->Show(true);

       break;
     }
 \end{verbatim}
 
       break;
     }
 \end{verbatim}
 

+\section{Printing under Unix (GTK+)}\label{unixprinting}
+
+Printing under Unix has always been a cause of problems as Unix
+does not provide a standard way to display text and graphics
+on screen and print it to a printer using the same application
+programming interface - instead, displaying on screen is done
+via the X11 library while printing has to be done with using
+PostScript commands. This was particularly difficult to handle
+for the case of fonts with the result that only a selected
+number of application could offer WYSIWYG under Unix. Equally,
+wxWidgets offered its own printing implementation using PostScript
+which never really matched the screen display.
+
+Starting with version 2.8.X, the GNOME project provides printing
+support through the libgnomeprint and libgnomeprintui libraries
+by which especially the font problem is mostly solved. Beginning
+with version 2.5.4, the GTK+ port of wxWidgets can make use of
+these libraries if wxWidgets is configured accordingly and if the
+libraries are present. You need to configure wxWidgets with the
+{\it configure --with-gnomeprint} switch and you application will
+then search for the GNOME print libraries at runtime. If they
+are found, printing will be done through these, otherwise the
+application will fall back to the old PostScript printing code.
+Note that the application will not require the GNOME print libraries
+to be installed in order to run (there will be no dependency on
+these libraries).
+
+It is expected that the printing code that is currently implemented
+in the GNOME print libraries will be moved into GTK+ later.