Improve how the status of messages is indicated.
Remove the Toast that always says 'Message Sent' and show graphical
indicators instead that show either:
* message is waiting to be sent
* message was sent (or requested to be sent)
* message was delivered
Please note that I didn't change the icons and did not migrate the UI to XML files to keep my change minimally invasive.
Closes#46
See merge request !9
Remove the Toast that always says 'Message Sent' and show graphical
indicators instead that show either:
* message is waiting to be sent
* message was sent (or requested)
* message was delivered
40 forgotten password
* Moved the UI definition over to XML and added the forgotten password button
* Code encapsulation in a new Base activity also enabling re-use between activities/fragments
Closes#40
See merge request !10
Don't mix JUnit 4's @Test with JUnit3's TestCase.
This is the world's most boring merge request. Android Studio was complaining about using JUnit 4's @Test annotations with JUnit 3's TestCase, so I fixed it.
Most of the changes come from Android Studio organising imports in a different order from Eclipse.
See merge request !8
Create hidden service in a subdirectory. #161
The permissions for the parent directory are too permissive (775) for Tor 0.2.7.5. Store the hidden service hostname and private key in a subdirectory with permissions 700.
See merge request !5
Touching startup failure notification now shows details
The text of the startup failure notification is unhelpful due to lack of
space. Touching the notification now launches an activity that gives details
of the problem and what can be done about it.
Closes#38
See merge request !7
Build with SDK 23, continue to target SDK 22. #162
This will allow people to download Android Studio, check out and build the project without extra steps. Compiling with the latest SDK is recommended even if your target is older (as ours is).
See merge request !6
The text of the startup failure notification is unhelpful due to lack of
space. Touching the notification now launches an activity that gives details
of the problem and what can be done about it.
Closes#38
Hide password strength meter when confirming password
Closes#100
I opted to hide the strength meter because:
* more extensive changes would have been required to set the strength meter to 100% red.
* IMHO it would lead to confusion as to the meaning of the strength meter.
* the "passwords do not match" error should eventually become a proper error of the confirm EditText, not a separate label.
See merge request !2
akwizgran
Torsten Grote
Ernir Erlingsson
akwizgran
str4d