Re: How do you develop on the PocketPC?

"Luke Dunstan" <[email protected]> writes:
> From: "Thomas Heller" <[email protected]>
>> "Luke Dunstan" <[email protected]> writes:
>>
>>> By the way, I've recently tried running the remote part of "winpdb"
>>> (http://www.digitalpeers.com/pythondebugger/) on Windows CE and
>>> connecting to it over TCP/IP from the GUI running on the PC, and after
>>> a trivial change (to handle a lack of PATH environment variable) it
>>> worked fine. Personally I would rather have the ability to communicate
>>> to the remote debugger using ActiveSync rather than only TCP/IP
>>> because it is more convenient especially since I only have Bluetooth
>>> not WiFi, so I have been investigating using the Remote API (RAPI).
>>
>> In case you are talking about the scripts I posted: Although the client
>> and server connect via TCP/IP, the only connection between the pockect
>> PC and the desktop computer I have is the cradle with an USB cable, plus
>> activesync (3.8, IIRC) running.  It seems activesync emulates internet
>> connection on the pocket pc.

> I have noticed that IE works on the PDA when cradled, but I know that
> ActiveSync is not providing a real network adapter on the PC side
> because an extra IP does not appear in the output of 'ipconfig'. This
> prevents running TCP listen servers on the PDA but it is true that
> your method works nicely in this case. As a demonstration of how we
> could make it even more convenient, I have modified it slightly so
> that the server starts the client script on the PDA remotely, using
> RAPI via ctypes. I have put the experimental RAPI interfacing code in
> a separate module "wincerapi".

I have done something very similar in the meantime, and this is getting
very cool.

> We should probably consider putting all these scripts in CVS somewhere.

And we should probably use the pocketRapi module that Brian Brown
posted.

There are important things missing, IMO: the ability to interrupt
running code with ^C, and to terminate the session with typing ^Z.
Unfortunately, I have not even be able to distinguish ^C from ^Z in the
get_input() function.  It seems that both raise an EOFError in the
thread that get_input() runs.  Maybe we cannot use raw_input, and have
to write our own function for that...

Thomas