From Earlham CS Department
Revision as of 20:28, 19 April 2012 by Gus (talk | contribs) (Our POSIT Bugs/Features)
Jump to navigation Jump to search

Welcome to Software Engineering Spring 2012 Class Wiki. Please post any information that you think will be helpful to the class and our projects. Need help with wiki syntax? Click Here

POSIT Project Resources

Our POSIT Pointers

Our POSIT Tutorials

Our POSIT Bugs/Features

  • Aaron and Tristan
    1. Finish empty find bug, commit changes to Google code repository.
    2. Add client optional client logging, at least all attempts to connect to server and response (if any)
    3. Fix pictures not always displaying on client's View Finds
  • Sean and Nick
    1. Improve server log format and content, consistent entries when actions are taken
    2. Improve the server side error handling, at minimum a function that logs what was happening and the message
    3. Add a client activity log to the server, could be a live feed from /var/log/httpd/{access, error}_log
  • Leif and Gus
    1. Fix the server's Google Maps API key
    2. Fix the 2x display of pictures
      • 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?
    3. Consider the single frame solution to providing a /m interface for the server
    4. 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?
    5. Provide an interface for viewing deleted finds and un-deleting them
  • Gustavo and Jeremy
    1. Fix the Google Maps display missing on the client, script and instructions for people to install a key
    2. Consider how to add a sensor reading to the client's tracking mode.


  • Server
    1. Fix QR codes for easy client download (built from our repository) and registration
  • Client
    1. Recording a long track (+1 hour?) causes a crash
  • Both


  • Server
    1. Design and develop /m support
    2. More dense/useful find display (sorting options, map thumbnail option, etc.)
    3. Placemark to find mapping
  • Client
  • Both
    1. Test harness geared towards find integrity
      • Presence and content
      • Add, update, delete
    2. Design and build POSITx-Rescue
      • Study the plugin architecture
      • Design the interface - functionality, screens, menus
      • Build the interface, notion of a skin and simplified structure

Android Development

Eclipse Tutorials

Student Logs

To Sort