Hello fellow /prog/grammers. I come with a question that I hope you will be able to answer or give me advice. If not then at least make the troll posts obvious so that I don't waste time learning something useless.
I want a PC-98 emulator, for Android. I want to be able to play touhou(the first 5 games) on the go. The thing is that even the emulator that exist for PC aren't that many and I think only one works good.
I currently only know Visual basic(a little since I learned it like 6 years ago and haven't used it in the 5 years after) and a little of python(learning it through google's online course).
The question is, can I make an emulator with that knowledge or is another language(other than python that is) better for the task? And which?
Learn how to design programs.
Learn how to use the android sdk.
Use any language, it doesn't matter.
If it's slow, consider profiling your emulator, learning the android ndk, and then replacing slow code.
Name:
L4TE2012-01-21 11:55
>>2 The PC-98 is different from the IBM PC in many ways; for instance, it uses its own 16 bit C-Bus instead of the ISA bus; BIOS, I/O port addressing, memory management, and graphics output are also different. However, localized MS-DOS or Windows will still run on PC-9801s.
But: The Android SDK provides the tools and APIs necessary to begin developing applications on the Android platform using the Java programming language.
Name:
Anonymous2012-01-21 13:43
If you want to wrote for Android, you have to use Java. This is what has held me back.
Name:
Anonymous2012-01-21 14:06
If I write a VM using Java will that be like using a VM inside a VM inside a VM?
most people just find it frustrating, but people coming from a scripting background find java difficult, probably because of the transition from flexible and terse syntax to verbose and strict. And you have to get used to the idea of structuring everything inside of classes, which is new to someone who has only written scripts, but that type of organization is common practice in most languages.
Name:
Anonymous2012-01-21 14:24
>>8
the good thing is that you have a project in mind, it easier to learn something to archive something else, that to learn something just for the sake of it.
Name:
Anonymous2012-01-21 14:58
>>4 I don't know if that will work...
It shouldn't be a problem, Dosbox already supports a lot of different hardware set-ups. For the BIOS I'm pretty sure it's a difference of less than ten interrupts.
Name:
Anonymous2012-01-21 15:22
>>5
There's always the Android NDK, but that will limit the portability and compatibility. (Android fragmentation in full effect yo.)
Name:
L4TE2012-01-21 15:48
>>12 >>3 The NDK allows you to implement parts of your applications using native-code languages such as C and C++.
Does "native code" mean any language I please? Because the only languages they mantion are C and C++.
:/
Name:
Anonymous2012-01-21 16:01
>>13
Trolling or retarded? "Native code" means it compiles into native machine code instead of using the virtual machine.
Name:
Anonymous2012-01-21 16:43
>>14
Excuse me do you know how to read?
Maybe you missed the part where I explain that I don't know much about programing?
Suck my dick, dude.
Name:
Anonymous2012-01-21 17:13
>>15
If you're that unable of finding out things for yourself you'll never know much about programming either.
Name:
Anonymous2012-01-21 17:30
lol
you need to be good in Java mate
pick up a book and learn it until you master it
then you move on to Android API
Name:
Anonymous2012-01-21 17:31
>>16 Mind telling us how you found out what native code was? If it involved at least one other person, then you are a hypocrite.
Name:
Anonymous2012-01-21 17:37
>>18
Not by asking stupid shit like a complete fucktard.
>>5,12
Android run a modified Java VM, named Dalvik. So it's expected that most code which runs in a regular JVM can be converted to Dalvik's .dex class files.
Also, Android have this SL4A, which allow development in various scripting languages, Python included.
For the native counterpart, the NDK provides a cross-compiler and some libraries. Can't you download gcc sources and make your own for the same arm targets, and then link with android ndk's gcc?
Anyways, from what I've gathered in this thread, this is what I'll need to do:
learn Java make a PC-98 emulator that works on PC(or find one that does and is GLP'd) learn android SDK port emulator to android using SDK if it's slow or doesnt work right learn ndk somehow use ndk to make emulator port work
Is that ok or should I make some adjustments to the proposed workflow?
The Android NDK is a companion tool to the Android SDK that lets you build performance-critical portions of your apps in native code. It provides headers and libraries that allow you to build activities, handle user input, use hardware sensors, access application resources, and more, when programming in C or C++. If you write native code, your applications are still packaged into an .apk file and they still run inside of a virtual machine on the device. The fundamental Android application model does not change.
Association Of British Insurers
American Bankruptcy Institute
ankle-brachial index
a phoenix demon in the form of a human who makes her debut in the episode titled: The Fiery Bird Master, Princess Abi (episode 146) and is present in most of the episodes up until the episode titled: The Demon Linked with the Netherworld (episode 154) where she and her mother Tekkei are slain by Naraku.
American Biographical Institute
>>62
Hey, I'm not exporting anything, I'm just sending bits to another machine in the same country as me! What that machine does with those bits is out of my hands!