Sorry for the huge diff, but all I did was applying Android Studio's 'Reformat Code' to all files. If everyone does that before submitting a patch we can keep it clean easily.
Details
- Reviewers
mtijink - Group Reviewers
KDE Connect - Commits
- R225:60049dab2a08: Apply coding style to whole project
R225:fa5a37c47264: Apply coding style to whole project
Compiles
Diff Detail
- Repository
- R225 KDE Connect - Android application
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
This brings up a good question that I have been meaning to ask for awhile: Are the coding guidelines for this project (KDE Connect) published anywhere?
Asking everyone to run Android Studio's code formatter is probably a good idea, but relies on everyone using the same settings... And getting developers to agree on code style is harder than herding cats :)
At a minimum, the C++ on the Desktop side and the Android on the mobile side are sometimes different. Of course, other than communicating with each other, they are fairly independent, so maybe having their code styles be different is not a big deal.
I think there is a general consensus about C++/Qt coding style in KDE, but I'm not aware of any for Java/Android code. I'm using default settings in Android Studio.
I didn't read through all this, but it seems fine and still works.
I think quickly applying this (and your other related diffs) is best, because it *will* be causing some merge conflicts for the other outstanding diffs.