eclipse-sailing-analytics/sailing-analytics
1
0 Fork 0
mirror of https://github.com/eclipse-sailing-analytics/sailing-analytics.git synced 2026-10-11 06:40:53 +00:00
Code Activity

Updated smartphone tracking (markdown)

Browse Source
This commit is contained in:
Fredrik Teschke authored and Wiki User committed 2013-08-05 16:31:07 +02:00
1 parent 8f57e6b347
commit 13cf2d061e
1 file changed
+29 -20
Download Patch File Download Diff File Expand all files Collapse all files
wiki/smartphone-tracking.md
+29 -20
View File
@@ -184,24 +184,33 @@ Async task that handles the execution of get requests.
### `AppPreferences`
Helper Class for accessing the App Preferences specified in settings_view.xml
## ToDo
* Server
* boat class for race: in racelog
* remove registered competitors: in racelog
* Servlet for getting all races, which are still open to register for
* persist tracking data (GPSFixStore)
* load stored tracked smartphone race (Panel in Admin Console, RaceLogConnector, only present such races with the necessary data in the racelog, and allow user to select whole leaderboard to restore)
* release mapping when race is finished
* mapping marks to devices
* RaceLogRaceTracker: functionality of RaceTracker as view on RaceLog (which then also makes tracking independent of smartphones, so we can mix different device types)
* generic method for registering listener for NMEA sentence types (e.g. to then process wind) -> move servlet for recieving NMEA out of smartphoneadapter
* user management (Competitors as users, credentials so not everybody can do everything)
-> integrate with OAuth, ISAF competitors etc.?
* security (not everybody can start race, goes hand in hand with user management)
* support dynamic mapping of smartphone to competitor -> so that it can change during the race
* support other input channels (e.g. Igtimi)
* Servlet for getting all competitors registered for a race (to in/exclude competitors) -> once RaceLog replication to all devices is implemented, this becomes unnecessary, as we then can just use the RaceLogAnalyzers
* Android
* abstract sending service, so that all POST / GET requests and not only RaceLogEvents can be sent using the semi-connectedness functionality --> just write JSONObjects/Strings directly into the file. The Servlet has to handle deserialization and the client doesn't have to know what type of object it is after having saved it (is this really the case?)
* simplify settings
* login/register Activity for registering the Team and Sailor the first time the App is started
### Server
* begin pre race phase event
* use for creating list of open smartphone events
* use to determine whether race can be started via servlet
* RaceLogRaceTracker: functionality of RaceTracker as view on RaceLog (which then also makes tracking independent of smartphones, so we can mix different device types)
* release mapping when race is finished (tracker listens for end event on RaceLog, and then calls adapters)
* create race creates tracker, or already before that?
* differentiate mapping device -> race and competitor and setting the TrackedRace (look at race status!)
* boat class for race: in racelog
* remove registered competitors: in racelog
* Servlet for getting all races, which are still open to register for
* persist tracking data (GPSFixStore)
* load stored tracked smartphone race (Panel in Admin Console, RaceLogConnector, only present such races with the necessary data in the racelog, and allow user to select whole leaderboard to restore)
* mapping marks to devices
* generic method for registering listener for NMEA sentence types (e.g. to then process wind) -> move servlet for recieving NMEA out of smartphoneadapter
* user management (Competitors as users, credentials so not everybody can do everything)
* -> integrate with OAuth, ISAF competitors etc.?
* security (not everybody can start race, goes hand in hand with user management)
* support dynamic mapping of smartphone to competitor -> so that it can change during the race
* support other input channels (e.g. Igtimi)
* Servlet for getting all competitors registered for a race (to in/exclude competitors) -> once RaceLog replication to all devices is implemented, this becomes unnecessary, as we then can just use the RaceLogAnalyzers
### Android
* abstract sending service, so that all POST / GET requests and not only RaceLogEvents can be sent using the semi-connectedness functionality --> just write JSONObjects/Strings directly into the file. The Servlet has to handle deserialization and the client doesn't have to know what type of object it is after having saved it (is this really the case?)
* simplify settings
* login/register Activity for registering the Team and Sailor the first time the App is started