]>
git.saurik.com Git - wxWidgets.git/blob - docs/doxygen/mainpages/platdetails.h
1 /////////////////////////////////////////////////////////////////////////////
3 // Purpose: Platform details page of the Doxygen manual
4 // Author: wxWidgets team
6 // Licence: wxWindows license
7 /////////////////////////////////////////////////////////////////////////////
12 @page page_port Platform Details
14 wxWidgets defines a common API across platforms, but uses the native graphical
15 user interface (GUI) on each platform, so your program will take on the native
16 look and feel that users are familiar with. Unfortunately native toolkits and
17 hardware do not always support the functionality that the wxWidgets API
18 requires. This chapter collects notes about differences among supported platforms
21 @li @ref page_port_wxgtk
22 @li @ref page_port_wxmac
23 @li @ref page_port_wxcocoa
24 @li @ref page_port_wxos2
25 @li @ref page_port_wxmgl
26 @li @ref page_port_wxx11
27 @li @ref page_port_wxmsw
28 @li @ref page_port_nativedocs
35 @section page_port_wxgtk wxGTK
38 <img src="gtk_logo.png" alt="GTK logo" title="GTK logo" class="logo">
41 wxGTK is a port of wxWidgets using the GTK+ library.
42 It makes use of GTK+'s native widgets wherever possible and uses
43 wxWidgets' generic controls when needed. GTK+ itself has been
44 ported to a number of systems, but so far only the original X11
45 version is supported. Support for other GTK+ backends is planned,
46 such as the new DirectFB backend.
48 All work is being done on GTK+ version 2.0 and above. Support for
49 GTK+ 1.2 will be deprecated in a later release.
51 You will need GTK+ 2.6 or higher which is available from:
55 The newer version of GTK+ you use, the more native widgets and
56 features will be utilized. We have gone to a great extent to
57 allow compiling wxWidgets applications with a latest version of
58 GTK+, with the resulting binary working on systems even with a
59 much lower version of GTK+. You will have to ensure that the
60 application is launched with lazy symbol binding for that.
62 In order to configure wxWidgets to compile wxGTK you will
63 need use the @c --with-gtk argument to the @c configure script.
64 This is the default for many systems.
66 GTK+ 1.2 can still be used, albeit discouraged. For that you can
67 pass @c --with-gtk=1 to the @c configure script.
69 For further information, please see the files in docs/gtk
75 @section page_port_wxmac wxMac
78 <img src="osxleopard_logo.png" alt="Mac OS X (Leopard) logo"
79 title="Mac OS X (Leopard) logo" class="logo">
82 wxMac is a port of wxWidgets for the Macintosh OS platform.
83 Currently MacOS X 10.4 or higher are supported. wxMac can
84 be compiled both using Apple's command line developer tools
85 as well as Apple's XCode IDE. wxMac supports both the Intel
86 and PowerPC architectures and can be used to produce
87 "universal binaries" in order create application which can run
88 both architecture. Unfortunately, wxMac does not support any
89 64-bit architecture since Apple decided not to port its Carbon
90 API entirely to 64-bit.
92 For further information, please see the files in docs/mac
97 @section page_port_wxmac wxCocoa
100 <img src="osxleopard_logo.png" alt="Mac OS X (Leopard) logo"
101 title="Mac OS X (Leopard) logo" class="logo">
104 wxCocoa is another port of wxWidgets for the Macintosh OS
105 platform. But in contrat to wxMac, it uses the Cocoa API.
106 Much work has gone into this port and many controls are
107 functional, but the port has not reached the maturity
108 of the wxMac port yet. It should be possible to use wxCocoa
109 on 64-bit architectures.
112 @section page_port_wxmgl wxMGL
114 wxMGL is a port of wxWidgets using the MGL library available
115 from SciTech as the underlying graphics backend. wxMGL draws
116 its widgets using the wxUniversal widget set which is part
117 of wxWidgets. MGL itself runs on a variety of platforms
118 including DOS, Linux hardware (similar to the Linux framebuffer)
119 and various graphics systems such as Win32, X11 and OS/2.
120 Note that currently MGL for Linux runs only on x86-based systems.
122 You will MGL 5.0 or higher which is available from
124 http://www.scitechsoft.com/products/product_download.html
126 In order to configure wxWidgets to compile wxMGL you will
129 @verbatim configure --with-mgl --with-universal @endverbatim
131 Under DOS, wxMGL uses a dmake based make system.
133 For further information, please see the files in docs/mgl
138 @section page_port_wxos2 wxOS2
140 wxOS2 is a port of wxWidgets for the IBM OS/2 Warp3 and Warp4 platforms.
141 This port is currently under construction and in beta phase.
145 @section page_port_wxx11 wxX11
148 <img src="x11_logo.png" alt="X.org logo" title="X.org logo" class="logo">
151 wxX11 is a port of wxWidgets using X11 (The X Window System)
152 as the underlying graphics backend. wxX11 draws its widgets
153 using the wxUniversal widget set which is now part of wxWidgets.
154 wxX11 is well-suited for a number of special applications such
155 as those running on systems with few resources (PDAs) or for
156 applications which need to use a special themed look.
158 In order to configure wxWidgets to compile wxX11 you will
161 @verbatim configure --with-x11 --with-universal @endverbatim
163 For further information, please see the files in docs/x11
164 in the distribution. There is also a page on the use of
165 wxWidgets for embedded applications on the wxWidgets web site.
171 @section page_port_wxmsw wxMSW
174 <img src="win_logo.png" alt="Windows logo" title="Windows logo" class="logo">
177 wxMSW is a port of wxWidgets for the Windows platforms
178 including Windows 95, 98, ME, 2000, NT, XP in ANSI and
179 Unicode mode (for Windows 95 through the MSLU extension
180 library). wxMSW ensures native look and feel for XP
181 as well when using wxWidgets version 2.3.3 or higher.
182 wxMSW can be compile with a great variety of compilers
183 including MS VC++, Borland 5.5, MinGW32, Cygwin and
184 Watcom as well as cross-compilation with a Linux hosted
187 For further information, please see the files in docs/msw
190 @subsection page_port_wxmsw_themedborders Themed borders on Windows
192 Starting with wxWidgets 2.8.5, you can specify the wxBORDER_THEME style to have wxWidgets
193 use a themed border. Using the default XP theme, this is a thin 1-pixel blue border,
194 with an extra 1-pixel border in the window client background colour (usually white) to
195 separate the client area's scrollbars from the border.
197 If you don't specify a border style for a wxTextCtrl in rich edit mode, wxWidgets now gives
198 the control themed borders automatically, where previously they would take the Windows 95-style
199 sunken border. Other native controls such as wxTextCtrl in non-rich edit mode, and wxComboBox,
200 already paint themed borders where appropriate. To use themed borders on other windows, such
201 as wxPanel, pass the wxBORDER_THEME style, or (apart from wxPanel) pass no border style.
203 In general, specifying wxBORDER_THEME will cause a border of some kind to be used, chosen by the platform
204 and control class. To leave the border decision entirely to wxWidgets, pass wxBORDER_DEFAULT.
205 This is not to be confused with specifying wxBORDER_NONE, which says that there should
206 definitely be @e no border.
208 @subsubsection page_port_wxmsw_themedborders_details More detail on border implementation
210 The way that wxMSW decides whether to apply a themed border is as follows.
211 The theming code calls wxWindow::GetBorder() to obtain a border. If no border style has been
212 passed to the window constructor, GetBorder() calls GetDefaultBorder() for this window.
213 If wxBORDER_THEME was passed to the window constructor, GetBorder() calls GetDefaultBorderForControl().
215 The implementation of wxWindow::GetDefaultBorder() on wxMSW calls wxWindow::CanApplyThemeBorder()
216 which is a virtual function that tells wxWidgets whether a control can have a theme
217 applied explicitly (some native controls already paint a theme in which case we should not
218 apply it ourselves). Note that wxPanel is an exception to this rule because in many cases
219 we wish to create a window with no border (for example, notebook pages). So wxPanel
220 overrides GetDefaultBorder() in order to call the generic wxWindowBase::GetDefaultBorder(),
221 returning wxBORDER_NONE.
223 @subsection page_port_wxmsw_wince wxWinCE
225 wxWinCE is the name given to wxMSW when compiled on Windows CE devices;
226 most of wxMSW is common to Win32 and Windows CE but there are
227 some simplifications, enhancements, and differences in
230 For building instructions, see docs/msw/wince in the
231 distribution, also the section about Visual Studio 2005 project
232 files below. The rest of this section documents issues you
233 need to be aware of when programming for Windows CE devices.
235 @subsubsection page_port_wxmsw_wince_ General issues for wxWinCE programming
237 Mobile applications generally have fewer features and
238 simpler user interfaces. Simply omit whole sizers, static
239 lines and controls in your dialogs, and use comboboxes instead
240 of listboxes where appropriate. You also need to reduce
241 the amount of spacing used by sizers, for which you can
242 use a macro such as this:
245 #if defined(__WXWINCE__)
246 #define wxLARGESMALL(large,small) small
248 #define wxLARGESMALL(large,small) large
252 topsizer->Add( CreateTextSizer( message ), 0, wxALL, wxLARGESMALL(10,0) );
255 There is only ever one instance of a Windows CE application running,
256 and wxWidgets will take care of showing the current instance and
257 shutting down the second instance if necessary.
259 You can test the return value of wxSystemSettings::GetScreenType()
260 for a qualitative assessment of what kind of display is available,
261 or use wxGetDisplaySize() if you need more information.
263 You can also use wxGetOsVersion to test for a version of Windows CE at
264 run-time (see the next section). However, because different builds
265 are currently required to target different kinds of device, these
266 values are hard-wired according to the build, and you cannot
267 dynamically adapt the same executable for different major Windows CE
268 platforms. This would require a different approach to the way
269 wxWidgets adapts its behaviour (such as for menubars) to suit the
272 See the "Life!" example (demos/life) for an example of
273 an application that has been tailored for PocketPC and Smartphone use.
275 @note don't forget to have this line in your .rc file, as for
276 desktop Windows applications:
278 @verbatim #include "wx/msw/wx.rc" @endverbatim
280 @subsubsection page_port_wxmsw_wince_sdk Testing for WinCE SDKs
282 Use these preprocessor symbols to test for the different types of device or SDK:
284 @li @b __SMARTPHONE__ Generic mobile devices with phone buttons and a small display
285 @li @b __PDA__ Generic mobile devices with no phone
286 @li @b __HANDHELDPC__ Generic mobile device with a keyboard
287 @li @b __WXWINCE__ Microsoft-powered Windows CE devices, whether PocketPC, Smartphone or Standard SDK
288 @li @b WIN32_PLATFORM_WFSP Microsoft-powered smartphone
289 @li @b __POCKETPC__ Microsoft-powered PocketPC devices with touch-screen
290 @li @b __WINCE_STANDARDSDK__ Microsoft-powered Windows CE devices, for generic Windows CE applications
291 @li @b __WINCE_NET__ Microsoft-powered Windows CE .NET devices (_WIN32_WCE is 400 or greater)
293 wxGetOsVersion will return these values:
295 @li @b wxWINDOWS_POCKETPC The application is running under PocketPC.
296 @li @b wxWINDOWS_SMARTPHONE The application is running under Smartphone.
297 @li @b wxWINDOWS_CE The application is running under Windows CE (built with the Standard SDK).
300 @subsubsection page_port_wxmsw_wince_sizing Window sizing in wxWinCE
302 Top level windows (dialogs, frames) are created always full-screen. Fit() of sizers will not rescale top
303 level windows but instead will scale window content.
305 If the screen orientation changes, the windows will automatically be resized
306 so no further action needs to be taken (unless you want to change the layout
307 according to the orientation, which you could detect in idle time, for example).
308 When input panel (SIP) is shown, top level windows (frames and dialogs) resize
309 accordingly (see wxTopLevelWindow::HandleSettingChange).
311 @subsubsection page_port_wxmsw_wince_toplevel Closing top-level windows in wxWinCE
313 You won't get a wxCloseEvent when the user clicks on the X in the titlebar
314 on Smartphone and PocketPC; the window is simply hidden instead. However the system may send the
315 event to force the application to close down.
317 @subsubsection page_port_wxmsw_wince_hibernation Hibernation in wxWinCE
319 Smartphone and PocketPC will send a wxEVT_HIBERNATE to the application object in low
320 memory conditions. Your application should release memory and close dialogs,
321 and wake up again when the next wxEVT_ACTIVATE or wxEVT_ACTIVATE_APP message is received.
322 (wxEVT_ACTIVATE_APP is generated whenever a wxEVT_ACTIVATE event is received
323 in Smartphone and PocketPC, since these platforms do not support WM_ACTIVATEAPP.)
325 @subsubsection page_port_wxmsw_wince_hwbutt Hardware buttons in wxWinCE
327 Special hardware buttons are sent to a window via the wxEVT_HOTKEY event
328 under Smartphone and PocketPC. You should first register each required button with
329 wxWindow::RegisterHotKey, and unregister the button when you're done with it. For example:
332 win->RegisterHotKey(0, wxMOD_WIN, WXK_SPECIAL1);
333 win->UnregisterHotKey(0);
336 You may have to register the buttons in a wxEVT_ACTIVATE event handler
337 since other applications will grab the buttons.
339 There is currently no method of finding out the names of the special
340 buttons or how many there are.
342 @subsubsection page_port_wxmsw_wince_dialogs Dialogs in wxWinCE
344 PocketPC dialogs have an OK button on the caption, and so you should generally
345 not repeat an OK button on the dialog. You can add a Cancel button if necessary, but some dialogs
346 simply don't offer you the choice (the guidelines recommend you offer an Undo facility
347 to make up for it). When the user clicks on the OK button, your dialog will receive
348 a wxID_OK event by default. If you wish to change this, call wxDialog::SetAffirmativeId
349 with the required identifier to be used. Or, override wxDialog::DoOK (return @false to
350 have wxWidgets simply call Close to dismiss the dialog).
352 Smartphone dialogs do @e not have an OK button on the caption, and are closed
353 using one of the two menu buttons. You need to assign these using wxTopLevelWindow::SetLeftMenu
354 and wxTopLevelWindow::SetRightMenu, for example:
357 #ifdef __SMARTPHONE__
358 SetLeftMenu(wxID_OK);
359 SetRightMenu(wxID_CANCEL, _("Cancel"));
360 #elif defined(__POCKETPC__)
361 // No OK/Cancel buttons on PocketPC, OK on caption will close
363 topsizer->Add( CreateButtonSizer( wxOK|wxCANCEL ), 0, wxEXPAND | wxALL, 10 );
367 For implementing property sheets (flat tabs), use a wxNotebook with wxNB_FLAT|wxNB_BOTTOM
368 and have the notebook left, top and right sides overlap the dialog by about 3 pixels
369 to eliminate spurious borders. You can do this by using a negative spacing in your
370 sizer Add() call. The cross-platform property sheet dialog wxPropertySheetDialog is
371 provided, to show settings in the correct style on PocketPC and on other platforms.
373 Notifications (bubble HTML text with optional buttons and links) will also be
374 implemented in the future for PocketPC.
376 Modeless dialogs probably don't make sense for PocketPC and Smartphone, since
377 frames and dialogs are normally full-screen, and a modeless dialog is normally
378 intended to co-exist with the main application frame.
380 @subsubsection page_port_wxmsw_wince_ppc Menubars and toolbars in PocketPC
382 On PocketPC, a frame must always have a menubar, even if it's empty.
383 An empty menubar/toolbar is automatically provided for dialogs, to hide
384 any existing menubar for the duration of the dialog.
386 Menubars and toolbars are implemented using a combined control,
387 but you can use essentially the usual wxWidgets API; wxWidgets will combine the menubar
388 and toolbar. However, there are some restrictions:
390 @li You must create the frame's primary toolbar with wxFrame::CreateToolBar,
391 because this uses the special wxToolMenuBar class (derived from wxToolBar)
392 to implement the combined toolbar and menubar. Otherwise, you can create and manage toolbars
393 using the wxToolBar class as usual, for example to implement an optional
394 formatting toolbar above the menubar as Pocket Word does. But don't assign
395 a wxToolBar to a frame using SetToolBar - you should always use CreateToolBar
396 for the main frame toolbar.
397 @li Deleting and adding tools to wxToolMenuBar after Realize is called is not supported.
398 @li For speed, colours are not remapped to the system colours as they are
399 in wxMSW. Provide the tool bitmaps either with the correct system button background,
400 or with transparency (for example, using XPMs).
401 @li Adding controls to wxToolMenuBar is not supported. However, wxToolBar supports
404 Unlike in all other ports, a wxDialog has a wxToolBar, automatically created
405 for you. You may either leave it blank, or access it with wxDialog::GetToolBar
406 and add buttons, then calling wxToolBar::Realize. You cannot set or recreate
409 @subsubsection page_port_wxmsw_wince_smart Menubars and toolbars in Smartphone
411 On Smartphone, there are only two menu buttons, so a menubar is simulated
412 using a nested menu on the right menu button. Any toolbars are simply ignored on
415 @subsubsection page_port_wxmsw_wince_closing Closing windows in wxWinCE
417 The guidelines state that applications should not have a Quit menu item,
418 since the user should not have to know whether an application is in memory
419 or not. The close button on a window does not call the window's
420 close handler; it simply hides the window. However, the guidelines say that
421 the Ctrl+Q accelerator can be used to quit the application, so wxWidgets
422 defines this accelerator by default and if your application handles
423 wxID_EXIT, it will do the right thing.
425 @subsubsection page_port_wxmsw_wince_ctx Context menus in wxWinCE
427 To enable context menus in PocketPC, you currently need to call wxWindow::EnableContextMenu,
428 a wxWinCE-only function. Otherwise the context menu event (wxContextMenuEvent) will
429 never be sent. This API is subject to change.
431 Context menus are not supported in Smartphone.
433 @subsubsection page_port_wxmsw_wince_ctrl Control differences on wxWinCE
435 These controls and styles are specific to wxWinCE:
437 @li wxTextCtrl The wxTE_CAPITALIZE style causes a CAPEDIT control to
438 be created, which capitalizes the first letter.
440 These controls are missing from wxWinCE:
442 @li MDI classes MDI is not supported under Windows CE.
443 @li wxMiniFrame Not supported under Windows CE.
445 Tooltips are not currently supported for controls, since on PocketPC controls with
446 tooltips are distinct controls, and it will be hard to add dynamic
449 Control borders on PocketPC and Smartphone should normally be specified with
450 wxBORDER_SIMPLE instead of wxBORDER_SUNKEN. Controls will usually adapt
451 appropriately by virtue of their GetDefaultBorder() function, but if you
452 wish to specify a style explicitly you can use wxDEFAULT_CONTROL_BORDER
453 which will give a simple border on PocketPC and Smartphone, and the sunken border on
456 @subsubsection page_port_wxmsw_wince_help Online help in wxWinCE
458 You can use the help controller wxWinceHelpController which controls
459 simple @c .htm files, usually installed in the Windows directory.
460 See the Windows CE reference for how to format the HTML files.
462 @subsubsection page_port_wxmsw_wince_install Installing your PocketPC and Smartphone applications
464 To install your application, you need to build a CAB file using
465 the parameters defined in a special .inf file. The CabWiz program
466 in your SDK will compile the CAB file from the .inf file and
467 files that it specifies.
469 For delivery, you can simply ask the user to copy the CAB file to the
470 device and execute the CAB file using File Explorer. Or, you can
471 write a program for the desktop PC that will find the ActiveSync
472 Application Manager and install the CAB file on the device,
473 which is obviously much easier for the user.
475 Here are some links that may help.
477 @li A setup builder that takes CABs and builds a setup program is at
478 http://www.eskimo.com/~scottlu/win/index.html.
479 @li Sample installation files can be found in
480 <tt>Windows CE Tools/wce420/POCKET PC 2003/Samples/Win32/AppInst</tt>.
481 @li An installer generator using wxPython can be found at
482 http://ppcquicksoft.iespana.es/ppcquicksoft/myinstall.html.
483 @li Miscellaneous Windows CE resources can be found at
484 http://www.orbworks.com/pcce/resources.html.
485 @li Installer creation instructions with a setup.exe for installing to PPC can be found at
486 http://www.pocketpcdn.com/articles/creatingsetup.html.
487 @li Microsoft instructions are at
488 http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnce30/html/appinstall30.asp?frame=true
489 @li Troubleshooting WinCE application installations:
490 http://support.microsoft.com/default.aspx?scid=KB;en-us;q181007
492 You may also check out <tt>demos/life/setup/wince</tt> which contains
493 scripts to create a PocketPC installation for ARM-based
494 devices. In particular, @c build.bat builds the distribution and
495 copies it to a directory called @c Deliver.
497 @subsubsection page_port_wxmsw_wince_filedlg wxFileDialog in PocketPC
499 Allowing the user to access files on memory cards, or on arbitrary
500 parts of the filesystem, is a pain; the standard file dialog only
501 shows folders under My Documents or folders on memory cards
502 (not the system or card root directory, for example). This is
503 a known problem for PocketPC developers.
505 If you need a file dialog that allows access to all folders,
506 you can use wxGenericFileDialog instead. You will need to include
507 @c wx/generic/filedlgg.h.
509 @subsubsection page_port_wxmsw_wince_evc Embedded Visual C++ Issues
511 <b>Run-time type information</b>
513 If you wish to use runtime type information (RTTI) with eVC++ 4, you need to download
514 an extra library, @c ccrtrtti.lib, and link with it. At the time of
515 writing you can get it from here:
518 http://support.microsoft.com/kb/830482/en-us
521 Otherwise you will get linker errors similar to this:
524 wxwince26d.lib(control.obj) : error LNK2001: unresolved external symbol "const type_info::`vftable'" (??_7type_info@@6B@)
527 <b>Windows Mobile 5.0 emulator</b>
529 Note that there is no separate emulator configuration for Windows Mobile 5.0: the
530 emulator runs the ARM code directly.
532 <b>Visual Studio 2005 project files</b>
534 Unfortunately, Visual Studio 2005, required to build Windows Mobile 5.0 applications,
535 doesn't do a perfect job of converting the project files from eVC++ format.
537 When you have converted the wxWidgets workspace, edit the configuration properties
538 for each configuration and in the Librarian, add a relative path ..\\..\\lib to
539 each library path. For example:
540 <tt>..\\$(PlatformName)\\$(ConfigurationName)\\wx_mono.lib</tt>.
542 Then, for a sample you want to compile, edit the configuration properties
544 <tt>..\\..\\lib\\$(PlatformName)\\$(ConfigurationName)</tt>
545 is in the Linker/General/Additional Library Directories property.
546 Also change the Linker/Input/Additional Dependencies property to something like
547 <tt>coredll.lib wx_mono.lib wx_wxjpeg.lib wx_wxpng.lib wx_wxzlib.lib wx_wxexpat.lib
548 commctrl.lib winsock.lib wininet.lib</tt>
549 (since the library names in the wxWidgets workspace were changed by VS 2005).
551 Alternately, you could could edit all the names to be identical to the original eVC++
552 names, but this will probably be more fiddly.
554 @subsubsection page_port_wxmsw_wince_issues Remaining issues
556 These are some of the remaining problems to be sorted out, and features
559 @li <b>Windows Mobile 5 issues.</b> It is not possible to get the HMENU for
560 the command bar on Mobile 5, so the menubar functions need to be rewritten
561 to get the individual menus without use of a menubar handle. Also the
562 new Mobile 5 convention of using only two menus (and no bitmap buttons) needs to be
564 @li <b>Sizer speed.</b> Particularly for dialogs containing notebooks,
565 layout seems slow. Some analysis is required.
566 @li <b>Notification boxes.</b> The balloon-like notification messages, and their
567 icons, should be implemented. This will be quite straightforward.
568 @li <b>SIP size.</b> We need to be able to get the area taken up by the SIP (input panel),
569 and the remaining area, by calling SHSipInfo. We also may need to be able to show and hide
570 the SIP programmatically, with SHSipPreference. See also the <em>Input Dialogs</em> topic in
571 the <em>Programming Windows CE</em> guide for more on this, and how to have dialogs
572 show the SIP automatically using the WC_SIPREF control.
573 @li <b>wxStaticBitmap.</b> The About box in the "Life!" demo shows a bitmap that is
574 the correct size on the emulator, but too small on a VGA Pocket Loox device.
575 @li <b>wxStaticLine.</b> Lines don't show up, and the documentation suggests that
576 missing styles are implemented with WM_PAINT.
577 @li <b>HTML control.</b> PocketPC has its own HTML control which can be used for showing
578 local pages or navigating the web. We should create a version of wxHtmlWindow that uses this
579 control, or have a separately-named control (wxHtmlCtrl), with a syntax as close as possible
581 @li <b>Tooltip control.</b> PocketPC uses special TTBUTTON and TTSTATIC controls for adding
582 tooltips, with the tooltip separated from the label with a double tilde. We need to support
583 this using SetToolTip.(Unfortunately it does not seem possible to dynamically remove the tooltip,
584 so an extra style may be required.)
585 @li <b>Focus.</b> In the wxPropertySheetDialog demo on Smartphone, it's not possible to navigate
586 between controls. The focus handling in wxWidgets needs investigation. See in particular
587 src/common/containr.cpp, and note that the default OnActivate handler in src/msw/toplevel.cpp
588 sets the focus to the first child of the dialog.
589 @li <b>OK button.</b> We should allow the OK button on a dialog to be optional, perhaps
590 by using wxCLOSE_BOX to indicate when the OK button should be displayed.
591 @li <b>Dynamic adaptation.</b> We should probably be using run-time tests more
592 than preprocessor tests, so that the same WinCE application can run on different
593 versions of the operating system.
594 @li <b>Modeless dialogs.</b> When a modeless dialog is hidden with the OK button, it doesn't restore the
595 frame's menubar. See for example the find dialog in the dialogs sample. However, the menubar is restored
596 if pressing Cancel (the window is closed). This reflects the fact that modeless dialogs are
597 not very useful on Windows CE; however, we could perhaps destroy/restore a modeless dialog's menubar
598 on deactivation and activation.
599 @li <b>Home screen plugins.</b> Figure out how to make home screen plugins for use with wxWidgets
600 applications (see http://www.codeproject.com/ce/CTodayWindow.asp for inspiration).
601 Although we can't use wxWidgets to create the plugin (too large), we could perhaps write
602 a generic plugin that takes registry information from a given application, with
603 options to display information in a particular way using icons and text from
604 a specified location.
605 @li <b>Further abstraction.</b> We should be able to abstract away more of the differences
606 between desktop and mobile applications, in particular for sizer layout.
607 @li <b>Dialog captions.</b> The blue, bold captions on dialogs - with optional help button -
608 should be catered for, either by hard-wiring the capability into all dialogs and panels,
609 or by providing a standard component and sizer.
612 @section page_port_nativedocs Documentation for the native toolkits
614 It's sometimes useful to interface directly with the underlying toolkit
615 used by wxWidgets to e.g. use toolkit-specific features.
616 In such case (or when you want to e.g. write a port-specific patch) it can be
617 necessary to use the underlying toolkit API directly:
619 @li wxMSW port uses win32 API: see MSDN docs at http://msdn2.microsoft.com/en-us/library/ms649779.aspx
620 @li wxGTK port uses GTK+: see GTK+ 2.x docs at http://developer.gnome.org/doc/API/2.0/gtk/index.html
621 @li wxMac port uses the Carbon API: see Carbon docs at http://developer.apple.com/carbon
622 @li wxCocoa port uses the Cocoa API: see Cocoa docs at http://developer.apple.com/carbon