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