kinda agree on that, but i don't think we can deal with multiple different platforms with one codebase (monkeypatching those will be ugly, like REALLY ugly in my sense). cmiiw though since i don't really involved with multiplatform software development before....Bigpet wrote:
I'm currently exploring to maybe making a platform shim, so that opsu! can be more easily ported to other platforms (because, lets be honest, there's no one single framework that can truly handle all platforms with reasonable trade-offs).
Slick patches probably because of recent skin select implementation (vs single selection on previous) and changes on hit lighting and scores (300,100,50,miss)Bigpet wrote:
Anyway during that exploration I saw that a bunch of the Slick2D files seem to be patched, is there a brief explanation as to what was changed?
(I know that I can always just do a diff, but asking doesn't hurt and I can do other things in the meantime )
Gradle build... well not a big issue for me but i actually quite love Maven because i can do shading (put all .jars in one .jar file).Bigpet wrote:
Also it seems to me that using Gradle as a build system is lot easier for the purposes of creating multiple versions and swapping out parts of the source on different platforms. But I'll worry about that a lot later when it becomes relevant, I just want to test the waters on how attached you are to Maven as the build system .
not quite sure if Gradle can do the same or not
but if GStreamer build is coming, that will be a bad news for opsu-android since i don't think there's a Android build for that...