Re: How do you develop on the PocketPC?

There is also a languishing wincerapi module in the pywin32 source code.  Is
that of use to anyone?

Mark.

> > "Luke Dunstan" <[email protected]> writes:
> >> We should probably consider putting all these scripts in CVS somewhere.
> >
> > And we should probably use the pocketRapi module that Brian Brown
> > posted.
>
> I am interested to know why you prefer it. I can think of the following
> advantages:
>
> - It initialises RAPI the first time you try to use it, and
> remembers this.
> - It includes more file I/O functions.
>
> I'm sure it is good for some purposes, but I can also think of
> some possible
> disadvantages:
>
> - The functions are in a class instead of a module. This means that you
> could create multiple instances of the class, which doesn't make sense.
> - The name "pocketRapi" implies Pocket PC only but RAPI really applies to
> Windows CE in general.
> - It requires win32file.
> - The file I/O functions do not follow the pattern of Python file objects.
> - It doesn't include the last error codes in exceptions raised.
> - It doesn't use "argtypes" or "restype". I don't know if this makes it
> faster?
> - Redistributions in "binary form" must reproduce the copyright notice.
>
> Luke
>
> > 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...