>But for me the failure of python to get foothold in xPhones and xPads as strong as on desktops across all major Intel OS including Linux (with GUI library...) turned me away from >Dabo: portability not only across windows desktop machines but Mac and Linux as well is not good enough after the "personal device" gets redefined to describe a touch-based >small device - Dabo would only slightly increase possible reach to those desktops NOT running windows compared to vfp and still miss out the pad/phone market. Any changes >done in that area in Dabo?

Python does run on Android and I understand also iOS. But in general I believe you are correct it's not going well for python on mobile devices. There is kivy but I believe it still is best suited for a touch screen desktop. As far as Dabo - it looks doubtful. If someone takes the time to include QT as lib for Dabo then the mobile market might change over night. That said - for the work I do I don't see mobile phone being a reasonable tool for the clients. Tablets might work if voice really works as an input method without access to web being a requirement.

I have been playing with Android tablets to provide data input without much success. Trying to create a sales order is not easy on a tablet. Then there is the off line issues and trying to sync the data (Yes there are lot's of areas without cell support). We have played with both native apps and web apps both seem to be full of compromises when compared to a small laptop like an Apple Air. We have printing issues (mostly solved with email). Then there is the training which did not go well either (an older gent).

In the cities the cell works but most of the time it's not 4G so the speed is slow. Also using the blue tooth keyboards eat battery life. All of the above have in general stopped me from offering a tablet solution.

One shining item was support was easy. When the cell connection worked all the normal tools worked.

Johnf