Adding initial code that will be used for generating the database that will be used within the application.
Fixed the problem that was causing the Feedback page to crash. The submit button will now work for uploading any feedback assuming the user has an internet connection when they go to use it. We don't currently have the function in the FileManager implemented for saving content past application shutdown. Somewhere along the line, the php files on the server have gotten removed and so the server is not able to handle the content from the feedback. #30 #62
The database is now updated with the butterfly lists that include the scientific and common family names. The butterfly database table now contains a column for frequent and clist. The frequent will be used to mark if that particular butterfly is on the users frequent list. The clist column will be a comma separated list of all the custom lists that particular butterfly is a member of. The provider for interacting with this new table is also finished. Some initial tests show that it is working as expected. #64
Fixed issue #65. The problem is Nathan's Toshiba tablet will not allow colons in file or directory names. We were putting colons in the directory name. Curtis suggested we change the format to something like 03h16m00s which I will implement later. This quick fix should make the tablets usable though before we go out surveying with Nathan. My quick fix just changes it so the .csv files will be written to the UBR folder, they will overwrite old files in there but I dont think that will be a problem in the short term.
formatting and cleanup
Finished issue #65, in the event of a failed creation of a folder containing a colon, will attempt to create a folder without colons.
updated location architecture. final commit before another redesign
commit before trying CurrentFusedLocationGetter
finished implementation of CurrentFusedLocationGetter and deprecated CurrentLocationGetter
bug fixes for fused location provider. Added gps prompt ala #45
attempted to add additional sighting fields
I performed a redesign of the database layout for the application. We did have a single database file that contain tables for the butterfly data as well as the surveys and sightings. This make it so that all the users data would be lost if we decided to copy in a new database with butterflies. Now the user data is in a separate database file as the butterfly listing. This will allow us to push region based lists without wiping out user data. Currently, the frequent and clist are still in the butterfly list so those will be lost. We will need to pull those into the user data database at some point.
Merged into databasesplit branch, fixed breadcrumbing
Revised settings page
Moved accidental copy of app from / into /app/android/
merged juldev into dev
merged SurveyFragment
merged from databasesplit
Merged ryandev and dev.
merged dev and hotfix_65