TESTING- Quality/ Dependency checks prior to initial APK build

[chrisdebian]

Nick did a really good job of forking an experimental branch of MapThePaths, so we could use it as a starting point for MOROW.

Not having the skills to do any new coding, yet; I installed a couple of tools and ran some tests on the forked code. I've tried to fix some of the code issues identified by Android Studio and IntelliJ IDEA. These are mostly automated checks that can be run using built-in tools. They include things like SDK and Gradle versions. Some things were picked up that aren't issues, but maybe something to look at in the future, if/ when we refactor.

I wasn't confident in committing the auto-suggested 'quick fixes', so seek support from anyone that feels able to look at the code and make any changes that are needed. This will then put us in a good place to build an APK.

Any one fancy having a look?

Cheers,

Chris.

[nickw1]

@chrisdebian I could have a look, again time permitting, but would be good to get some other contributors on board too.

One thing to bear in mind is that the OS library will be completely replaced so any issues referred to in there, or in code using it, can probably be ignored.

[chrisdebian]

Hi, Nick.

Completely agree about contributors. I was hoping that by announcing an APK, to build on, that would help.

Remember, just because you wrote the code, you don't have to maintain it. As you say, we'll need to get some 'developer' skill onboard.

Cheers,

Chris.