I am officially announcing my intention to create an Android TI-68k emulator, to be based off of TIEmu 3.03 -gdb, found here: http://sourceforge.net/projects/gtktiemu/files/tiemu-linux/TIEmu%203.03/tiemu-3.03-nogdb.tar.gz/download
At this point I'm just calling it Android TIEmu, or maybe ATIE for short, although when the project is actually ready for release we ("we" being everyone who contributes) will probably come up with something better.
This is basically a port of the PC/Linux TIEmu, and is intended to look, feel, and act as close to that program as possible, although there will obviously be some major differences, considering the medium it will live in, i.e. Android devices, as well as the unfortunate necessity of having to rewrite the C source of TIEmu into Java for the Android app.
Obviously the most important thing is that the app is capable of successfully running TI-89(T), TI-92(+), and Voyage-200 ROMs, and having an as-close-as-possible-to-the-real-thing UI, but the other features of TIEmu, such as file transfer, macro recording, etc., are also desired as well.
At this point, seeing as how I've only barely started, exactly three things are done:
The original C code for TIEmu has been downloaded.
The absolutely horrible TIEmulator app, which inspired me to do this, has been mostly decompiled. (The purpose of this is to have a reference point when making ATIE, in case we need some kind of clue on how to do a certain bit. There is no intention of stealing any of the actual code itself- mainly because it really sucks. )
An Eclipse project for the app has been created.
At some point I intend to create a git repo on Google Code, once I figure out how.
I would love help. Any kind. Programmers and testers especially.
In order to test, of course, you need at least one Android device. I personally have a Sanyo Zio phone, running AOS 2.2, and a Toshiba Thrive tablet, running AOS 3.1, so those two devices will obviously be getting tested on. However, the larger the variety of devices we have to test with, the better, for somewhat obvious reasons.
Oh, and for anyone curious about the awful Android app I was referring to, here's a link to it's page on the Android Market: https://market.android.com/details?id=com.TIEmulator
Ugly, isn't it?
Update: I'm pretty sure I successfully made the GIT repo: http://code.google.com/p/android-ti-emu/
At this point I'm just calling it Android TIEmu, or maybe ATIE for short, although when the project is actually ready for release we ("we" being everyone who contributes) will probably come up with something better.
This is basically a port of the PC/Linux TIEmu, and is intended to look, feel, and act as close to that program as possible, although there will obviously be some major differences, considering the medium it will live in, i.e. Android devices, as well as the unfortunate necessity of having to rewrite the C source of TIEmu into Java for the Android app.
Obviously the most important thing is that the app is capable of successfully running TI-89(T), TI-92(+), and Voyage-200 ROMs, and having an as-close-as-possible-to-the-real-thing UI, but the other features of TIEmu, such as file transfer, macro recording, etc., are also desired as well.
At this point, seeing as how I've only barely started, exactly three things are done:
The original C code for TIEmu has been downloaded.
The absolutely horrible TIEmulator app, which inspired me to do this, has been mostly decompiled. (The purpose of this is to have a reference point when making ATIE, in case we need some kind of clue on how to do a certain bit. There is no intention of stealing any of the actual code itself- mainly because it really sucks. )
An Eclipse project for the app has been created.
At some point I intend to create a git repo on Google Code, once I figure out how.
I would love help. Any kind. Programmers and testers especially.
In order to test, of course, you need at least one Android device. I personally have a Sanyo Zio phone, running AOS 2.2, and a Toshiba Thrive tablet, running AOS 3.1, so those two devices will obviously be getting tested on. However, the larger the variety of devices we have to test with, the better, for somewhat obvious reasons.
Oh, and for anyone curious about the awful Android app I was referring to, here's a link to it's page on the Android Market: https://market.android.com/details?id=com.TIEmulator
Ugly, isn't it?
Update: I'm pretty sure I successfully made the GIT repo: http://code.google.com/p/android-ti-emu/