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
> 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 ppyg
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
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
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
om 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
C 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]&g
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.
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 w
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
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
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
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 AR
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
tr
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 <[E
* 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 i
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 approa
17 matches
Mail list logo
