[PyKDE] Sharp Zaurus support

Michael Lauer mickey at tm.informatik.uni-frankfurt.de
Thu Dec 12 16:42:01 GMT 2002


Hi Greg,


> I'm considering putting together a PyQt based app for the Sharp Zaurus and 
> would like to know what kind of success people have had.

Great success. We have a very large PyQt application on the Sharp Zaurus
and despite some minor issues its working really good.

>  Is the Zaurus 
> version of PyQt based on Qt 3.x or on one of the Qt 2.x series? 

Qt/E 2.3.x

> Is the 
> Zaurus version trimmed down in any way or do I get all the features that I 
> would have available to a desktop app?

The Zaurus (as is the iPAQ) build of Qt/Embedded is a stripped down
build, several features as following are missing:

#define QT_NO_CODECS
#define QT_NO_UNICODETABLES
#define QT_NO_IMAGEIO_PPM
#define QT_NO_FREETYPE
#define QT_NO_BDF
#define QT_NO_DRAGANDDROP
#define QT_NO_PROPERTIES
#define QT_NO_NETWORKPROTOCOL
#define QT_NO_IMAGE_TEXT
#define QT_NO_COLORNAMES
#define QT_NO_TRANSFORMATIONS
#define QT_NO_TRANSLATION_BUILDER
#define QT_NO_COMPLEXTEXT
#define QT_NO_PRINTER
#define QT_NO_PICTURE
#define QT_NO_DIAL
#define QT_NO_SIZEGRIP
#define QT_NO_WORKSPACE
#define QT_NO_STYLE_POCKETPC
#define QT_NO_STYLE_MOTIF
#define QT_NO_STYLE_PLATINUM
#define QT_NO_FILEDIALOG
#define QT_NO_FONTDIALOG
#define QT_NO_PRINTDIALOG
#define QT_NO_COLORDIALOG
#define QT_NO_INPUTDIALOG
#define QT_NO_PROGRESSDIALOG
#define QT_NO_WIZARD
#define QT_NO_EFFECTS
#define QT_NO_DOM
#define QT_NO_SEMIMODAL
#define QT_NO_SPLITTER
#define QT_NO_QWS_BEOS_WM_STYLE
#define QT_NO_QWS_KDE2_WM_STYLE

Yours,
-- 
:M:
--------------------------------------------------------------------------
Dipl.-Inf. Michael 'Mickey' Lauer  
mickey at tm.informatik.uni-frankfurt.de 
  Raum 10b - ++49 69 798 28358       Fachbereich Informatik und Biologie
--------------------------------------------------------------------------




More information about the PyQt mailing list