X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/8e1bf7046ee361c3078cdf8ec1f0456e57a6ede5..5200ca361e9edef8b7c075f8989b2dbe9c4c7ad8:/docs/latex/wx/portnote.tex

diff --git a/docs/latex/wx/portnote.tex b/docs/latex/wx/portnote.tex
index a2f782580a..3e71a18bdb 100644
--- a/docs/latex/wx/portnote.tex
+++ b/docs/latex/wx/portnote.tex
@@ -4,9 +4,9 @@
 
 wxWidgets defines a common API across platforms, but uses the native graphical
 user interface (GUI) on each platform, so your program will take on the native
-look and feel that users are familiar with. Unfortunatelly native toolkits and
-dedicated hardware not always support complete set of API functionality. This
-chapter collects notes about differences among supported platforms and ports.
+look and feel that users are familiar with. Unfortunately native toolkits and
+hardware do not always support the functionality that the wxWidgets API
+requires. This chapter collects notes about differences among supported platforms and ports.
 
 \input wxgtk.tex
 \input wxmsw.tex
@@ -16,3 +16,18 @@ chapter collects notes about differences among supported platforms and ports.
 \input wxmgl.tex
 \input wxx11.tex
 
+\subsection{Documentation for the native toolkits}\label{nativedocs}
+
+It's sometimes useful to interface directly with the underlying toolkit
+used by wxWidgets to e.g. use toolkit-specific features.
+In such case (or when you want to e.g. write a port-specific patch) it can be
+necessary to use the underlying toolkit API directly:
+
+\begin{description}\itemsep=0pt
+\item[{\bf wxMSW}]
+wxMSW port uses win32 API: \urlref{MSDN docs}{http://msdn2.microsoft.com/en-us/library/ms649779.aspx}
+
+\item[{\bf wxGTK}]
+wxGTK port uses GTK+: \urlref{GTK+ 2.x docs}{http://developer.gnome.org/doc/API/2.0/gtk/index.html}
+
+\end{description}
\ No newline at end of file