The most mature ports of our toolkit (wxGTK, wxMSW and wxMac) are nearly equally advanced in terms of features. The development on them is "easy" - they all have the same screen sizes, keyboards, pointing devices, and sounds so once a wrapper around their native API is in place, the ports can share a common wxWidgets infrastructure for events, placement of controls etc.
A few releases earlier we started work on a new family of ports that are increasingly demanded by the market: handhelds, phones and PDAS. See more about it at http://wxwidgets.org/docs/embedded.htm
wxWinCE is the name given to wxMSW when compiled on Windows CE devices. We have a dedicated section in our manual about this port, see: http://www.lpthe.jussieu.fr/~zeitlin/wxWindows/docs/wxwin_wxmswport.html#wxmswport
Are you a wxWinCE user? What do you miss most? When and how do you use #ifdef __WXWINCE__ in your code? Do you have some own improvements to this port? Please share any opinions and findings about the current state of the wxWinCE port on wx-dev and (for bugs and patches) the SourceForge trackers, and let's make it better together for future releases.
Subscribe to:
Post Comments (Atom)
4 comments:
The most needed thing related to wxWinCE (and other ports for mobile devices) is a good tutorial about how to set up the development process using this ports, includeing how to set up emulator and some description of where to use such applications (some success stories also could be helpful. Storytelling also is a good way of sharing knowledge).
Information which can be found at wxwidgets.org seems to be not very helpful. It just says that indded, such wxWidgets ports exist and does not explain how to start the develpment and ehere to find needed tools. However such information could be very helpful.
The wxWiki page about it may be helpful.
Hi,
For me the most important things in wxCE are:
1. Remove the terrible OK button on each Dialog, make it optional.
I also have some problem with wxDialog, but I can not to precise it. I try to make an example and let you know.
2. More tests, more manual, for eVC++ 4.0 and for VS 2005.
Regards,
does wxwince support wince 6.0 x86?
Post a Comment