Meeting tomorrow at 1PM in Riggs

Component API Document
-header files
-english description



UML document
-use cases
-stub code

David Marshall-
API for Rover group

Stephen Wesson-
API for Cam/Nerf group

Chris Abbott-
API for GUI gorup

Rob Brennan-
UML Document (with use-cases)

David Ho-
Camera API (this includes images only, no commands)(this is for however many cameras they use)
(i would say like where to save the jpeg on the server for the camera group)
(where the jpeg is being read from on the laptop itself)
(call me if anyone has questions)
803-707-3466



Everyone-
We also need stub code for wednesday.
Be thinking about that.
Remember Patent office meeting tomorrow then our group meeting is right after that. (try to have your documents by then to ask him questions about them)
I have copied the repository and gui code from the old class project onto my computer and usb thumb drive. If anyone needs that stuff, call me or shoot me an email. dsmarsh@clemson.edu.



-David Marshall

oh and post your stuff before the meeting if you want everyone to be able to comment on it

If possible, shoot me the repository code. swesson@clemson.edu

I'm having trouble wrapping my head around what exactly our API's need to include for tomorrow. For instance, am I putting together a header file for the communication between the repository and the camera on the rover?

Such as...

//Command codes (obviously needs to the the same codes as GUI)
typedef enum
{
CAM_UP = 201,
CAM_DOWN,
CAM_RIGHT,
CAM_LEFT,
CAM_ZOOM_IN,
CAM_ZOOM_OUT,
GUN_UP = 301,
GUN_DOWN,
GUN_RIGHT,
GUN_LEFT,
GUN_FIRE,
//Reset command here (need more than one reset command for camera and nerf gun separate??)
} COMMAND;

//Calls function matching command sent from GUI
void callCommand(COMMAND cmd);

etc, etc...

I may be way off, which is why I'm a little confused.