Tile replacement work hasn't even started for the GBA. I'm not going to focus on that until I reimplement GB tile replacement and finish what work I started for GBC tile replacement. Currently the plan is 1) to integrate code from the old project into the new one for GB/GBC emulation then 2) write a Qt GUI, 3) go back and work on tile replacement for GB/GBC games then 4) do a 0.1 release.
GBA tile replacement is going to be much more complicated than either the GB/GBC. Given that computing hashes even on a simple game like Kirby's Dreamland could slowdown emulation on my 3.8GHz i5-2500K, GBA work is going to be a monster. I'm thinking of using multi-threading to alleviate some of the hashing stress across multiple cores. It'd be optional but beneficial, and there's no reason not to add it in this day and age.
GBA tile replacement is going to be much more complicated than either the GB/GBC. Given that computing hashes even on a simple game like Kirby's Dreamland could slowdown emulation on my 3.8GHz i5-2500K, GBA work is going to be a monster. I'm thinking of using multi-threading to alleviate some of the hashing stress across multiple cores. It'd be optional but beneficial, and there's no reason not to add it in this day and age.