| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
| |
- Use final modifer wherever possible
- Use try-with-resources for input/output streams
Signed-off-by: Harsh Shandilya <harsh@prjkt.io>
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
I know we decided to ditch the idea of shutting up "Exception
thrown with empty param" warnings but this pesters me too
much and we can instead just treat this as a weird future proofing
thing if and when we end up needing the exception messages.
Signed-off-by: Harsh Shandilya <harsh@prjkt.io>
|
| |
|
|
|
|
| |
Signed-off-by: Samuel Holland <samuel@sholland.org>
|
|
|
|
|
|
| |
Address Java and Android lints.
Signed-off-by: Samuel Holland <samuel@sholland.org>
|
|
|
|
| |
Signed-off-by: Samuel Holland <samuel@sholland.org>
|
|
|
|
|
|
| |
Pretty straightforward, I was clearly overthinking this.
Signed-off-by: Harsh Shandilya <harsh@prjkt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is an activity, so it does not join the fragment backstack, but
instead piles on top
SettingsActivity
| -> MainActivity
| -> EditorFragment
| -> DetailFragment
| -> ListFragment
Without overriding the back button in the toolbar, it simply
kills the entire state on MainActivity and causes it to reload.
By calling finish() on the activity when home is pressed from the
item menu we can silently make it die without affecting any underlying
states held by MainActivity and instead return to the exact fragment
we launched settings from.
Signed-off-by: Harsh Shandilya <harsh@prjkt.io>
|
|
|
|
|
|
|
|
|
|
| |
AppCompat is the preferred way to go for any app targetting
a wider range of SDKs.
Replace all activities and fragments with their AppCompat
variants and fixup method calls to use support variants.
Signed-off-by: Harsh Shandilya <harsh@prjkt.io>
|
| |
|
| |
|
|
|
|
| |
Signed-off-by: Samuel Holland <samuel@sholland.org>
|
|
|
|
|
|
| |
It is no longer used.
Signed-off-by: Samuel Holland <samuel@sholland.org>
|
|
Signed-off-by: Samuel Holland <samuel@sholland.org>
|