[maemo-developers] non-Hildonized v Hildonized Python app
From: Rabson, Hugo SPC MIL USA USARPAC hugo.rabson at us.army.milDate: Fri Dec 26 00:46:01 EET 2008
- Previous message: Init scripts after low-battery shutdown
- Next message: non-Hildonized v Hildonized Python app
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi, Aside from a prettier GUI and Nokia-specific connectivity, what do I lose if I don't Hildonize a Python (PyGtk) app? I'm porting an app to Windows and Linux. So far, Python w/ Gtk+Glade suits my needs best. It must remain a cross-platform app (one codebase, one embedded database, three executables residing on one directory on one removable disk). I am trying to find a way to keep the codebase as non-system-specific as possible. If I start Hildonizing the code, I think I'll have to either write a one-way automatic Hildonizer or somehow split the code into modules (one Hildonized, one non-Hildonized). The program is very GUI-oriented, so I'm really tempted not to Hildonize it at all and see if that's good enough. So, I guess my questions are:- 1. Is there a way to automatically Hildonize an app? 2. If not, is there an easy way to keep two codebases (one Hildonized, one non-Hildonized) in a Python app? 3, Failing that, what do I lose by not Hildonizing the Python app at all (at least, not in the GUI)? Thanks for your time. Happy Holidays & all that. -Hugo
- Previous message: Init scripts after low-battery shutdown
- Next message: non-Hildonized v Hildonized Python app
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]