REFACTOR: Removing libraries and project files that don't need to be there; updated git ignore.
TESTING: Updating to modern Robolectric; updated pom dependencies; broke out test runner into utility classes
TESTING: Removed useless tests that were causing the command line build to fail; added comments.
WIP: Some of the tests are now passing; need to figure out how to test the bus - if I need to at all. It would be nice to verify that the keys are sending the right values to the bus. It's possible that the tests I want to run really belong in an automated suite.

* Added application
* Added otto bus, mocking to pom
* Broke out display and calculator buttons into separate fragments
* Moved lots of code around to support new breakdown
* Made the fragment dumber, make the activity smarter, might want to rebalance later
* Added base fragment
* Added view events

* Some tests are working!
REFACTOR: Rename
Made the tests pass for the simplified button filled fragment; removed mention of the bus; recording the event for testing instead; verified all the button clicks lead to the correct number events; added tests for the operator events + equals and clear; added a test class so I could get access to the event.
Fixed crashes on load of fragments
Dumbed down the activity; moved logic to display; would like to break out more logic in the display into a utility/state tracker, if time.
Made the calculations work again, tests next!

* Removed Object casting, using strings instead for the display
* Updated enum to have a string representation
* Getting number instead of event string
Broke out display and calculator state into separate fragments

* Created calculator state fragment and moved logic here, added to FM
* Display now receives events and only updates the display, moved logic to state tracker
* Updated tests in the display fragment to cover the events that will be encountered
* Moving test logic to the correct classes, added new test class
* Created navigation event fragments

Outstanding:
* Equals button doesn't work at the moment, may need to break out the
  operation/state tracking further into two items (NONE, NUMBER, EQUAL in one
  group and calculator operations in another)
* Make the tests pass in the calculator state
* Use DI or something to swap out the Otto bus for testing
Improved state tracking

* Broke out number logic into a separate function
* Tested number key cases, added test class for utility and state tracking
* Added/used a new tracking value for the type of key entered last and separated from the operators
* Added overflow checking and error new string, new exception type

Outstanding:
* Get display value from the DisplayFragment or obtain in another way
* Make the tests pass in the state fragment
Storing the value in the activity each time that it is updated

* Created a new event type
* Registered event type in activity, stored value
* Got value for operations in the calculator state

TODO: Make tests pass!
REFACTOR: Moved the events to the events/subpackages; created new base type for each category; normalized naming.
REFACTOR: Moved more files into packages
WIP: Updating operation tests