I just installed Microsoft's eMbedded Visual Basic and eMbedded Visual C++ for developing PocketPC applications. What a joke! eVB is nothing more than VBScript, which offers a very limited subset of the VB language and relatively few controls. The controls that it does offer are full of inconsistencies as far as appearance and functionality are concerned. For example, the command button and scroll bar controls are plain 2D, whereas the scrollbars built into the textbox control are 3D. Other controls that VB programmers are used to offer very limited functionality. For example, there is no .Image property of the PictureBox control for obtaining the graphical contents of the control. Furthermore, there is only support for one data type (Variant) and a large part of the WinCE API is totally inaccessible from eVB. Also, because eVB is interpreted, it does not generate .EXE files, but instead generates .VB files that are interpreted by VBSCRIPT.DLL (which is generally built into the firmware on a Pocket PC. Even so, it still requires at least one runtime file, PVBLOAD.EXE, and most of the time additional files). To top it all off, there are at least three different flavors of Windows CE - handheld, palmtop, and PocketPC. Some commands/controls (or properties and methods of) that are available in one version may not be supported in another. A real mess.
On the other hand, eMbedded Visual C++ allows you to do virtually anything, but is very cumbersome to use. I couldn't get any the sample projects to run. I'm sure if I spent a few more hours I could manage to get stuff to work, but when I looked at the code for accomplishing even the simplest of tasks, it seemed daunting. If you're going to do any sort of user interface, Microsoft recommends that you use eVB.
It would be great if there was a way to use PowerBASIC to generate Windows CE .EXE files. Does anyone know if this is possible? I realize that there would need to be some sort of add-on or patch, since there are several different processors used by PocketPC manufacturers (Intel Strong ARM, Hitachi, MIPS). If not, has anyone heard if the company is bringing out a WinCE development product? Based on the comments I've been reading in the newsgroups, people are generally displeased with the half-assed development products Microsoft has provided for developing on the PocketPC platform. I think PowerBASIC is sitting on a goldmine if they can pull it off. Relative to past attempts, the PocketPC platform (Windows CE 3.0) is and will continue to be very successful. My only advice to PowerBASIC would be to offer a complete tool, not just a subset, that can produce fast and efficient .EXE files and can access the entire WinCE API.
[This message has been edited by Dean Sadata (edited August 15, 2000).]
On the other hand, eMbedded Visual C++ allows you to do virtually anything, but is very cumbersome to use. I couldn't get any the sample projects to run. I'm sure if I spent a few more hours I could manage to get stuff to work, but when I looked at the code for accomplishing even the simplest of tasks, it seemed daunting. If you're going to do any sort of user interface, Microsoft recommends that you use eVB.
It would be great if there was a way to use PowerBASIC to generate Windows CE .EXE files. Does anyone know if this is possible? I realize that there would need to be some sort of add-on or patch, since there are several different processors used by PocketPC manufacturers (Intel Strong ARM, Hitachi, MIPS). If not, has anyone heard if the company is bringing out a WinCE development product? Based on the comments I've been reading in the newsgroups, people are generally displeased with the half-assed development products Microsoft has provided for developing on the PocketPC platform. I think PowerBASIC is sitting on a goldmine if they can pull it off. Relative to past attempts, the PocketPC platform (Windows CE 3.0) is and will continue to be very successful. My only advice to PowerBASIC would be to offer a complete tool, not just a subset, that can produce fast and efficient .EXE files and can access the entire WinCE API.
[This message has been edited by Dean Sadata (edited August 15, 2000).]
Comment