Cs345-2012 - Revision history

Gus: /* Our POSIT Bugs/Features */

2012-04-30T00:26:59Z

Our POSIT Bugs/Features

← Older revision		Revision as of 00:26, 30 April 2012
Line 46:		Line 46:
	# This was incorrectly characterized. The loop to display images was not broken, but rather somehow duplicates of the images were being stored in the database with unique ids. Maybe a client bug?		# This was incorrectly characterized. The loop to display images was not broken, but rather somehow duplicates of the images were being stored in the database with unique ids. Maybe a client bug?
	*# Fix the partial image display problem where the bottom is cut-off or grayed-out		*# Fix the partial image display problem where the bottom is cut-off or grayed-out
	*# Look at 0,0 vs null,null for Finds without geotagging (Tristan and Aaron working on client)		*# <span style="text-decoration:line-through;">Look at 0,0 vs null,null for Finds without geotagging (Tristan and Aaron working on client)</span>
	*# Implement the single frame solution to providing a /m interface for the server		*# <span style="text-decoration:line-through;">Implement the single frame solution to providing a /m interface for the server</span>
	*# Consider the deletes not synced but, two different approaches (delete vs flag and filter), reconcile how the clients do this and how the server does this, one approach for all?		*# Consider the deletes not synced but, two different approaches (delete vs flag and filter), reconcile how the clients do this and how the server does this, one approach for all?
	*# <span style="text-decoration:line-through;">Provide an interface for viewing deleted finds and un-deleting them</span>		*# <span style="text-decoration:line-through;">Provide an interface for viewing deleted finds and un-deleting them</span>

Twright09: /* Our POSIT Bugs/Features */

2012-04-29T16:23:19Z

Our POSIT Bugs/Features

← Older revision		Revision as of 16:23, 29 April 2012
Line 30:		Line 30:
	===Our POSIT Bugs/Features===		===Our POSIT Bugs/Features===
	* Aaron and Tristan		* Aaron and Tristan
	*# Finish empty find bug, commit changes to Google code repository. (Fixed. Need to commit and ~~post~~.)		*# Finish empty find bug, commit changes to Google code repository. (Fixed. Need to <span style="text-decoration:line-through;">commit and</span> push.)
	*# <span style="text-decoration:line-through;">Add client optional client logging, at least all attempts to connect to server and response, e.g. login, send finds, send tracks</span>		*# <span style="text-decoration:line-through;">Add client optional client logging, at least all attempts to connect to server and response, e.g. login, send finds, send tracks</span>
	# This was already supported by plugging the device into computer and running from Eclipse.		# This was already supported by plugging the device into computer and running from Eclipse.
	*# Look at 0,0 vs null,null for Finds without geotagging (Leif and Gus working on server)		*# <span style="text-decoration:line-through;">Look at 0,0 vs null,null for Finds without geotagging (Leif and Gus working on server)</span>
	# Filtering 0,0 locations is already implemented on the client side in MapFindsActivity.java in the function centerFinds() specifically on line 380.		# Filtering 0,0 locations is already implemented on the client side in MapFindsActivity.java in the function centerFinds() specifically on line 380.
	*# Fix pictures not always displaying on client's View Finds		*# Fix pictures not always displaying on client's View Finds

Charliep: /* Our POSIT Bugs/Features */

2012-04-27T11:47:40Z

Our POSIT Bugs/Features

← Older revision		Revision as of 11:47, 27 April 2012
Line 38:		Line 38:
	* Sean and Nick		* Sean and Nick
	*# Improve server log format and content, consistent entries when actions are taken		*# Improve server log format and content, consistent entries when actions are taken
			*# Fix finds with no pictures error on server's map display
	*# Improve the server side error handling, at minimum a function that logs what was happening and the message		*# Improve the server side error handling, at minimum a function that logs what was happening and the message
	*# Add a client activity log to the server, could be a live feed from /var/log/httpd/{access, error}_log		*# Add a client activity log to the server, could be a live feed from /var/log/httpd/{access, error}_log
Line 46:		Line 47:
	*# Fix the partial image display problem where the bottom is cut-off or grayed-out		*# Fix the partial image display problem where the bottom is cut-off or grayed-out
	*# Look at 0,0 vs null,null for Finds without geotagging (Tristan and Aaron working on client)		*# Look at 0,0 vs null,null for Finds without geotagging (Tristan and Aaron working on client)
	*# ~~Consider~~ the single frame solution to providing a /m interface for the server		*# Implement the single frame solution to providing a /m interface for the server
	*# Consider the deletes not synced but, two different approaches (delete vs flag and filter), reconcile how the clients do this and how the server does this, one approach for all?		*# Consider the deletes not synced but, two different approaches (delete vs flag and filter), reconcile how the clients do this and how the server does this, one approach for all?
	*# <span style="text-decoration:line-through;">Provide an interface for viewing deleted finds and un-deleting them</span>		*# <span style="text-decoration:line-through;">Provide an interface for viewing deleted finds and un-deleting them</span>
	* Gustavo and Jeremy		* Gustavo and Jeremy
	*# <span style="text-decoration:line-through;">Fix the Google Maps display missing on the client, script and instructions for people to install a key		*# <span style="text-decoration:line-through;">Fix the Google Maps display missing on the client, script and instructions for people to install a key
	*# ~~Consider how to add~~ a sensor reading to the client's ~~tracking~~ mode.		*# Implement adding a sensor reading (temperature) to the client's Tracking mode. Adjust the client's and server's data models and sync plumbing so that the temperature readings are stored with the expedition in the database.

	===== Unassigned =====		===== Unassigned =====

Gus at 18:32, 24 April 2012

2012-04-24T18:32:41Z

← Older revision		Revision as of 18:32, 24 April 2012
Line 45:		Line 45:
	# This was incorrectly characterized. The loop to display images was not broken, but rather somehow duplicates of the images were being stored in the database with unique ids. Maybe a client bug?		# This was incorrectly characterized. The loop to display images was not broken, but rather somehow duplicates of the images were being stored in the database with unique ids. Maybe a client bug?
	*# Fix the partial image display problem where the bottom is cut-off or grayed-out		*# Fix the partial image display problem where the bottom is cut-off or grayed-out
	*# Look at 0,0 vs null,null for Finds without geotagging (Tristan and ~~Gus~~ working on client)		*# Look at 0,0 vs null,null for Finds without geotagging (Tristan and Aaron working on client)
	*# Consider the single frame solution to providing a /m interface for the server		*# Consider the single frame solution to providing a /m interface for the server
	*# Consider the deletes not synced but, two different approaches (delete vs flag and filter), reconcile how the clients do this and how the server does this, one approach for all?		*# Consider the deletes not synced but, two different approaches (delete vs flag and filter), reconcile how the clients do this and how the server does this, one approach for all?

Twright09: /* Our POSIT Bugs/Features */

2012-04-24T02:32:34Z

Our POSIT Bugs/Features

← Older revision		Revision as of 02:32, 24 April 2012
Line 32:		Line 32:
	*# Finish empty find bug, commit changes to Google code repository. (Fixed. Need to commit and post.)		*# Finish empty find bug, commit changes to Google code repository. (Fixed. Need to commit and post.)
	*# <span style="text-decoration:line-through;">Add client optional client logging, at least all attempts to connect to server and response, e.g. login, send finds, send tracks</span>		*# <span style="text-decoration:line-through;">Add client optional client logging, at least all attempts to connect to server and response, e.g. login, send finds, send tracks</span>
			# This was already supported by plugging the device into computer and running from Eclipse.
	*# Look at 0,0 vs null,null for Finds without geotagging (Leif and Gus working on server)		*# Look at 0,0 vs null,null for Finds without geotagging (Leif and Gus working on server)
	# Filtering 0,0 locations is already implemented on the client side in MapFindsActivity.java in the function centerFinds() specifically on line 380.		# Filtering 0,0 locations is already implemented on the client side in MapFindsActivity.java in the function centerFinds() specifically on line 380.

Twright09: Edited our bug fix / feature list (Tristan & Aaron)

2012-04-24T02:31:46Z

Edited our bug fix / feature list (Tristan & Aaron)

← Older revision		Revision as of 02:31, 24 April 2012
Line 30:		Line 30:
	===Our POSIT Bugs/Features===		===Our POSIT Bugs/Features===
	* Aaron and Tristan		* Aaron and Tristan
	*# <span style="text-decoration:line-through;">~~Finish empty find bug, commit changes to Google code repository.</span>~~		*# Finish empty find bug, commit changes to Google code repository. (Fixed. Need to commit and post.)
	*# Add client optional client logging, at least all attempts to connect to server and response, e.g. login, send finds, send tracks		*# <span style="text-decoration:line-through;">Add client optional client logging, at least all attempts to connect to server and response, e.g. login, send finds, send tracks</span>
	*# Look at 0,0 vs null,null for Finds without geotagging (Leif and Gus working on server)		*# Look at 0,0 vs null,null for Finds without geotagging (Leif and Gus working on server)
			# Filtering 0,0 locations is already implemented on the client side in MapFindsActivity.java in the function centerFinds() specifically on line 380.
	*# Fix pictures not always displaying on client's View Finds		*# Fix pictures not always displaying on client's View Finds
	* Sean and Nick		* Sean and Nick

Charliep: /* Our POSIT Bugs/Features */

2012-04-21T12:02:33Z

Our POSIT Bugs/Features

← Older revision		Revision as of 12:02, 21 April 2012
Line 41:		Line 41:
	*# <span style="text-decoration:line-through;">Fix the server's Google Maps API key</span>		*# <span style="text-decoration:line-through;">Fix the server's Google Maps API key</span>
	*# <span style="text-decoration:line-through;">Fix the 2x display of pictures</span>		*# <span style="text-decoration:line-through;">Fix the 2x display of pictures</span>
	# This was incorrectly characterized. The loop to display images was not broken, but rather somehow duplicates of the images were being stored in the database with unique ~~id#s~~. Maybe a client bug?		# This was incorrectly characterized. The loop to display images was not broken, but rather somehow duplicates of the images were being stored in the database with unique ids. Maybe a client bug?
			*# Fix the partial image display problem where the bottom is cut-off or grayed-out
	*# Look at 0,0 vs null,null for Finds without geotagging (Tristan and Gus working on client)		*# Look at 0,0 vs null,null for Finds without geotagging (Tristan and Gus working on client)
	*# Consider the single frame solution to providing a /m interface for the server		*# Consider the single frame solution to providing a /m interface for the server

Charliep at 20:31, 20 April 2012

2012-04-20T20:31:47Z

← Older revision		Revision as of 20:31, 20 April 2012
Line 55:		Line 55:
	*# Fix QR codes for easy client download (built from our repository) and registration		*# Fix QR codes for easy client download (built from our repository) and registration
	*# Images are corrupted. Last bits seem to be scrambled. Images are stored in the DB.		*# Images are corrupted. Last bits seem to be scrambled. Images are stored in the DB.
			*# Cleanup all those warnings that appear in /var/log/httpd/error_log whenever a page is referenced
	* Client		* Client
	*# Log should include the version ID of the POSIT software, the Android software, and the Google API		*# Log should include the version ID of the POSIT software, the Android software, and the Google API

Charliep: /* Our POSIT Bugs/Features */

2012-04-20T19:49:44Z

Our POSIT Bugs/Features

← Older revision		Revision as of 19:49, 20 April 2012
Line 31:		Line 31:
	* Aaron and Tristan		* Aaron and Tristan
	*# <span style="text-decoration:line-through;">Finish empty find bug, commit changes to Google code repository.</span>		*# <span style="text-decoration:line-through;">Finish empty find bug, commit changes to Google code repository.</span>
	*# Add client optional client logging, at least all attempts to connect to server and response (~~if any~~)		*# Add client optional client logging, at least all attempts to connect to server and response, e.g. login, send finds, send tracks
			*# Look at 0,0 vs null,null for Finds without geotagging (Leif and Gus working on server)
	*# Fix pictures not always displaying on client's View Finds		*# Fix pictures not always displaying on client's View Finds
	* Sean and Nick		* Sean and Nick
Line 41:		Line 42:
	*# <span style="text-decoration:line-through;">Fix the 2x display of pictures</span>		*# <span style="text-decoration:line-through;">Fix the 2x display of pictures</span>
	# This was incorrectly characterized. The loop to display images was not broken, but rather somehow duplicates of the images were being stored in the database with unique id#s. Maybe a client bug?		# This was incorrectly characterized. The loop to display images was not broken, but rather somehow duplicates of the images were being stored in the database with unique id#s. Maybe a client bug?
			*# Look at 0,0 vs null,null for Finds without geotagging (Tristan and Gus working on client)
	*# Consider the single frame solution to providing a /m interface for the server		*# Consider the single frame solution to providing a /m interface for the server
	*# Consider the deletes not synced but, two different approaches (delete vs flag and filter), reconcile how the clients do this and how the server does this, one approach for all?		*# Consider the deletes not synced but, two different approaches (delete vs flag and filter), reconcile how the clients do this and how the server does this, one approach for all?

Charliep: /* Unassigned */

2012-04-20T19:45:54Z

Unassigned

← Older revision		Revision as of 19:45, 20 April 2012
Line 57:		Line 57:
	*# Recording a long track (+1 hour?) causes a crash		*# Recording a long track (+1 hour?) causes a crash
	* Both		* Both
			*# 0,0 vs null,null for Finds with no geotagging
	*# Find log should include username, which is then passed to server and stored as an attribute of the find		*# Find log should include username, which is then passed to server and stored as an attribute of the find