[PyKDE] Sharp Zaurus support
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. Is the Zaurus version of PyQt based on Qt 3.x or on one of the Qt 2.x series? 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? From reading the Qtopia info on trolltech, it appears that Qt Embedded should support all the functionality of the main Qt library, but I still don't see anywhere explaining what version QtE is based on... Thanks for any info. Greg ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] Sharp Zaurus support
On Thursday 12 December 2002 3:08 pm, Greg Fortune wrote: 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. Is the Zaurus version of PyQt based on Qt 3.x or on one of the Qt 2.x series? 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? From reading the Qtopia info on trolltech, it appears that Qt Embedded should support all the functionality of the main Qt library, but I still don't see anywhere explaining what version QtE is based on... Thanks for any info. The version of Qt is 2.3.3. However, a hardware vendor can fine tune the configuration any number of ways. The following is a list of disabled features on the Zaurus... QT_NO_CODECS QT_NO_COLORDIALOG QT_NO_DIAL QT_NO_DOM QT_NO_DRAGANDDROP QT_NO_IMAGE_TEXT QT_NO_INPUTDIALOG QT_NO_FILEDIALOG QT_NO_FONTDIALOG QT_NO_MIMECLIPBOARD QT_NO_NETWORKPROTOCOL QT_NO_PICTURE QT_NO_PRINTDIALOG QT_NO_PRINTER QT_NO_PROGRESSDIALOG QT_NO_PROPERTIES QT_NO_SEMIMODAL QT_NO_SIZEGRIP QT_NO_SPLITTER QT_NO_STYLE_CDE QT_NO_STYLE_INTERLACE QT_NO_STYLE_MOTIF QT_NO_STYLE_MOTIFPLUS QT_NO_STYLE_PLATINUM QT_NO_STYLE_SGI QT_NO_TRANSFORMATIONS QT_NO_WIZARD QT_NO_WORKSPACE QT_NO_THREAD_SUPPORT The only way to know how the detail of how each of these affects Qt is to look at the source - but most refer to whole classes so it's not too difficult to work out. Phil ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] Sharp Zaurus support
Greg Fortune [EMAIL PROTECTED] writes: 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. Is the Zaurus version of PyQt based on Qt 3.x or on one of the Qt 2.x series? Is the The Zaurus has Qt/Embedded 2.3.2, with some limits on functionality. PyQt being just a wrapper around Qt, it doesn't lift those restrictions. I don't know if there is a list of restrictions somewhere. Here are the ones I discovered while porting code: - The QSplitter object does not exist. - QColor doesn't take string arguments, you have to specify a colour by RGB or use one of the predefined color objects. Another incompatibility I discovered is that QWidget.setBackgroundColor has no effect, at least for a plain widget. You have to paint the background yourself. All these are limitations due to Qt, so they apply no matter what tools you use for Zaurus programming. I haven't run into anything limitation due to Python or PyQt yet. It's rather the opposite: it is much easier to work with Python on the Zaurus as you can modify the code right on the Zaurus without having to worry about compilation. In fact, I developed substantial parts of code on the train. And speed is perfectly sufficient if you don't do number crunching. In summary, Python+PyQt is the best handheld programming system I have seen until now. Of course, as a longtime Python fan I might be biased ;-) Konrad. ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] Sharp Zaurus support
On Thursday 12 December 2002 3:48 pm, Greg Fortune wrote: The version of Qt is 2.3.3. However, a hardware vendor can fine tune the configuration any number of ways. The following is a list of disabled features on the Zaurus... Bummer, but that's exactly what I needed to know. QT_NO_CODECS QT_NO_COLORDIALOG QT_NO_DIAL QT_NO_DOM QT_NO_DRAGANDDROP QT_NO_IMAGE_TEXT QT_NO_INPUTDIALOG QT_NO_FILEDIALOG QT_NO_FONTDIALOG QT_NO_MIMECLIPBOARD QT_NO_NETWORKPROTOCOL QT_NO_PICTURE QT_NO_PRINTDIALOG QT_NO_PRINTER QT_NO_PROGRESSDIALOG QT_NO_PROPERTIES QT_NO_SEMIMODAL QT_NO_SIZEGRIP QT_NO_SPLITTER QT_NO_STYLE_CDE QT_NO_STYLE_INTERLACE QT_NO_STYLE_MOTIF QT_NO_STYLE_MOTIFPLUS QT_NO_STYLE_PLATINUM QT_NO_STYLE_SGI QT_NO_TRANSFORMATIONS QT_NO_WIZARD QT_NO_WORKSPACE QT_NO_THREAD_SUPPORT I assume I could recompile Qtopia to re-enable any of these features I need, right? You are confusing Qt/Embedded with Qtopia. I don't know if you can compile your own Qt/Embedded as it would require knowledge of the Zaurus hardware. Phil ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] Sharp Zaurus support
Am Don, 2002-12-12 um 16.48 schrieb Greg Fortune: I assume I could recompile Qtopia to re-enable any of these features I need, right? You can recompile Qt/Embedded with less disabled features, however you will lose binary compatibility with stock Zaurii, of course. If you really really need a missing feature then it would be better to refactor this feature into a seperate library and enhance the PyQt build process to support this. If you want to go this way, let's join forces - I'd be interested. Cheers, -- :M: -- Dipl.-Inf. Michael 'Mickey' Lauer [EMAIL PROTECTED] Raum 10b - ++49 69 798 28358 Fachbereich Informatik und Biologie -- ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] Sharp Zaurus support
On Thursday 12 December 2002 10:50 am, Michael Lauer wrote: Am Don, 2002-12-12 um 19.45 schrieb Greg Fortune: snip I assume I could recompile Qtopia to re-enable any of these features I need, right? You are confusing Qt/Embedded with Qtopia. I don't know if you can compile your own Qt/Embedded as it would require knowledge of the Zaurus hardware. Perhaps Sharp provides something like a makefile for their platform. Luckily this is not needed. Qt/Embedded comes with all the necessary configurations. Simply configure Qt/Embedded with ./configure -xplatform linux-sharp-g++ and you're set. Note that you need a cross compilation environment. Cool :) Now all I need to do is spring the $430 for a Zaurus and a wireless card and I'm good to go. I just wish the price would drop a little. I'm about to give up and just order one :) Thanks for the help, Greg ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] Sharp Zaurus support
Greg Fortune wrote: [snip] Cool :) Now all I need to do is spring the $430 for a Zaurus and a wireless card and I'm good to go. I just wish the price would drop a little. I'm about to give up and just order one :) Thanks for the help, Greg Greg, keep an eye on http://froogle.google.com/froogle?q=sharp+zaurusprice1=price2=375price=betweenbtnP=Go and http://froogle.google.com/froogle?q=cf+wirelessprice1=price2=70price=betweenbtnP=Go -- Tom Jenkins Development InfoStructure http://www.devis.com ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
