Re: [PythonCE] very slow XMLRPCServer
David McNab schrieb: > Hi, > > I'm trying to run an XML-RPC server on my ipaq h4100, based on the > python 'SimpleXMLRPCServer', but it's ridiculously slow to process > requests. > > Turnaround for even the simplest client requests is around 30-40 > seconds. I don't know if this will help you or not: I tried to use XMLRPC betweem a small embedded ARM system runing linux and a Windows PC. The performance of a client on the PC and a server on the embedded system was acceptable (~10 requests per second), but the server on the PC called by a client running on the embedded system was unacceptable: 1 request took around 5 seconds to complete. I have since switched to jsonrpc instead of xmlrpc which has a much better performance: around 70 requests per second, in both directions. Thomas ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] Is there a script that would let me do this?
Thomas Heller schrieb: > Tony Lee schrieb: >> I installed pythonce on my WM6. It works good! >> >> >> I wonder if there is a simple script that can act as a console that >> takes input from the port (telnet) and output the data to the port >> also. >> >> Like a io redirection, so I can just telnet to the WM6 to do script >> development instead of typing on the tiny keyboard. > > I have developed a python 'remote-console' for windows ce. It requires > that the device is connected via ActiveSync. > > http://code.google.com/p/ctypes-stuff/ > > Download the files from > http://ctypes-stuff.googlecode.com/svn/trunk/wince/remote-console/ > and start 'python console.py' on your PC. > Update: I posted a prebuilt binary here (no installation needed, simply run the exe): http://ctypes-stuff.googlecode.com/files/PythonConsole-1.0.exe -- Thanks, Thomas ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] Is there a script that would let me do this?
Tony Lee schrieb: > I installed pythonce on my WM6. It works good! > > > I wonder if there is a simple script that can act as a console that > takes input from the port (telnet) and output the data to the port > also. > > Like a io redirection, so I can just telnet to the WM6 to do script > development instead of typing on the tiny keyboard. I have developed a python 'remote-console' for windows ce. It requires that the device is connected via ActiveSync. http://code.google.com/p/ctypes-stuff/ Download the files from http://ctypes-stuff.googlecode.com/svn/trunk/wince/remote-console/ and start 'python console.py' on your PC. -- Thanks, Thomas ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] pygame / ctypes / SDL
Adam Walley schrieb: > Well, I have now got a small demo app working, which makes use of SDL > LoadBMP, Surface, blit, audio (wav), keysym, and draw functions. I have > compiled a small DLL, that allows access to these functions through ctypes, > and it works very well. The core of the application is a python script, > which then calls the other functions as required. > > I will try to post a link shortly, for any one who would like to take a > look. I am wondering whether this whole exercise is kind of re-inventing the > wheel, since pygame-ctypes was already attempted. However, so far everything > seems to be working smoothly, and I am quite encouraged by the results. Cool. But, I'm curious: what about pyglet? Has someone tried to port that to WinCE? -- Thanks, Thomas ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
[PythonCE] Installation of Python packages on Windows CE
How should Python packages be installed on Windows CE? The context is that I am preparing a new release of comtypes. I have learned so far on this list that a CAB file is a convenient way to install software, but my question is what should this cab file create: - as usual on Windows, a directory tree containing .py files in \Program Files\Python\Python25 or - a zipfile in \Program Files\Python\Python25 which would be put on sys.path by a .pth file in the same directory and imported by the zipimport mechanism? For the zip-file, there are again several possibilities: - should the zipfile be compressed to save space or not? I'm not sure if decompressing slows down importing or not... - Should the zipfile contain only .pyc files to save space, but then source code is not available for tracebacks, for example - Should the zipfile contain only .py files to save space, but importing would probably be slower because the modules have to be recompiled every time Python uses them - Should the zipfile contain .py files plus .pyc files? Or are there even other possibilities? -- Thanks, Thomas ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] The State of Affairs
Lachezar Dobrev schrieb: > 2008/7/30 Thomas Heller <[EMAIL PROTECTED]>: >> ... >> BTW: How do you install a cab on a CE device? > 1. Download CAB using WLAN, WWAN, Bluetooth FTP, Bluetooth PAN, etc. > from the Web-Site, or a network share. > 2. Double-tap the cab file :) > > Works with Windows CE 4, Windows CE 5, Windows CE Embedded 4+, not > sure about Mobile Windows though. Ah thanks. So, is there someone who provides an initial inf file which can be used to create a comtypes .cab file? ;-) -- Thanks, Thomas ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] The State of Affairs
Alexandre Delattre schrieb: > I was thinking that a first step to enhance distribution of PythonCE > apps, would be to be able to create easily .cab for them. > > .cab are installable over the air, as well by cross installing from > desktop. > > If I met enough positive feedback, I'll start trying to implement a > distutils extension that will allow to create .cab the python way > (i.e. Without using directly MS tools) > > Looking forward your feedbacks, Alexandre I'm not sure whether this will help you or not, but I remember that I once had a ctypes-based cab file creator running. Found it in the web archive: http://web.archive.org/web/20050404190244/http://starship.python.net/crew/theller/moin.cgi/CreateCab BTW: How do you install a cab on a CE device? -- Thanks, Thomas ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] Comtypes installation problem...
David Goncalves schrieb: > Hi, > >> By the time I wrote pypoom, comtypes (version 0.3 if I remember well) >> worked out of the box on WinCe. >> >> Sergei, if you send me your tweaked version of comtypes, I think I'll be >> able to replace your "comments" with more portable statements like : >> If os.name == 'ce': ... >> , or so. >> And then submit a preliminary patch to Thomas > > I've done the same on the only needed file '_safearray.py'. > All the parts not working on WinCE are skipped with a > > if os.name != "ce" : > x > x > > > The file is from the 0.4.2 version of comtypes. Before I apply this patch to comtypes: This patch allows to *import* the comtypes.safearray module, but it also probably makes it non-functional. So, the question is: Which COM objects are people using on Windows CE? Do these objects use the SAFEARRAY data type? Thanks, Thomas ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] Comtypes installation problem...
David Goncalves schrieb: > Hi, > > I'm trying to install comtypes on Python 2.5 (2007-10 release). > I've copied the "comtypes" folder to "Program files\Python25\Lib". > > When i do a "import comtypes" to check if everything is ok, i > get the following message : > > function "SafeArrayCreateVectorEx" not found > with a lot of debug informations... comtypes uses functions that do not exist on WinCE, and I haven't yet found the time to fix that. If someone would like to provide patches that keep the Windows functionality intact, please go ahead (although I will be in vacation the next two week, starting tomorrow. -- Thanks, Thomas ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] Comtypes installation problem...
Michael Foord schrieb: > David Goncalves wrote: >> Hi, >> >> I'm trying to install comtypes on Python 2.5 (2007-10 release). >> I've copied the "comtypes" folder to "Program files\Python25\Lib". > > That is part of the Win32 extensions for Python which run on the desktop > (with a different CPU and different APIs to your WinCE device). No, comtypes is a pure Python COM package, based on ctypes. No need to compile anything. Thomas ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] getting ctypes to work in 2.4 version
Petri Wunsch schrieb: > Hi, > > is there a separate ctypes package dowloadable for pythonCE 2.4 I > can find it only for normal python but it's kind of hard to install > that foexample in windows mobile device. Look for ctypes-1.0.0.winCE-arm-py2.4.zip in this page: http://sourceforge.net/project/showfiles.php?group_id=71702 You have to select the 1.0.0 release. Thomas ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] remote-console
Jan Ischebeck schrieb:
> Hi Thomas,
>
> Your script works well for me on Ubuntu Feisty.
>
> The only issue I have is, that it doesn't detect the "//Program Files/"
> folder correctly for non-US Pocket PCs. (E.g. German WinCE uses
> "//Programme/").
>
> I've tried to get this directory via CeGetSpecialFolder, but was not
> successful. Below my additions to rapi.py to make use CeGetSpecialFolder.
The magic constant is CSIDL_PROGRAM_FILES = 0x26. I have adapted your patch
somewhat and committed it to the repository. Can you please check if it works
for you?
>
> Jan
>
> #
> # getSpecialFolderPath
>
> rapi.CeGetSpecialFolderPath.errcheck = errcheck
> rapi.CeGetSpecialFolderPath.argtypes = (ctypes.c_int, DWORD,
> ctypes.c_void_p);
>
> def GetSpecialFolderPath(folderid):
> length=128
> buf = ctypes.create_string_buffer('\000' * length)
> rapi.CeGetSpecialFolderPath(folderid, length, buf)
> value = ctypes.string_at(buf, length).decode('utf-16')
> return value[0:value.index('\x00')]
Thanks for tha patch,
Thomas
___
PythonCE mailing list
PythonCE@python.org
http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] remote-console
Ruben Miguelez Garcia schrieb: >> Ah, great. Yes, the current version only works on Windows, it requires >> that the device is connected via ActiveSync. The CeRemoteAPI is used to >> transfer the client script to the device, and start the interpreter there. >> Sorry for this limitation. > >> Is there something on Linux that allows to >> transfer files and start processes on the PDA? > > I really don't know because I didn't have time to investigate it and my > application is already finished, so I won't work more with the PDA for some > time. > > But I think It should be possible. I just connected the usb cable from the > cradle to my laptop and this is the output from the kernel: > > > # dmesg > usb 2-1: new full speed USB device using uhci_hcd and address 2 > drivers/usb/serial/usb-serial.c: USB Serial support registered for Generic > usbcore: registered new driver usbserial_generic > usbcore: registered new driver usbserial > drivers/usb/serial/usb-serial.c: USB Serial Driver core v2.0 > drivers/usb/serial/usb-serial.c: USB Serial support registered for PocketPC > PDA > drivers/usb/serial/ipaq.c: USB PocketPC PDA driver v0.5 > ipaq 2-1:1.0: PocketPC PDA converter detected > usb 2-1: PocketPC PDA converter now attached to ttyUSB0 > usbcore: registered new driver ipaq > - > I found the synce project on sourceforge. This contains a rapi library that emulates the rapi.dll on Windows. I have adapted the remote console sources so that it also works on linux (tested on Ubuntu). I'm not a Linux expert, but here is (in short) what I did: - Installed the synce-serial, synce-dccm, libsynce0, librapi packages. - Cradled the CE device into the USB connector (I use a Dell X50 PDA, with Windows Mobile 2003) - Run these commands (some or all of them with sudo): modprobe ipaq synce-serial-config ttyUSB0 synce-serial-start Now the device connects to the PC, and I can run console.py. Note that there should be no need to adjust anything in the console.py or the client.py sources (at least if you use the default IP address that synce suggests: 192.168.131.102). console.py accepts some command line switches that the python interpreter also understands. Useful are probably "-c " and "-m ". Thomas ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] remote-console
Ruben Miguelez Garcia schrieb: > Dear Thomas, > >> A much improved version is available here: >> >> http://ctypes-stuff.googlecode.com/svn/trunk/wince/remote-console/ >> >> The console.py script is thought to be run on the workstation. Editing >> the client.py script (which is transferred automatically to the PDA) is no >> longer needed. >> >> console.py accepts some command line options which can also be used for >> Python itself: -m 'package', -c 'Python commands', other options are >> accepted but don't do anything: -i, -u. > > Is this program only for Windows? (i.e. to be run on a Windows-Python ) > > I have Linux and it give me some errors [1]. It seems that the problem > is > just importing ctypes.wintypes which crash. > > I have tried to update ctypes many times but the error don't disappear. > > Does anyone have similar problem? > > > Thanks for your time and your program. I'm still using the previous > version. :o) Ah, great. Yes, the current version only works on Windows, it requires that the device is connected via ActiveSync. The CeRemoteAPI is used to transfer the client script to the device, and start the interpreter there. Sorry for this limitation. Is there something on Linux that allows to transfer files and start processes on the PDA? Thomas ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] Bluetooth
Ruben Miguelez Garcia schrieb: > Hello to all, > I am new on the list. > Firstly I will share all my experiences until now. > Then I am going to explain some research that I did about bluetooth > on "Windows CE" because that is my main problem now. > > == Some experiences == > > 1- After read many mails on the list, I decided to use the server & client > connection programs provided on the thread "How do you develop on the > PocketPC?" > > 2- The first execution raise the error "ImportError: No module named ctypes". > Then I updated the windows version inside the PDA to 2.5 and everything fine. > > 3-On the beginning, click on the client.py only opened a Python session > without connect to the server. Then I discovered that with the PDA connected > to the laptop by USB with ActiveSync running, the wifi was not working. After > unplug the USB cable, wifi works fine and one click over the client.py > connect to the server. > > PD: Of course, I had to modify the IP inside the client.py to point to my > laptop. I'm afraid I cannot help with the bluetooth stuff, but I have worked somewhat on the server&client connection program. A much improved version is available here: http://ctypes-stuff.googlecode.com/svn/trunk/wince/remote-console/ The console.py script is thought to be run on the workstation. Editing the client.py script (which is transferred automatically to the PDA) is no longer needed. console.py accepts some command line options which can also be used for Python itself: -m 'package', -c 'Python commands', other options are accepted but don't do anything: -i, -u. Thomas ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] VensterCE release
[EMAIL PROTECTED] schrieb: > Hello Brian, > > Well, since I'm a student, I didn't really take into account > commercial use. I ideally thought that GPL gives a lot of freedom for > free or commercial development. > If it encouranges python ce users to choose venster as their gui > toolkit, in free or commercial products, I will release the upcoming > version under a MIT license. > > Anyway, have you tried venster-ce ? > I'll be glad to have comments or (constructive :-) criticism ! > > Alex. I have tried a version that I pulled from CVS (or was it SNV?) some days ago. I was quite impressed, although I had problems understanding the menus in french ;-). Thomas ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
[PythonCE] ctypes-1.0.1
I've released ctypes-1.0.1 (see the announcement on ctypes-users, for example). This is exactly the same version that is also bundled with Python 2.5, so I assume there's no need to build a separate windows-ce binary. Thomas ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
[PythonCE] Small buglet (?) in Python CE 2.4.3
Python 2.4.3 (#0, Apr 29 2006, 20:58:35) [MSC v.1201 32 bit (Unknown)] on
Pocket PC
(Remote Console on ('192.168.99.10', 20238))
PocketPC>>> cmp(buffer("abc"), buffer("def"))
\Temp\_script20238.py:1: RuntimeWarning: tp_compare didn't return -1, 0 or 1
-1
PocketPC>>>
Thanks,
Thomas
___
PythonCE mailing list
PythonCE@python.org
http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] py2exe
Luke Dunstan wrote: > - Original Message - > From: "Brad Clements" <[EMAIL PROTECTED]> > To: > Sent: Friday, June 02, 2006 7:58 AM > Subject: Re: [PythonCE] py2exe > > >> On 1 Jun 2006 at 20:59, ahmad adel rldardiry wrote: >> >>> Could this be done? A py2exe version for pocketpc, that generates an >>> executable that can run on Pocket PC? >> >> py2exe requires ctypes. I think there was some progress getting ctypes to >> work >> on Windows CE. No, py2exe does not require ctypes (AFAIK ;-). > Actually I ported ctypes months ago, and since then both Thomas Heller and I > have released ctypes binaries for versions of PythonCE. > >> >> However you'd still need a linker for ARM and pre-made DLLs, plus figure >> out if >> the .zip'd python scripts can be appended to a Windows CE executable >> (that's the >> trick py2exe uses to bundle everything up on X86 platforms) > > Yes, that may be the tricky part I think, but I have not looked into it. If that does not work or is not possible, one should still be able to build with a separate library.zip. Thomas ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] Running Python program without getting Python CE window
Ed Blake wrote: > --- "Michael Foord" <[EMAIL PROTECTED]> wrote: > >> You ought to check out Wax. It's a friendly Pythonic layer that sits >> atop of wx and IMHO is just as easy to use as Tkinter. > > Lol! I've been using/tinkering with firedrop for a few weeks now so I am > vaguely familier with wax. I don't really like the idea of using a largish > wrapper over the top of a huge library though, especially on a small embedded > device! Also wax is incomplete, and as I've said I don't know enough Wx to > fix/add stuff. I've lost the original email, butI hope this is still on topic: Now that ctypes works on WindowsCE, someone should revive the venster project! http://venster.sourceforge.net/htdocs/ Thomas ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] ceFile.py implementing basic file-like interface
> On Feb 14, 2006, at 14:06, Thomas Heller wrote: > >> I haven't taken a detailed look at the code, but it may be useful >> ;-). I'm currently hacking a little bit with distutils to integrate >> win CE support into the ctypes setup script so that it is easier to >> transfer the code to the pda. >> >> IMO modules like these should have an official place in CVS or SVN >> somewhere, so that they can be installed and used by others - >> standalone files that everyone installes in his own private >> directories isn't that useful. >> >> Since they are ctypes-based, the ctypes CVS repository on >> sourceforge would be a possible place, and a convenient one for me. >> Of course, other places could be good as well. What do you think? >> >> Thomas >> Shane Holloway (IEEE) wrote: > Yes, I saw your new ctypes version for CE. Very excited. > Unfortunately we are stuck in .NET land for a few near-term releases. > I just can't wait to switch over to using python on this platform. > Ctypes will certainly help us get there! > > As for common modules, I certainly agree that they need a common > place to live. I would expect them to be somewhere like the PythonCE > project on SourceForge or some other central area. I don't really > like the idea of multi-purposing the ctypes repository with CE stuff > for much the same reasons as I did not care for the comtypes being in > there. You may have heard that ctypes will be included in Python 2.5 (yay!). I think this will lead to a split between 'core ctypes' and ctypes based modules and packages (even if ctypes will further be maintained in the SF CVS repo). comtypes is such a package, and it is convenient for me to have it in the same repository. For ctypes itself, I want, and have already started, to extend the ctypes and comtypes setup scripts so that both packages can be build, transferred to the pda, and possibly even tested with some arguments to the setup script. What I need for that is a very limited subset of the rapi functionality, and this should certainly be in the ctypes CVS - even if it is ripped off some 'official' rapi module. > The RAPI interfaces are just one of the things I'd like to > see in this common repository, and I know everyone else has expressed > similar sentiments. We will really need a good .NET bridge for the > compact framework eventually. Hopefully we will be able to build > that atop ctypes -- but I'm starting to think we are going to need to > use a combination of OpenNETCF.org 2.0 Framework as well as the .NET > 2.0 CF to get things to approach what Zope has implemented for the > desktop. Anyhow I've started to ramble. ;) > > I really prefer SVN over CVS. ;) But I'm not too picky. We are > more than happy to host on TechGame -- our current structure is SVN > and Trac, and you can see an example at > http://techgame.net/projects/framework. But if we end up hosting > under ctypes or pythonce, I'll be just as happy. A place to start > working in is the important part. I'm a beginner with SVN but have used CVS for quite some years now, so I have no preference currently although I'm convinced SVN is better. I'm not opposed to hosting at techgame. Same for ctypes CVS, same for PythonCe, or whatever. I'll be happy to bring in my ctypes expertise to a rapi module, and that's it. Thomas ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] ceFile.py implementing basic file-like interface
Shane Holloway (IEEE) wrote: > Hey Everyone, > > Just thought I'd upload our latest RAPI code that implements a file like > object for reading and writing over RAPI. Hope you all find it > helpful! Currently, it doesn't support the readline and iterator type > thing, though that should be doable on top of this interface. Just > didn't have time to tackle that piece when I was writing it. > > Enjoy! > -Shane & Brian I haven't taken a detailed look at the code, but it may be useful ;-). I'm currently hacking a little bit with distutils to integrate win CE support into the ctypes setup script so that it is easier to transfer the code to the pda. IMO modules like these should have an official place in CVS or SVN somewhere, so that they can be installed and used by others - standalone files that everyone installes in his own private directories isn't that useful. Since they are ctypes-based, the ctypes CVS repository on sourceforge would be a possible place, and a convenient one for me. Of course, other places could be good as well. What do you think? Thomas ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] How do you develop on the PocketPC?
(Sorry for the late reply - sooo much to do ;-) "Luke Dunstan" <[EMAIL PROTECTED]> writes: > From: "Thomas Heller" <[EMAIL PROTECTED]> > >> We have three more or less complete and tested rapi modules. I have to >> admit that after reading it I like Luke's module better than the >> TechGame one, although I found at least one error in it (CeCreateProcess >> must take a pointer to PROCESS_INFORMATION). > > Note that PROCESS_INFORMATION contains an "_as_parameter_" property > that takes the address for you. I would agree to removing this though > because it may be more confusing than convenient. I totally forgot about the _as_parameter_ mechanism (even though it is documented in the tutorial). Problem with it is that it's not compatible with argtypes, iirc. >> We have the script that I posted which implements the start of a remote >> Python interpreter. I don't know what others think of it, but I find it >> pretty cool, it lets me try out code on the PDA without having to fiddle >> with this stick ;-). > > I forgot to mention it earlier but I am actually using your script most of > the time instead of the default PythonCE shell :-). Cool. >> How should we proceed? >> >> Create a development environment for CE, based on ctypes? > > I think everyone will have different ideas of what a "development > environment for CE" should be, and a wiki page is probably a good way to > collect the ideas. It would also be nice if an existing IDE or something > could be modified and extended to allow remote development for Windows CE, > because it would save a lot of time compared to creating it from scratch. > Off the top of my head I would like an IDE with the following features: > > - Remote interactive Python shell like the one you posted > - Source code editor with the usual features (to be elaborated later) > - Integrated remote debugger like winpdb > - GUI written in wxPython (this is just my preference and the reasons can be > discussed later) > - Preferably doesn't require manual installation of device-side components > apart from the standard PythonCE, i.e. it should install the rest > automatically > - Perhaps an integrated remote display function like ActiveSync Remote > Display or VNC, because this would be important for developing graphical > Python apps for Windows CE > > That should be enough to kick off discussion. Ok, here are my thoughts in this: I prefer xemacs as IDE, and normally do not use debuggers (ok, sometimes pdb from the console). I plan to extend the remote interactive shell to accept all parameters that python.exe takes, then it could be used edit the code script in xemacs, and execute it on the pda by hitting C-c C-c. I also have already extended the remote console to be configuration-free, the desktop's IP address is passed as parameter. Later, the device-side script can be transferred automatically from the desktop with rapi calls. But this shouldn't discourage you from the above ideas - sounds great anyway. >> Where should the repository be? > > I think it should be part of the PythonCE project on SourceForge because I > imagine it would appeal to most users and because I think it is too small to > require a separate project at this stage. > >> Who is interested in developing it? > > I am interested in working on it but I will be going on holiday soon for > around 3 weeks, so I won't be available immediately. >> Where should the repository be? >> >> > Brian Brown <[EMAIL PROTECTED]> writes: > We can host it, I can create a trac project at http:// > www.techgame.net/projects/ceDev or something > > Just let me know and I can set it up. It would have an svn repository. > > >> Who is interested in developing it? >> >> > > We can contribute to the development, so who else wants to get on board? So, it seems we have to decide whether the project should be hosted inside the PythonCE project on SF, or a trac project on techgame. And i seems Brian, Luke, and me would be interested as developers. Not a bad start, if you ask me. Thomas ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] How to edit registry on pocketpc to change how IE displays python files.
Fuzzyman <[EMAIL PROTECTED]> writes:
> Stewart Midwinter wrote:
>
>>David, there should be a script that edits the registry for you, and
>>it comes with a shortcut to help run it. Which version of PythonCE
>>did you install?
>>
>>
>>
>>
> It didn't work for me. The one supplied seem to need running on the PC
> (using cereg.exe) not the PocketPC - and it defines various *extra*
> entries as well. It didn't work for me yet anyway.
>
> I haven't yet taken the manual steps described to get it working. I was
> re-installing over a previous install.
Here is the script that I used (maybe it is from Luke):
#
# Setup the registry to allow us to double click on python scripts
#
from _winreg import *
print "Setting up registry to allow\ndouble clicking of Python files to work"
#
# Create the registry entries for ".py" and ".pyc" extensions
#
for Name in (".py", ".pyc"):
Key = CreateKey(HKEY_CLASSES_ROOT, Name)
SetValue(Key, None, REG_SZ, "Python.File")
CloseKey(Key)
#
# Create HKEY_CLASSES_ROOT\Python.File\Shell\Open\Command = "\Program
Files\Python\Python.exe" "%1"
#
Key = CreateKey(HKEY_CLASSES_ROOT, "Python.File")
for Name in ("Shell","Open","Command"):
New_Key= CreateKey(Key, Name)
CloseKey(Key)
Key = New_Key
SetValue(Key, None, REG_SZ, "\"\\Program Files\\Python\\Python.exe\" \"%1\"")
CloseKey(Key)
import time
time.sleep(5)
I did run it with 'execfile(r"\My Documents\Scripts\setup-registry.py")'
on the pocket PC itself, from within Python.
What I didn't achieve so far was to associate a useful icon with .py
files, maybe someone could post the registry entries for that?
Thomas
___
PythonCE mailing list
PythonCE@python.org
http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] How do you develop on the PocketPC?
We have three more or less complete and tested rapi modules. I have to admit that after reading it I like Luke's module better than the TechGame one, although I found at least one error in it (CeCreateProcess must take a pointer to PROCESS_INFORMATION). We have the script that I posted which implements the start of a remote Python interpreter. I don't know what others think of it, but I find it pretty cool, it lets me try out code on the PDA without having to fiddle with this stick ;-). How should we proceed? Create a development environment for CE, based on ctypes? Where should the repository be? Who is interested in developing it? And so on. For ctypes, wrapping the *complete* rapi functions would be an interesting experiment, also for automated code generation. Large enough to be interesting, small enough to be ready in limited time. Thomas ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] How do you develop on the PocketPC?
"Luke Dunstan" <[EMAIL PROTECTED]> writes: >>> From: "Thomas Heller" <[EMAIL PROTECTED]> >> >> Do you know of any other way except TCP/IP to establish a two-way >> communication between the desktop and the PDA? >> > One way I know is using the CeRapiInvoke() API, which is a kind of remote > procedure call: > > STDAPI_( HRESULT ) CeRapiInvoke( > LPCWSTR pDllPath, > LPCWSTR pFunctionName, > DWORD cbInput, > BYTE * pInput, > DWORD * pcbOutput, > BYTE ** ppOutput, > IRAPIStream ** ppIRAPIStream, > DWORD dwReserved > ); > > You can specify a DLL and function name and the device-side part of RAPI > will load the DLL and call the function, but it must have the following > prototype (see also wincerapi.py): > > typedef HRESULT (STDAPICALLTYPE RAPIEXT)( > DWORD cbInput, > BYTE * pInput, > DWORD * pcbOutput, > BYTE ** ppOutput, > IRAPIStream * pIRAPIStream > ); > > In block mode (ppIRAPIStream == NULL) you can simply pass a block of data in > each direction. The interesting part is that if you pass a pointer then you > will receive a IRAPIStream* that allows the device and PC to communicate in > both directions similar to a socket. > > I have tested this in one direction only using the CeInvoke sample from the > Pocket PC 2003 SDK, and I also tested replacing the desktop-side program > with a Python script. However, so far this API does not seem robust; for > example if the device-side DLL releases the stream then IRAPIStream::Read() > seems to block forever in the desktop program. The CeInvoke sample handles > this by sending a command over the stream to let the desktop know that it > has finished, but to my mind it is a hack because it would be like sending a > disconnect command over a TCP socket and relying on that to shut down the > other end. The function IRAPIStream::SetRapiStat can supposedly set a > timeout for Read() but so far I can't get it to work. There is a two-way > stream sample in an MSDN KB article that I have yet to try. > > For creating development tools there is also the possibility of using the > Platform Manager APIs, which are installed and used by eMbedded Visual C++ > to communicate with the remote debugger, among other things. Platform > Manager supports multiple "transports" including TCP/IP and ActiveSync and > you can even create your own transport. I haven't actually tried using it > yet though :-). This is useful info, I'm sure I need it when I have time;-) Thanks, Thomas ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] How do you develop on the PocketPC?
"Luke Dunstan" <[EMAIL PROTECTED]> writes: > - Original Message ----- > From: "Thomas Heller" <[EMAIL PROTECTED]> > To: > Sent: Monday, January 09, 2006 10:42 PM > Subject: Re: [PythonCE] How do you develop on the PocketPC? > > >> "Luke Dunstan" <[EMAIL PROTECTED]> writes: >> >>> I'm sorry to say that I've seen the NULL bug before but have been too >>> distracted by the task at hand to fix it, but here is a patch that >>> fixes it. >>> >>> 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. >> >> Thomas > > 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. Luke, Do you know of any other way except TCP/IP to establish a two-way communication between the desktop and the PDA? Thomas ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] How do you develop on the PocketPC?
" Luke Dunstan" <[EMAIL PROTECTED]> writes: > From: "Thomas Heller" <[EMAIL PROTECTED]> >> "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. I must say I didn't look at the module, but assumed that it wrapped a large amount of the rapi functions, so I wanted to avoid reinventing this particular wheel. Same for the license, I didn't look at it. If I were to commit these scripts somewhere, and add a ctypes-based rapi module, I would most certainly like to take responsibility for the rapi code anyway. Hopefully that would be a good thing, but in the version that I have there are only a couple of lines like this: ctypes.oledll.rapi.CeRapiInit() res = ctypes.windll.rapi.CeCreateProcess(unicode(REMOTE_EXE), unicode(REMOTE_CLIENT), None, None, False, 0, None, None, None, None) if res == 0: raise ctypes.WinError(ctypes.windll.rapi.CeRapiGetError() or \ ctypes.windll.rapi.CeGetLastError()) [...] try: [] finally: ctypes.oledll.rapi.CeRapiUninit() Not very reusable. To answer your question about 'argtypes' and 'restypes': Not setting argtypes may gain a little bt of speed, but the big advantage of using 'argtypes' would be the auto-string/unicode conversion that ctypes does (which is also missing in my own code). Sorry, Thomas ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] 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 ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] How do you develop on the PocketPC?
"Luke Dunstan" <[EMAIL PROTECTED]> writes: > I'm sorry to say that I've seen the NULL bug before but have been too > distracted by the task at hand to fix it, but here is a patch that > fixes it. > > 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. Thomas ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] How do you develop on the PocketPC?
"Luke Dunstan" <[EMAIL PROTECTED]> writes:
> I sometimes use interactive commands, but usually through a program called
> ActiveSync Remote Display which is like Remote Desktop.
Ok, I've downloaded the Windows Mobile Power toys. Maybe there's
something useful in it.
> Other times I do double-click on scripts, and it is possible (but
> inconvenient) to see the error messages by switching to the Python
> window.
Ah, I see. Could the error window be made smaller and moveable so that
one could move it around to see the actual traceback?
> I have been planning on creating some tools to help this process but
> maybe you've already done that?
>
> Your script would be appreciated.
I've attached it. There are two issues with it:
First, you have to set the PC's IP address in the client.py script.
For me, 127.0.0.1 did *not* seem to work.
Second, you must start the server.py script on the PC before starting
the client.py script on the pocket device. I was not able to start the
connection from the pocket device, although that would seem more logical.
Thomas
# Thomas Heller 20060109
# Run this on the Pocket_PC, *after* starting server.py on the PC
import sys, socket, code, time
try:
HOST = '192.168.0.236'# The remote host
PORT = 2 # The same port as used by the server
s = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
s.connect((HOST, PORT))
def readfunc(prompt=""):
if prompt:
sys.stderr.write(prompt)
try:
data = s.recv(1024)
except EOFError:
s.close()
sys.stderr._output.write(data[:-1])
sys.stderr._output.write("\n")
return data[:-1]
class Output(object):
def __init__(self, output):
self._output = output
def write(self, text):
self._output.write(text)
s.send(text)
sys.stdout = Output(sys.stdout)
sys.stderr = Output(sys.stderr)
##sys.ps1 = "Pocket_PC >>> "
##sys.ps2 = "Pocket_PC ... "
banner = "Python %s on %s\n(Remote Console)" % (sys.version, sys.platform)
# Replace the builtin raw_input (which doesn't work on CE anyway),
# to make pdb work.
import __builtin__
__builtin__.raw_input = readfunc
code.interact(banner=banner, readfunc=readfunc)
except SystemExit:
raise
except:
import traceback
traceback.print_exc()
time.sleep(5)
# Thomas Heller 20060109
# Start this script on the PC, then start client.py on the Pocket PC.
import socket, sys, threading
HOST = '' # Symbolic name meaning the local host
PORT = 2 # Arbitrary non-privileged port
s = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
s.bind((HOST, PORT))
s.listen(1)
conn, addr = s.accept()
def get_input():
while 1:
data = raw_input()
conn.send(data + '\n')
t = threading.Thread(target=get_input)
t.setDaemon(True)
t.start()
while 1:
data = conn.recv(1024)
if not data:
print "SystemExit, hit return to end."
raise SystemExit
sys.stderr.write(data)
___
PythonCE mailing list
PythonCE@python.org
http://mail.python.org/mailman/listinfo/pythonce
[PythonCE] How do you develop on the PocketPC?
Does anyone (everyone ?) start the Python interpreter on the device, and use the stylus to enter interactive commands? Or does one write scripts on the PC, let ActiveSync transfer them, and start them by clicking on the filename? I cannot really believe that. BTW, when an uncatched exception occurs in a script, I see a box displaying: """ Python Error Traceback (innermost last): : """ When I close this box (by clicking the OK button in the upper right corner), I can see (for less than a second) the interpreter window showing the real traceback, but not long enough to be able to read it. So, I made a pair of scripts which start a server on the host PC, which sends commands to a script running on the device, executing them, and send the results back for display on the PC. Don't know if it is worth to post it here... Thomas ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] Python 2.3.5 for Windows CE / ARM (Pocket PC 2003)
Andy Baker <[EMAIL PROTECTED]> writes: > Regarding the Win32 extensions... > > Is there a document that lists: > 1. What does work. > 2. What wont work because it's not relevant to WinCE > 3. What could work given some extra work > > I am particularly interesting in Win32.com.client which as I > understand it doesn't work. Could it potentially work? WinCE does have > COM as far as I know but I don't know what differences there are. I cannot answer these questions, but I'll try to get comtypes working. Are there 'interesting' COM objects on a Pocket PC 2003 to experiment with? Thanks, Thomas ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] Hello and some questions
Info4HiDeVis <[EMAIL PROTECTED]> writes: > my last question is for this maillinglist: some maillinglists are also > readable as news-group (for example: dzug.org) - is it for this > maillinglist possible too? this can make the reading and writing over > the mail-client more easier. Sure: see http://gmane.org Thomas ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] PythonCE on the ARM emulator
"Luke Dunstan" <[EMAIL PROTECTED]> writes: >>> I have tried the simple solution of disabling the version check and I >>> was able to install and run the ctypes unittests on the ARM emulator. >>> >>> Thomas: I can give you the build of Python that I used, if you want. >>> >> That would be great, although I really should be able to compile (and >> debug!) this myself. If I do this, I would want to quickly move from >> Python 2.3.4 to 2.4.2. Or is there any reason not to try this, on CE? >> >> Thomas > > Unfortunately I don't have an appropriate place my Python builds, so > could you suggest somewhere? Of course I eventually want it to become > part of the PythonCE project, so perhaps the developers of that > project would be kind enough to allow me to upload new builds, marked > as "alpha" or "snapshots" for now? If you want, I can add you as developer to the ctypes project. Then you can upload them to the ctypes files section (I assume these builds will also be of interest to other people, and they are related to ctypes as well). If you agree, send me your SF username by private mail. > I think moving to version 2.4.2 is a good idea but I doubt it will be > trivial and I think it will distract from the current task verifying > that my port of ctypes works as you expect. I think it is better to > focus on the working version of Python we have at the moment and > upgrade later. Is there any specific problem with using Python 2.3? No, except that I want to use decorators, if at all possible. But this can wait. Thomas ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] PythonCE on the ARM emulator
"Luke Dunstan" <[EMAIL PROTECTED]> writes: > I have tried the simple solution of disabling the version check and I > was able to install and run the ctypes unittests on the ARM emulator. > > > -- > Ran 269 tests in 168.000s > > OK > > Thomas: I can give you the build of Python that I used, if you want. > That would be great, although I really should be able to compile (and debug!) this myself. If I do this, I would want to quickly move from Python 2.3.4 to 2.4.2. Or is there any reason not to try this, on CE? Thomas ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] PythonCE on the ARM emulator
Michael Foord <[EMAIL PROTECTED]> writes: > Thomas Heller wrote: >> Since Luke Dunstan has ported ctypes to windows CE, so I got interested >> in this platform. I don't have a Windows CE device, but I found the MS >> Device Emulator (1.0, Community Preview): >> >> http://msdn.microsoft.com/mobility/windowsmobile/downloads/emulatorpreview/default.aspx >> >> To get started, I installed the emulator and tried to install the >> current CE binaries on it. The interactive interpreter works as far as >> I can tell, except that I cannot import any extension modules in it. >> When I try this, 'import _winreg' or 'import socket', Python is >> terminated without any indication what was wrong. >> >> Has anyone with more experience tried to run Python on this 'platform'? >> > > I can't download it. :-( I had the same problem initially. First, you need to use InternetExplorer. Second, you need to setup a passport account. Third, you need to disable any popup blockers, because the page does the download via an ActiveX control. > Shame - I'd like to play with it. I also missed any 'announcement' about > ctypes for PythonCE. Sounds good. Well, up to now it is just a patch on the sourceforge tracker. I'd like to try it out myself before integrating the patch and announcing a new version. Thomas ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
[PythonCE] PythonCE on the ARM emulator
Since Luke Dunstan has ported ctypes to windows CE, so I got interested in this platform. I don't have a Windows CE device, but I found the MS Device Emulator (1.0, Community Preview): http://msdn.microsoft.com/mobility/windowsmobile/downloads/emulatorpreview/default.aspx To get started, I installed the emulator and tried to install the current CE binaries on it. The interactive interpreter works as far as I can tell, except that I cannot import any extension modules in it. When I try this, 'import _winreg' or 'import socket', Python is terminated without any indication what was wrong. Has anyone with more experience tried to run Python on this 'platform'? Thanks, Thomas ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
