Connecting geeks

wxPython running on Maemo

January 20th, 2006

I just managed to run succesfully wxPython on Maemo, the development environment for Nokia 770.

I downloaded the sources, and followed these instructions, with two minor exceptions:

I used these configure options for wxWidgets:


../configure --without-opengl --disable-debug --enable-sound --with-gtk --enable-unicode

and these options for setup.py for wxPython:


python2.3 setup.py build_ext --inplace UNICODE=1 BUILD_GLCANVAS=0 BUILD_STC=0 BUILD_GIZMOS=0 BUILD_ANIMATE=0

This is the look and feel of wxPython running on Maemo

The look and feel is still a bit ugly, because I did not make any change to the original code. I will try to hildonize wxWidgets. I hope it won’t be too dificult.

10 Comments Add your own

1. Alejandro Rivero | January 22nd, 2006 at 11:22 pm

Fine thing! Have you already noted it somewhere in the Maemo Wiki? Perhaps in a How to, or in the list of ported applications.
2. herraiz | January 23rd, 2006 at 5:27 am

Not yet. I only compiled wxWidgets and wxPython on Maemo, but without changes over the original code. The look and feel is not yet hildon-like, so I will try to improve the look and feel and then I will add it to the Maemo wiki.
3. Connecting geeks » &hellip | February 3rd, 2006 at 12:20 pm

[…] My last try did not manage to get a proper look and feel in the Maemo environment. I copied the files from /usr/share/themes from my Nokia 770 to the scratchbox environment on my computer (just click here if you are wondering what the hell is a scratchbox), and added this to .gtkrc-2.0 to my home directory […]
4. Chris | February 21st, 2006 at 4:00 pm

I’m curious about memory issues. wxPython takes a fair bit of memory (34MB for a simple app on my linux box), which looks to be in short supply on the 770. Part of this is due to the extra layer of wxWidgets on top of GTK, in additon to the Python bindings.

For this reason, I had expected that PyGTK may be the only usable option for Python GUI development on the 770. I’m so glad you’ve proved me wrong!
5. herraiz | February 22nd, 2006 at 5:37 am

Yes, I am afraid you are right. But even only PyGTK is consuming a lot of memory. For example, I was developing a email client with PyGTK, and it ran perfectly on my computer inside the scratchbox. But when I tried it on my Nokia 770 it was slow as you can’t imagine.
6. Khertan | August 7th, 2007 at 7:13 am

Hi,

I’ve just read that you ve developped an email client in PyGTK. Does it include an offline imap and is it available somewhere ?

Thanks
7. herraiz | August 18th, 2007 at 12:32 am

I started to develop it, but I never finished it. It worked awfully anyway.

I recommend you to try claws-mail iinstead.
8. stan one | September 13th, 2007 at 8:33 am

Where’s the .deb or working binary,
trying to compile it for the N800 and its failing.

did you happen to pack it up when you compiled it.?
9. stan one | September 13th, 2007 at 8:33 am

Where’s the .deb or working binary,
trying to compile it for the N800 and its failing.

did you happen to pack it up when you compiled it.?
10. Peter | October 2nd, 2007 at 1:45 pm

wxPython 2.8.6.0 seems to run okay.

Here is a summary of how I got it working in scratchbox:

Set up scratchbox and get it working per the tutorial
Create a file named .gtkrc-2.0 in your scratchbox home directory with the following line:
include ‘/usr/share/themes/default/gtk-2.0/gtkrc’

Install the python2.5 package from the maemo repository (right now only the ARM packages will install)
Download the wxPython 2.8.6.0 source code archive and extract it
create a bld directory inside of the directory
cd into it

../configure –without-opengl –disable-debug –enable-sound –with-gtk –enable-unicode
make
make install

cd into the wxPython subdirectory
python2.5 setup.py build_ext –inplace UNICODE=1 BUILD_GLCANVAS=0 BUILD_STC=0 BUILD_GIZMOS=0
python2.5 setup.py install UNICODE=1 BUILD_GLCANVAS=0 BUILD_STC=0 BUILD_GIZMOS=0

cd into
/samples/simple
run-standalone.sh python2.5 ./simple.py

A lot of the demos will run too, though with a lot of them you get a message about a _stc python module that is missing. I haven’t looked into it.