about to start developing. Still some confusion

[UMCP_matt]

1. GAPI is made by microsoft. How are all these programs related to each other (gapi,gapidraw,pocketfrog,easyCE,overloaded). Is gapidraw a extension of gapi? is EasyCE a extension of gapi? Is everything just a wrapper of gapi? Is gapi sort of like the DirectX of handhelds and everything like a wrapper or GAPI?
So are there 4 choices when programming
gapi. pocketfrog. easyce. overloaded. right?

2. I am also confused if I will use embedded c++ 4.0 OR VC++ 6.0 OR VS.NET? (I have the 1st and 3rd installed)

basically what is everyones setup?

[fzammetti]

[Michael Y]

[R0B]

[BurningSheep]

recommended by who? I see the devs recommending to use VC++ 6 for development on your PC and use EVC++ 3 for compiling to test/run it on your PPC

[edit]
VS.NET would be just as good for desktop development/debugging
[/edit]

[R0B]

That seems pointless. The only ones I know who would say use VC++ 6.0 first are

1)those who program for win ce 2.11 (which you originally had to use 6.0)

2)Those who like jumping on the band wagon just to say evc++ sucks. It is actually just more work, since workspace files are not compatible between the two

[BurningSheep]

[R0B]

[UMCP_matt]

[Michael Y]

[BurningSheep]

[Phantom]

[Phantom]

[Dan East]

To expand on what Rob said, before eVC++ was released one had to purchase VC++ 6.0 and then purchase an add-on Windows CE Toolkit to create Windows CE software. With the release of Pocket PC (Windows CE 3.0) MS created standalone, free development platforms (eVC++, eVB). Personally, it is a very rare occurrence that I use VC++ 6.0 during any of my Pocket PC development.

I strongly recommend using Ethernet if you are going to do hard core Windows CE development. You would probably have a total of $150 or so in an Ethernet CF card, hub and NIC for your PC. However, it is without a doubt the fastest method of connecting to your Pocket PC, bar none. It is around 30 times faster than USB. I can download a 1 MB executable and initiate a debug session in around 5 seconds total. Stepping and hitting breakpoints is instantaneous. With USB it takes close to a full minute just to begin a debug session, and 20-30 seconds to step a single line of code.

Oh, WiFi (802.11b) is just as fast as Ethernet - I can tell no difference in performance if my device in within 20 feet or so of my WAP with power-saving off.

Dan East

[UMCP_matt]