Ok, I think you finally realize that
it's not going to be "just a recompile" to get APRSISCE/32 to run
under Android. Android is not Win32, WINE is not on Android.
Android may be based on *nix, but it is a completely different GUI
Saying that they're all graphical environments, so there must be
similarities is like saying that since English, Spanish,
Portuguese, German, and Mandarin Chinese are all spoken languages,
there must be similarities in them. That may be true, but it
doesn't really make it any easier to learn another one if you know
one. Or worse, to translate a book written in English to German
if you don't know German.
APRSISCE/32 is written in C and directly invokes the native Win32
API on both Windows desktops and Windows Mobile. Android
development is done in Java with some provision for linking in
some C computation (but not User Interface) code. And Android
has it's own GUI calls. Yes, APRSISCE/32 is currently in English
and Android requires German and I don't speak German (yet).
I'll make the same offer I made before. If you really, really,
REALLY want me to port APRSISCE/32 to Android, then I'll be glad
to take a 1 year sabbatical from my day job to learn the required
skills and platform, port the code, debug the new implementation,
and release APRSIS/droid (or whatever it ends up being called). I
estimate this to be about (US) $150,000.00 and you'll have the
program in your hot little Android devices approximately 1 year
from when the (cashier's) check clears the bank.
Any takers? I didn't think so. So let's please drop the Android
discussion or take it over to the cafe. It has nothing to do with
supporting the current APRSISCE/32 application on Windows Mobile
and desktop devices.
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and
PS. Just for historical clarity: APRSISCE/32 is written in C and
uses the Win32 API and runs on the Windows Mobile platform for one
and only one reason. I KNOW C, been coding it for years. I KNOW
Win32, been coding it for slightly less time (OS/2 was before
that). And I OWN a Windows Mobile device and have done Windows
Mobile coding professionally. You are all freely reaping the
benefits of that experience. The only learning curve I had was
the APRS protocol, and as other APRS authors can attest, that was