GitLab

should streamline new users setting up as well as the debugging process

Keeping the display updates but hopefully fixing the app so it doesn't crash when it tries to talk to a Bluetooth device

Fixed the problem where documents under 'note pad' wouldn't show up if they already existed. took out 1 second sampling interval and replaced it with 3.

If the user had never uploaded, downloaded, or cleared in the database actions activity, field day displays 'Never' instead of nothing.

New 'Current Database Information' on the bottom of Database Actions Activity. It displays: last time uploaded, last time downloaded, last time cleaned, current size, current status which could be: empty, initialized but no reading or streaming data, initialized with reading and streaming data, or initialized and just reading or streaming data. Font is set to 'Appearance Medium.' Only layout for portrait mode currently.

SensorSampleService gets updated site, sector or spot from SensorSampleActivity if the user changes it while bound to the service. Streaming button pulses when Field Day is streaming and writing to the database.

'NotePad' under 'Lab Notebook' opens the activity that will be used for downloading and opening pdfs from a remote server. The icons will change eventually, but since NotePad was already there, I used that for initial code. Inside that activity there's a button that says 'Download Files' that opens a popup asking for the URL and path of the directory. The activity goes out and gets a list of files from that directory on the remote machine (Indexing must be enabling by the web server on the remote machine). The activity shows a multi-select interface where the user can choose which files or folders to download. Checking the boxes and hitting 'Download' doesn't actually do anything right now.

New button in 'Sampling' -> 'Database Actions' that allows the user to clean the local database. If this button is pressed, it confirms that the user what's to clear the database. A backup copy is saved in the external storage: /storage/emulated/0/FieldDay/archive/<date>-readings.db, and all of the local tables are dropped and re-created. These methods are also called upon successfully uploaded tables to the remote database.

'Sampling' -> 'Database Actions' has two buttons, one for uploading and one for setting up local database. Upon clicking 'Upload' Field Day goes out inserts the spots, making sure that the (trip, site, sector, spot) primary key isn't broken on the remote database. After uploading spots, readings are uploaded and then streaming. Field Day uses a transaction by setting 'autoCommit' to false. If any SQLException is caught during this process then the transaction is rolled back. Tested with sampling 'Built In' sensor data, all rows appear in the database on hopper.

Moved the 'Remote Database Setup' from the Settings Fragment to 'Database Actions' under 'Sampling' -> 'Database Actions.'

New 'Database Actions' icon under the 'Sampling' icon. In the database activity, the user will be able to choose between uploading database tables or setting up the local database from a remote database. Field Day remembers the user's database information until a fresh install.

Reread button only on the fragment for bluetooth sensor, since it won't be needed for built in sensors. Got rid of unused files and images. Buttons are grayed out if they are not usable yet. For example: reread, sample and stream are not available on bluetooth sensors until the sensor is connected and the first value is read. After reading the first value, the buttons are turned to their normal color and set as clickable.

postgresql.jar to use with JDBC and connecting to remote database. Able to connect and read columns and rows from the remote database, tested with field_science database on hopper. The values aren't stored yet, that will be the next thing implemented.

Settings option to 'Connect to remote database'. This opens a new activity where the user inputs server ip, database name, username and password, etc (everything that is needed to connect to the database using the jdbc driver) to connect to the remote database for the schemas and rows in the tables. Doesn't actually do the connecting yet, this is just a layout page with some edit texts. It's not pretty, that will come after it's working.

There's a scan devices option under 'SensorSampleActivity.' This goes out and scans for Bluetooth LE devices that are available. It's not pretty, but we can focus on the aesthetics later. Tested and able to see available devices. Right now, the activity just lists them. Next thing to work on is actually connecting and getting the device information sensor fragments.

About a blank AboutFragment because on click() on the main screen page the about button would just go to the last fragment opened. Made minor changes to the layout files for the fragments and activities for best-practices/up to date syntax.

Customized radio button selector for time interval for writing to the database. This is just the UI basics, has not been used in the java code for actually controlling the write frequency to the database.

Added EditText options for site, sector and spot in the SensorSampleActivity. Set writeToDB to use those values instead of just sample hardcoded ones. Rearrange SensorSampleActivity so there's room for all of the options. In the settings.xml file, there's now an option to specify what the Trip Name is for database readings. I didn't think it was necessary to have Trip Name be on the SensorSampleActivity if it's going to be constant throughout the entire trip.

Cleaned up Settings.java to get rid of useless things from Seshat. Made the background of BuiltInSensors prettier!

Added FieldDay name to generated APK for both debug and release .apk. Debug uses a hard coded name. Release uses the "app" directory name. Changed "app" directory to "FieldDay" directory.

Fixed some minor grammatical errors -- now all of the Sample Buttons in 'Take a Sample' resolve to their correct fragment. Also fixed some spacing issues with Sensors and sensor values in strings.xml.

SensorListAdapter now uses a ViewHolder for both of the textviews  (sensor name and sensor value) for each item in the list. Using a ViewHolder really optimizes the code, by limiting the number of inflations of the Layout and the number of getViewById calls. For our list, it's not so bad, because there are only like 10 sensors, but once you get up to 100s of sensors, calling getViewById really is exhaustive.

aSensor now has a getLastValueString and getLastValue float methods. Their names explain what they do, the float methods returns the number values, and the string method returns the string (most for TextViews).

Added a debug checkbox option, so we know when we want to debug (send data collected to a different database - perhaps called 'debug').