[maemo-developers] non-Hildonized v Hildonized Python app
From: Martin Grimme martin.grimme at gmail.comDate: Fri Dec 26 02:06:07 EET 2008
- Previous message: non-Hildonized v Hildonized Python app
- Next message: non-Hildonized v Hildonized Python app
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi, 2008/12/25, Rabson, Hugo SPC MIL USA USARPAC <hugo.rabson at us.army.mil>: > Aside from a prettier GUI and Nokia-specific connectivity, what do I > lose if I don't Hildonize a Python (PyGtk) app? Apart from what you've mentioned, you don't lose much else, really. Maybe you'll lose a few potential users, though. > 1. Is there a way to automatically Hildonize an app? Not really. It's usually a major UI redesign to make it fit well on the small screen. With small, I don't mean the resolution, but the physical size. > 2. If not, is there an easy way to keep two codebases (one Hildonized, > one non-Hildonized) in a Python app? The main differences are HildonWindow vs GtkWindow and the application menus. You could abstract from the implementations with a wrapper class and load the appropriate implementation for the platform. You can detect if you're running on hildon with: try: import hildon except: HAVE_HILDON = False else: HAVE_HILDON = True There are other ways for detecting, too. But this is what I prefer. > 3, Failing that, what do I lose by not Hildonizing the Python app at all > (at least, not in the GUI)? See above. > Thanks for your time. Happy Holidays & all that. Happy holidays to you, too! Regards, Martin
- Previous message: non-Hildonized v Hildonized Python app
- Next message: non-Hildonized v Hildonized Python app
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]