Re: [PythonCE] Python CE on a Intel XScale industrial device.
2008/8/5, Alexandre Delattre <[EMAIL PROTECTED]>: > > Now... Do I need the Tkinter pack to use ppygui? I did not find any > > reference to that, and I am eager to trim down the Python > > distribution. > > No, ppygui has no external dependence besides PythonCE and the system dlls > that comes out of the box on wince devices. A byte-code only distribution of > ppygui is around 250 kB. That is nice to know. Since these devices rarely have much available space wasting 2 MB on TCL is not something I'm looking forward to. With tinkering I can have up to 80 MB of available disk space, but I'd like to keep it low-size. > > Hmm... I wonder if I could be converted into a Python Head. > > You mean a python egg ? No :). I meant Myself (from Java Head into a Python Head). Although this was a nice shot :) > Also, I remember from the time I played with evc++ that PythonCE is > targeted for armv4 processors. From what I read XScale is armv5 but is > supposed to be backward compatible with armv4. This is what I read around the network. > Maybe the .cab installer check the processor type id without taking into > account backward-compatibility stuff ? I agree. This seems a most-likely reason. > I think you don't have to hurry on recompilation yet if you're able to make > work what you need for your project. Also I'm afraid only Visual Studio 2005 > allow to compile for armv5, in case you really want to recompile something > optimized for your architecture. Actually I would want the opposite: a VM that would work on many devices rather than a VM that would work on only one type of device a bit better. Pardon the terminology, I still look at the Python frame through my Java experience. We are targeting a Client-Server architecture, where the server does most of the job, and the client is used as a 'Screen and Keyboard Terminal' without putting much resource pressure on it. I was actually wondering if there is a way to build a new CAB file with only the Processor Type changed (no re-compilation). However I lack the tools to do so. > Alexandre P.S. I will be off the subject for a while. I need to focus back to the server side. My device was also put to real use, and I will have no test bed for a week or so. ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] Python CE on a Intel XScale industrial device.
> Success! > After manually copying the ...\ppygui-0.7\ppygui\*.py to a newly > created $PYTHONHOME\Lib\site-packages\ppygui the demo application > started (pretty damn fast!) and displayed correctly (as far as I > know). Glad to here that works :) > Now... Do I need the Tkinter pack to use ppygui? I did not find any > reference to that, and I am eager to trim down the Python > distribution. No, ppygui has no external dependence besides PythonCE and the system dlls that comes out of the box on wince devices. A byte-code only distribution of ppygui is around 250 kB. > I'll be having problems creating a distribution pack for > installing on the devices we'll be using. These days I've been working on a script that helps producing easily .cab for pythonce applications and libraries. Hopefully I'll polish and publish it in the week. > Hmm... I wonder if I could be converted into a Python Head. You mean a python egg ? Also, I remember from the time I played with evc++ that PythonCE is targeted for armv4 processors. From what I read XScale is armv5 but is supposed to be backward compatible with armv4. Maybe the .cab installer check the processor type id without taking into account backward-compatibility stuff ? I think you don't have to hurry on recompilation yet if you're able to make work what you need for your project. Also I'm afraid only Visual Studio 2005 allow to compile for armv5, in case you really want to recompile something optimized for your architecture. Alexandre ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] Python CE on a Intel XScale industrial device.
2008/8/4, Alexandre Delattre > > Any pointers on the ppygui installation issue? > The traceback points to the Html control module, which is not the most > essential, however, as the installer relies on this control you'll have to > proceed to manual installation, i.e. copy ppygui package from the archive to > \Program Files\Python25\Lib > > Then you have to edit ppygui/api.py and comment out the line: > from html import * > > Then try to run the demo.py file which does not use the html control, and > see if it works. Success! After manually copying the ...\ppygui-0.7\ppygui\*.py to a newly created $PYTHONHOME\Lib\site-packages\ppygui the demo application started (pretty damn fast!) and displayed correctly (as far as I know). Now... Do I need the Tkinter pack to use ppygui? I did not find any reference to that, and I am eager to trim down the Python distribution. I'll be having problems creating a distribution pack for installing on the devices we'll be using. Hmm... I wonder if I could be converted into a Python Head. ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] Python CE on a Intel XScale industrial device.
I understand what you mean, but I am more worried about the subtle differences in processors (like the MMX vs SSE in X86). These differences do not surface early, but when requested. I still remember 'those times' where a program would run correctly for some time, until one tries floating point operations and would crash badly. I thought of running the Python regression tests, but I don't think those are available for Python CE, and I was unable to complete the tests on a test Desktop machine (some weird unstoppable exception is some *chat* test case). I am afraid I can not volunteer to build the CAB files myself. I am a bit scared to ask, but can't 'we' use SourceForge's farms to set up a continuous build system? I can not volunteer for that task either, because I am not a SourceForge (project) developer. You ask if I was able to install anything... I '''installed''' Mozilla's Minimo browser, but it has no Processor Type specified, and on top of that it would not run afterwards: the .exe files have no icon, and 'This is not a CE program' error shows when I try to run any of them. I have not seen any available CAB files for XScale, that I could test with. BTW. The Minimo project seems to have been archived and dropped. I don't like where Mozilla is going :-/ (I actively dislike Firefox 3.0). 2008/8/4, Alexandre Delattre <[EMAIL PROTECTED]>: > Hi, > > What I meant is that if you can run python.exe without crashing, it seems > obvious to me that this code is compatible with your processor (else the > .exe would refuse to start, or you would have very strange results and won't > be able to enter a single command). > To me, the processor seems not to be the real backend problem, but you may > be right about the processor type specified in the cab preventing the > installation. > Are you able to install other PocketPC applications from .cab ? > > > Alexandre... > > Who is 'we' who should rebuild the CABs? > > Good question ... I'd really like to do that but I don't have much time > right now (plenty of other projects and stuff to do...) and need to have > evc++4.0 working on my computer (f*ckin windows vista ...). > If someone is willing to take that up, I'll be glad to give directions. > > > Any pointers on the ppygui installation issue? > The traceback points to the Html control module, which is not the most > essential, however, as the installer relies on this control you'll have to > proceed to manual installation, i.e. copy ppygui package from the archive to > \Program Files\Python25\Lib > > Then you have to edit ppygui/api.py and comment out the line: > from html import * > > Then try to run the demo.py file which does not use the html control, and > see if it works. > > Alexandre. > ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] Python CE on a Intel XScale industrial device.
Hi, What I meant is that if you can run python.exe without crashing, it seems obvious to me that this code is compatible with your processor (else the .exe would refuse to start, or you would have very strange results and won't be able to enter a single command). To me, the processor seems not to be the real backend problem, but you may be right about the processor type specified in the cab preventing the installation. Are you able to install other PocketPC applications from .cab ? > Alexandre... > Who is 'we' who should rebuild the CABs? Good question ... I'd really like to do that but I don't have much time right now (plenty of other projects and stuff to do...) and need to have evc++4.0 working on my computer (f*ckin windows vista ...). If someone is willing to take that up, I'll be glad to give directions. > Any pointers on the ppygui installation issue? The traceback points to the Html control module, which is not the most essential, however, as the installer relies on this control you'll have to proceed to manual installation, i.e. copy ppygui package from the archive to \Program Files\Python25\Lib Then you have to edit ppygui/api.py and comment out the line: from html import * Then try to run the demo.py file which does not use the html control, and see if it works. Alexandre. ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] Python CE on a Intel XScale industrial device.
More updates. Thanks to Alexandre I was able to start Python with Tkinter, however I was a bit disappointed by the hardness of the installation procedure, and the unexpected dependancy on the TCL Toolkit. No matter. I extracted the .CAB file with a Windows utility called MSCEInf.exe. I copied the files to the device using a (W)LAN. I then copied the celib.dll and the TCL/TK libraries (a very tedious procedure). I was able to successfully create a Tkinter Frame with a label inside. I was also able to run the provided Tkinter._test(). Trying to install the ppygui however was no success at all. A few seconds after starting install.py I got: > Traceback (innermost last): > File "\Temp\ppygui-0.7\install.py", line 5, in > import ppygui as gui > File "\Temp\ppygui-0.7\ppygui\__init__.py", line 1, in > from api import * > File "\Temp\ppygui-0.7\ppygui\api.py", line 29, in > from html import * > File "\Temp\ppygui-0.7\ppygui\html.py", line 101, in > _InitHTMLControl() > File "\Temp\ppygui-0.7\ppygui\html.py", line 99, in _InitHTMLControl > cdll.htmlview.InitHTMLControl(GetModuleHandle(0)) > File > "C:\devl\release\PythonCE-2.5-20061219\Python-2.5-wince\Lib\ctypes\__init__.py", > line 387, in __getattr__ > File > "C:\devl\release\PythonCE-2.5-20061219\Python-2.5-wince\Lib\ctypes\__init__.py", > line 312, in __init__ > : [Error 87] Windows Error 0x7E Which baffled me completely (I am quite new to this stuff). However inspired by this minor success I used a set of tools for Linux: 1. I extracted the CAB file with cabextract. 2. I used hexer to edit the *.000 file and replace the supported processor from 0x0A11 at position 20 with 0x0920 (which is the XScale processors' cpu id). 3. I used lcab to 'try' and recreate the CAB with the updated files. Well... At first the installer no longer bugged me with '... can not run on this device...'. It actually started copying files. However for all the .dll and .exe files the installer said: 'File ... was not copied.' (or something similar). It also told me I need to get the CAB file from the source location again. The result was not very good. I canceled the installation half-way through (too many pop-ups). The 'Program Files\Python25' had a number of files and directories similar to what I got when I extracted the cab with the Windows tool. However all the .dll and .exe files had zero length. Surprisingly a lot of .pyd files were there with a positive length. I did not get to the registration process, so I have not checked the .py .pyc and .pyw associations. The un-installation also did no go as expected, leaving most files inside the device. However I believe that this shows, that the processor type IS the issue with the installer. Alexandre... Who is 'we' who should rebuild the CABs? Any pointers on the ppygui installation issue? 2008/7/31 Alexandre Delattre <[EMAIL PROTECTED]>: > Hi, > > In my opinion if you're able to run the python exe it means that is not > processor related. > > I think the problem comes from what you've pointed out, the OS versions > constraints. > > I think we should rebuild the .cab to allow os versions from 4.00 and 5.99 as > you suggested. There's also a bug in the cab that would be worth fixing at > the same time: > > In one of the registry key that associates .pyw to pythonce without shell we > have to replace \nopcceshell by /nopcceshell. > > Else this cause the error : to be raised when running .pyw. > > For tKinter, the dll are not shipped with PythonCE and you have to copy them > manually, more info on the wiki. > > For ppygui I'll be very glad if you use my toolkit, and if you send me your > traceback I'll make my possible to make it work for you. > I think the issue you described comes from that ppygui was designed for > PocketPC 2003 and Windows Mobile, while it seems from screenshot your device > has the 'classic' wince interface. > > Regards, > Alexandre > > > - Message d'origine - > De: Lachezar Dobrev <[EMAIL PROTECTED]> > Env: jeudi 31 juillet 2008 17:05 > À: Alexandre Delattre <[EMAIL PROTECTED]> > Objet: Re: [PythonCE] Python CE on a Intel XScale industrial device. > > Update follows... > > People on this list were quite helpful in referencing a couple of > tools for Pocket PC CAB file mangling. > 1. I was able to extract the Python CE CAB file an uploaded the > extracted files to my device. The python executable had an icon, and I > was able to run it. It seemed to work. I was able to execute a few > minor tests my way: a few dir()-s, a few imports,
Re: [PythonCE] Python CE on a Intel XScale industrial device.
Hi, In my opinion if you're able to run the python exe it means that is not processor related. I think the problem comes from what you've pointed out, the OS versions constraints. I think we should rebuild the .cab to allow os versions from 4.00 and 5.99 as you suggested. There's also a bug in the cab that would be worth fixing at the same time: In one of the registry key that associates .pyw to pythonce without shell we have to replace \nopcceshell by /nopcceshell. Else this cause the error : to be raised when running .pyw. For tKinter, the dll are not shipped with PythonCE and you have to copy them manually, more info on the wiki. For ppygui I'll be very glad if you use my toolkit, and if you send me your traceback I'll make my possible to make it work for you. I think the issue you described comes from that ppygui was designed for PocketPC 2003 and Windows Mobile, while it seems from screenshot your device has the 'classic' wince interface. Regards, Alexandre - Message d'origine - De: Lachezar Dobrev <[EMAIL PROTECTED]> Env: jeudi 31 juillet 2008 17:05 À: Alexandre Delattre <[EMAIL PROTECTED]> Objet: Re: [PythonCE] Python CE on a Intel XScale industrial device. Update follows... People on this list were quite helpful in referencing a couple of tools for Pocket PC CAB file mangling. 1. I was able to extract the Python CE CAB file an uploaded the extracted files to my device. The python executable had an icon, and I was able to run it. It seemed to work. I was able to execute a few minor tests my way: a few dir()-s, a few imports, a few Base64 encoding and decoding operations, and it seemed to work fine. Until I tried to import Tkinter: > >>> import sys > >>> import Tkinter > Traceback (most recent call last): > File > "C:\devl\release\PythonCE-2.5-20061219\Python-2.5-wince\Lib\lib-tk\Tkinter.py", > line 38, in > RuntimeError: Could not find CeLib DLL > >>> Which led me to believe something is not right. Has anyone seen that? Does anyone know how to fix that? A similar error occurs when I try to install the PocketPyGui (ppygui-0.7) which I thought I would use for the GUI part. However the exception then has a bit longer stack trace (about 10 frames). 2. Reading the documentation on the pocketpc-cab and lcab utilities I found something that rang a bell: Appendix A: a list of processor architectures ... 1824 - ARM 720 2080 - ARM 820 2336 - ARM 920 2577 - StrongARM ... My device says in the System Properties: 'Intel, ARM920T-PXA27x' Could this be the culprit of my problems? Is ARM920 compatible with Strong ARM? Should I give-up on trying to install the current version and try to compile a version for my device personally? I also noted that the CAB files state, that the allowed OS version is 4.00 up to 5.00, shouldn't it be up to 5.99 or something? Not that my device has Windows 5.1 or anything, but I saw a the Smart Phone version note a MAX OS Version of 5.99... I hope I get more feed-back on the subject. I feel I am getting closer, but I am neither a Mobile-Device expert, nor a Python expert. I am fairly new to this stuff. ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] Python CE on a Intel XScale industrial device.
Hi, Lachezar. I recall having the exact same message. I cannot remember which application I was using/trying to install at the time. The problem was easily fixed by obtaining a celib.dll and putting it into the Windows folder on my device. I believe you will find lots of posts about this. Adam. 2008/7/31 Lachezar Dobrev <[EMAIL PROTECTED]> > Update follows... > > People on this list were quite helpful in referencing a couple of > tools for Pocket PC CAB file mangling. > 1. I was able to extract the Python CE CAB file an uploaded the > extracted files to my device. The python executable had an icon, and I > was able to run it. It seemed to work. I was able to execute a few > minor tests my way: a few dir()-s, a few imports, a few Base64 > encoding and decoding operations, and it seemed to work fine. Until I > tried to import Tkinter: > > > >>> import sys > > >>> import Tkinter > > Traceback (most recent call last): > > File > "C:\devl\release\PythonCE-2.5-20061219\Python-2.5-wince\Lib\lib-tk\Tkinter.py", > line 38, in > > RuntimeError: Could not find CeLib DLL > > >>> > > Which led me to believe something is not right. > Has anyone seen that? Does anyone know how to fix that? > > A similar error occurs when I try to install the PocketPyGui > (ppygui-0.7) which I thought I would use for the GUI part. However the > exception then has a bit longer stack trace (about 10 frames). > > 2. Reading the documentation on the pocketpc-cab and lcab utilities > I found something that rang a bell: > >Appendix A: a list of processor architectures >... >1824 - ARM 720 >2080 - ARM 820 >2336 - ARM 920 >2577 - StrongARM >... > >My device says in the System Properties: 'Intel, ARM920T-PXA27x' >Could this be the culprit of my problems? Is ARM920 compatible > with Strong ARM? Should I give-up on trying to install the current > version and try to compile a version for my device personally? > > I also noted that the CAB files state, that the allowed OS version > is 4.00 up to 5.00, shouldn't it be up to 5.99 or something? Not that > my device has Windows 5.1 or anything, but I saw a the Smart Phone > version note a MAX OS Version of 5.99... > > I hope I get more feed-back on the subject. > I feel I am getting closer, but I am neither a Mobile-Device expert, > nor a Python expert. I am fairly new to this stuff. > ___ > PythonCE mailing list > PythonCE@python.org > http://mail.python.org/mailman/listinfo/pythonce > ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] Python CE on a Intel XScale industrial device.
Update follows... People on this list were quite helpful in referencing a couple of tools for Pocket PC CAB file mangling. 1. I was able to extract the Python CE CAB file an uploaded the extracted files to my device. The python executable had an icon, and I was able to run it. It seemed to work. I was able to execute a few minor tests my way: a few dir()-s, a few imports, a few Base64 encoding and decoding operations, and it seemed to work fine. Until I tried to import Tkinter: > >>> import sys > >>> import Tkinter > Traceback (most recent call last): > File > "C:\devl\release\PythonCE-2.5-20061219\Python-2.5-wince\Lib\lib-tk\Tkinter.py", > line 38, in > RuntimeError: Could not find CeLib DLL > >>> Which led me to believe something is not right. Has anyone seen that? Does anyone know how to fix that? A similar error occurs when I try to install the PocketPyGui (ppygui-0.7) which I thought I would use for the GUI part. However the exception then has a bit longer stack trace (about 10 frames). 2. Reading the documentation on the pocketpc-cab and lcab utilities I found something that rang a bell: Appendix A: a list of processor architectures ... 1824 - ARM 720 2080 - ARM 820 2336 - ARM 920 2577 - StrongARM ... My device says in the System Properties: 'Intel, ARM920T-PXA27x' Could this be the culprit of my problems? Is ARM920 compatible with Strong ARM? Should I give-up on trying to install the current version and try to compile a version for my device personally? I also noted that the CAB files state, that the allowed OS version is 4.00 up to 5.00, shouldn't it be up to 5.99 or something? Not that my device has Windows 5.1 or anything, but I saw a the Smart Phone version note a MAX OS Version of 5.99... I hope I get more feed-back on the subject. I feel I am getting closer, but I am neither a Mobile-Device expert, nor a Python expert. I am fairly new to this stuff. ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] Python CE on a Intel XScale industrial device.
Hello, I'm doubting the problem comes from the processor type, as you were able to run the Python 2.2 port which is also compiled for arm. Unfortunately CeGCC support only arm platform yet (the two cross-compilation targets available are arm-wince-cegcc and arm-wince-mingw32) so I'm afraid it wouldn't be of any help if arm code wasn't compatible with xscale processor (which I'm doubting). I'm suspecting more there is another constraint specified in the .inf file used to create the PythonCE cab that prevent installing on your device, but I don't see now what it could be exactly. I suggest you to try to make a "hand-made" install by copying the \Program Files\Python 25\ dir from another install to your device and see if you could run python.exe. Hope it helps, Alexandre ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] Python CE on a Intel XScale industrial device.
The confusion about activesync is that if the program had been compiled for multiple architectures then the processor specific cabs would all be inside the exe installer and activesync would select the appropriate one for the particular device. It sounds like you're going to need to figure out a way to compile for the Xscale without the use of Visual Studio. As Jared suggested in another thread, try http://cegcc.sourceforge.net/ or maybe http://www.ronetix.at/software.html I'm not sure on the difference between ARM and XScale but maybe VS left out something your specific devices need that isn't on other devices. Alex Lachezar Dobrev wrote: Well... First thanks for the Active Sync explanation. Reading the mailing list archives I was left with the impression, that Active Sync was actually translating the application for the architecture of the connected device. So I found a friend, tricked him into installing Active Sync, and trying to install the .EXE distribution files. Both the ARM and the SmartPhone versions failed to install with a similar message. Another thing I am not grasping is the difference between ARM, StrongARM and XScale. Probably wrong, but I thought XScale was backwards compatible with the ARM processors, however a quick tour around the Wikipedia hints otherwise... Pardon my bluntness, but until recently I had Java on every platform I had in mind... Can someone compile a Python version for an XScale processor? How does this work? Do I need a Windows host? Is the Python CE compilable with a GNU toolkit set? Like I've said Windows based development is a No-No for us. 2008/7/28, Jared Forsyth <[EMAIL PROTECTED]>: Firstly, the Active Sync method merely automates the copy .CAB/install process--you're not missing out in anything. The only problem I can thing of is that of your processor: your device runs XSale, while I believe the .CABs are compiled for ARM ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] Python CE on a Intel XScale industrial device.
One more word on the ASync - you are right that it does modify certain files when they are transfered, but not all. I have not tested this properly, but I believe that AS will recognise certain files (especially media) and convert them to work on within the limitations of the PPC device (e.g. lower resolution, etc...). I believe there are a number of options as far as cross-compiling from Linux to a WinCE target. I have used PellesC (with Wine), but I am also investigating the use of ceGCC (on Jared's advice). I think ceGCC will be more likely to work for XScale targets. Cross-compiling would avoid the need to have a Windows host. Adam 2008/7/28 Lachezar Dobrev <[EMAIL PROTECTED]> > Well... > > First thanks for the Active Sync explanation. Reading the mailing > list archives I was left with the impression, that Active Sync was > actually translating the application for the architecture of the > connected device. > So I found a friend, tricked him into installing Active Sync, and > trying to install the .EXE distribution files. Both the ARM and the > SmartPhone versions failed to install with a similar message. > > Another thing I am not grasping is the difference between ARM, > StrongARM and XScale. Probably wrong, but I thought XScale was > backwards compatible with the ARM processors, however a quick tour > around the Wikipedia hints otherwise... > > Pardon my bluntness, but until recently I had Java on every platform > I had in mind... > Can someone compile a Python version for an XScale processor? How > does this work? Do I need a Windows host? Is the Python CE compilable > with a GNU toolkit set? > > Like I've said Windows based development is a No-No for us. > > 2008/7/28, Jared Forsyth <[EMAIL PROTECTED]>: > > Firstly, the Active Sync method merely automates the copy .CAB/install > > process--you're not missing out in anything. > > The only problem I can thing of is that of your processor: your device > runs > > XSale, while I believe the .CABs are compiled for ARM > ___ > PythonCE mailing list > PythonCE@python.org > http://mail.python.org/mailman/listinfo/pythonce > ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] Python CE on a Intel XScale industrial device.
Hi, Lachezar. I would agree with Jared. Not having used any XScale devices, I do not have what you might call hard evidence, but a quick Google for ARM and XScale lead me to the MSDN website, which seems to confirm that compiling for XScale is a specific target (and would therefore suggest that ARM compiled packages may not work). My iPAQ uses WM5 v5.1.1702 and happily runs PythonCE 2.5. One other thought is to try to update your operating system on the XScale device as much as possible and then re-try the PythonCE install package (maybe there are some compatibility settings you can enable/disable in the OS?). Adam 2008/7/28 Jared Forsyth <[EMAIL PROTECTED]> > Firstly, the Active Sync method merely automates the copy .CAB/install > process--you're not missing out in anything. > The only problem I can thing of is that of your processor: your device runs > XSale, while I believe the .CABs are compiled for ARM > > > On Mon, Jul 28, 2008 at 4:27 AM, Lachezar Dobrev <[EMAIL PROTECTED]>wrote: > >> * Apologies for the resending, the first message did not go through. * >> >> Hello list members. >> Recently our project (Java based) grew into the mobile devices range. >> However the devices had a serious flaw (for us): the Windows CE >> operating system. >> For some time we were able to develop based in the Pocket IE >> available on the device and use an AJAX+Server-Side approach to do our >> work. >> >> Recently we hit some use cases where this approach would not work, >> or would need serious development in order to provide the needed >> interaction requirements. >> >> We could not find a Java VM to suit our needs, and development using >> Microsoft's development frame is a No-No for us. >> >> That is why I undertook the challenge to evaluate Python based >> development. >> >> Here I took my first blow... The files on the SourceForge site did >> not install on the device. >> The device is: http://www.mobilecompia.co.kr/en/sub01/sub01_1.php >> It features Windows CE 5.0 on an Intel XScale PXA processor with a >> number of crucial features for our application (WLAN, WWAN, Barcode >> scanner). >> >> Since we are working with Linux/BSD workstations I was unable to try >> the Active Sync method, and was forced to download the CAB files, >> however when trying to install the application I get a 'Setup Failed' >> message: >> >> > The application cannot run on this device type. >> > Please install the application specific to this device type. >> >> This is with both CAB files: >> PythonCE-25-20061219.PPC2003_ARM.CAB >> and >> PythonCE.WM.CAB >> >> I tried also the 'Pocket PC Python' from >> http://www.murkworks.com/Research/Python/PocketPCPython/Overview >> That WORKS! But since it's Python 2.2 the GUI toolkits refuse to >> work (no annotations?). >> >> Can you please advise further? >> ___ >> PythonCE mailing list >> PythonCE@python.org >> http://mail.python.org/mailman/listinfo/pythonce >> > > > ___ > PythonCE mailing list > PythonCE@python.org > http://mail.python.org/mailman/listinfo/pythonce > > ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] Python CE on a Intel XScale industrial device.
Well... First thanks for the Active Sync explanation. Reading the mailing list archives I was left with the impression, that Active Sync was actually translating the application for the architecture of the connected device. So I found a friend, tricked him into installing Active Sync, and trying to install the .EXE distribution files. Both the ARM and the SmartPhone versions failed to install with a similar message. Another thing I am not grasping is the difference between ARM, StrongARM and XScale. Probably wrong, but I thought XScale was backwards compatible with the ARM processors, however a quick tour around the Wikipedia hints otherwise... Pardon my bluntness, but until recently I had Java on every platform I had in mind... Can someone compile a Python version for an XScale processor? How does this work? Do I need a Windows host? Is the Python CE compilable with a GNU toolkit set? Like I've said Windows based development is a No-No for us. 2008/7/28, Jared Forsyth <[EMAIL PROTECTED]>: > Firstly, the Active Sync method merely automates the copy .CAB/install > process--you're not missing out in anything. > The only problem I can thing of is that of your processor: your device runs > XSale, while I believe the .CABs are compiled for ARM ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] Python CE on a Intel XScale industrial device.
Firstly, the Active Sync method merely automates the copy .CAB/install process--you're not missing out in anything. The only problem I can thing of is that of your processor: your device runs XSale, while I believe the .CABs are compiled for ARM On Mon, Jul 28, 2008 at 4:27 AM, Lachezar Dobrev <[EMAIL PROTECTED]> wrote: > * Apologies for the resending, the first message did not go through. * > > Hello list members. > Recently our project (Java based) grew into the mobile devices range. > However the devices had a serious flaw (for us): the Windows CE > operating system. > For some time we were able to develop based in the Pocket IE > available on the device and use an AJAX+Server-Side approach to do our > work. > > Recently we hit some use cases where this approach would not work, > or would need serious development in order to provide the needed > interaction requirements. > > We could not find a Java VM to suit our needs, and development using > Microsoft's development frame is a No-No for us. > > That is why I undertook the challenge to evaluate Python based > development. > > Here I took my first blow... The files on the SourceForge site did > not install on the device. > The device is: http://www.mobilecompia.co.kr/en/sub01/sub01_1.php > It features Windows CE 5.0 on an Intel XScale PXA processor with a > number of crucial features for our application (WLAN, WWAN, Barcode > scanner). > > Since we are working with Linux/BSD workstations I was unable to try > the Active Sync method, and was forced to download the CAB files, > however when trying to install the application I get a 'Setup Failed' > message: > > > The application cannot run on this device type. > > Please install the application specific to this device type. > > This is with both CAB files: > PythonCE-25-20061219.PPC2003_ARM.CAB > and > PythonCE.WM.CAB > > I tried also the 'Pocket PC Python' from > http://www.murkworks.com/Research/Python/PocketPCPython/Overview > That WORKS! But since it's Python 2.2 the GUI toolkits refuse to > work (no annotations?). > > Can you please advise further? > ___ > PythonCE mailing list > PythonCE@python.org > http://mail.python.org/mailman/listinfo/pythonce > ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
[PythonCE] Python CE on a Intel XScale industrial device.
* Apologies for the resending, the first message did not go through. * Hello list members. Recently our project (Java based) grew into the mobile devices range. However the devices had a serious flaw (for us): the Windows CE operating system. For some time we were able to develop based in the Pocket IE available on the device and use an AJAX+Server-Side approach to do our work. Recently we hit some use cases where this approach would not work, or would need serious development in order to provide the needed interaction requirements. We could not find a Java VM to suit our needs, and development using Microsoft's development frame is a No-No for us. That is why I undertook the challenge to evaluate Python based development. Here I took my first blow... The files on the SourceForge site did not install on the device. The device is: http://www.mobilecompia.co.kr/en/sub01/sub01_1.php It features Windows CE 5.0 on an Intel XScale PXA processor with a number of crucial features for our application (WLAN, WWAN, Barcode scanner). Since we are working with Linux/BSD workstations I was unable to try the Active Sync method, and was forced to download the CAB files, however when trying to install the application I get a 'Setup Failed' message: > The application cannot run on this device type. > Please install the application specific to this device type. This is with both CAB files: PythonCE-25-20061219.PPC2003_ARM.CAB and PythonCE.WM.CAB I tried also the 'Pocket PC Python' from http://www.murkworks.com/Research/Python/PocketPCPython/Overview That WORKS! But since it's Python 2.2 the GUI toolkits refuse to work (no annotations?). Can you please advise further? ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
[PythonCE] Python CE on a Intel XScale industrial device.
Hello list members. Recently our project (Java based) grew into the mobile devices range. However the devices had a serious flaw (for us): the Windows CE operating system. For some time we were able to develop based in the Pocket IE available on the device and use an AJAX+Server-Side approach to do our work. Recently we hit some use cases where this approach would not work, or would need serious development in order to provide the needed interaction requirements. We could not find a Java VM to suit our needs, and development using Microsoft's development frame is a No-No for us. That is why I undertook the challenge to evaluate Python based development. Here I took my first blow... The files on the SourceForge site did not install on the device. The device is: http://www.mobilecompia.co.kr/en/sub01/sub01_1.php It features Windows CE 5.0 on an Intel XScale PXA processor with a number of crucial features for our application (WLAN, WWAN, Barcode scanner). Since we are working with Linux/BSD workstations I was unable to try the Active Sync method, and was forced to download the CAB files, however when trying to install the application I get a 'Setup Failed' message: > The application cannot run on this device type. > Please install the application specific to this device type. This is with both CAB files: PythonCE-25-20061219.PPC2003_ARM.CAB and PythonCE.WM.CAB I tried also the 'Pocket PC Python' from http://www.murkworks.com/Research/Python/PocketPCPython/Overview That WORKS! But since it's Python 2.2 the GUI toolkits refuse to work (no annotations?). Can you please advise further? ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
