Sportsmans App

- This is the page where you can find all of the information about the Sportsman Application.

Specifications of the Project

Software Platforms

In the development process we will be using PHP, MySQL, HTML, CSS, JavaScript, Eclipse, Android and Adobe Dreamweaver.

Team Members

Mert Ahmet GUNES
Onur ISPANLAR
Kemal YILDIZOGLU
Doga TUNCYUZ

Project Owner

Mr. Rick Frisbie

Purpose of the Sportsman Application

This project aims to provide technological features to the hunters with a mobile application when they are hunting and allow them to share information before or after the hunting with a web application. This web application also includes features like, users can create groups to share specific information and hunt together.

Project has 2 parts: A Website and an Android Application.

Hunter's Journal Website

Hunter's Journal is the planned name of the website.
Every user must register in order to use the website.
After being a member; users can add friends, see and edit profile pages, send messages, see other user's profile pages, create hunting events and invite other people and share their notes about their hunts.
Mert and Onur will work on website part of the project.

Hunter's Journal Android Application

In the Android Application, users will have following features:

The main usage of the application is that a user can take notes about his/her hunt, such as: the weather conditions, sunset time, moon's position etc.
Another usage is that you can access your inbox throughout the application and can send a message.
Also you can see the status of your community members.
Doga and Kemal will work on the Android part of the project.

Progress of the Project

Meetings with the project owner had arranged and the specifications of the project has been decided.

Development of the Interfaces are now in progress.

Database information will be provided from the owner.

02/28/2011

Home Page is ready. You can see the news on the home page. Also registration, logging in and logging out modules are finished.

Server is connected, database is ready. In order to see the home page click that link [1]

Technical Documentation of Hunter's Journal

Website

Communities:

Forum

   Kemal

Classifieds

   Kemal

Blog

   Blog part of the project is missing. In this part, admins of the website will be able to share their blog's links.

My Communities

Trophies:

   Mert

Message Center:

   Kemal

My Journal:

Personal Profile

   Mert

Hunt

   Onur

Scouting

   Onur

Locker

   Onur

Android Project

The purpose of the project changed a bit in time. First functionalities were like in the first description, the application to show the weather conditions, sunset etc. but the time constraints made it impossible for us to finish them all in time. That is why after productive meetings with Mr. Frisbie, we shortened the requirements list to: - Logging in - Hunting notes - Scouting notes - Adding definitions for user to use in hunt and scouting pages - Messaging capabilities

Logging in

The user logs in using username and password he gave to the website. The users email password combination’s existence is checked in this page. The user can also register from that page.

Known issues: -Some control problems can be fixed.

Hunting notes

First page the user will see is all the previous hunts. When the user clicks on one, he will see and edit these hunts.

The user can start taking notes by clicking “Start new hunt”.

This is the part where you take all the notes; - Date: o Full date is the input here. - Location: o Location is taken by having the name of the area and the state which is compared in the data and added to database if that state has that location name - Hunting area: o This field makes the user to select a hunting area that is predefined in database or added by the user to database. - Standing area: o This field makes the user to select a standing area that is predefined in database or added by the user to database. - Weapons used: o This field makes the user to select a weapon that is predefined in database or added by the user to database. - Backpack: o This field makes the user to select all the backpack items from a list that is defined by the user and add it to that specific backpack for that hunt. - Phase of rut: o This field makes the user to select the rut phase from the database. - Start time: o This field takes the starting time of the hunt. - End time: o This field takes the end time of the hunt. - Comments: o All the comments about that hunt are noted in this field. - Who went with you: o Your hunting buddies who came with you to that hunt can be added to this field.

Known bugs: -Information for users about what to put in that field. -Backpack is not functional. -The visual part needs to be revised. We didn’t touch the visual parts at all. -Wwwy can be improved by adding the buddies but not just the names of them (Combining the names and users). -Controlling the “null” return of the SQL statement has to be controlled. -The SQL statement does not control “updating the hunt”, so the “insert” statement has to be changed to an “update” statement.

Scouting notes

The scouting part has 7 different scouting topics, which are: -Scrape -Rub -Bed -Track (not been implemented yet) -Animal (not been implemented yet) -Droppings (not been implemented yet) -Other (not been implemented yet)

Scouting/Scrape page

First page the user will see is all the previous scrapes. When the user clicks on one, he will see and edit these scrapes.

The user can start taking notes by clicking “New Scrape”.

This is the part where you take all the notes: - Date: o Full date is the input here. - Location: o Location is taken by having the name of the area and the state, which is compared in the data and added to database if that state has that location name. - Is it fresh: o This field makes the user to select the freshness of the scrape. - Is it new: o This field makes the user to select how new the scrape is. - Tree: o This field makes the user to select the tree type from database - Size: o This field makes the user to select the size in a type all the hunters can understand. - Is it natural: o This field makes the user to select if the scrape is natural or not. - Description: o This field takes the description of the scrape as input.

Scouting/Bed page

First page the user will see is all the previous bed. When the user clicks on one, he will see and edit these beds.

The user can start taking notes by clicking “New Bed”.

This is the part where you take all the notes: - Date: o Full date is the input here. - Location: o Location is taken by having the name of the area and the state, which is compared in the data and added to database if that state has that location name. - Is it spook: o This field makes the user to select if the bed is spook or not. - Notes o This field is used for taking notes. - Description: o This field takes the description of the bed as input.

Known bugs: -The visual part needs to be revised. We didn’t touch the visual parts at all. -Information for users about what to put in that field. -Controlling the “null” return of the SQL statement has to be controlled. -The SQL statement does not control “updating the hunt”, so the “insert” statement has to be changed to an “update” statement. -The parts that are missing can be implemented by just tweaking from the hunt or working scout pages

Definitions and settings

This is the part where all the definitions are saved to database for the other pages’ use.

-Stands This page takes a new stand name and sends it to the database for hunt and scouting pages to use.

-Hunting areas This page takes a new hunting area name and sends it to the database for hunt and scouting pages to use.

-Weapons This page takes a new weapon name and sends it to the database for hunt, scouting and backpack pages to use.

-Clothing This page takes a new clothing name and sends it to the database for hunt, scouting and scouting pages to use.

-Equipment This page takes the new hunting areas and sends it to the database for hunt, scouting and scouting pages to use.

Known issues: -The visual part needs to be revised. We didn’t touch the visual parts at all. -Backpack has to be implemented. -Some control problems can be fixed.

Messaging capabilities

This is the part where the users send “PM”(personal message)’s to each other. The screens and what they do is pretty much straight forward.

-Sending new message takes two inputs: “To” and “body”. “To” makes the user select the user he wants to send to. Body is as the name already implies the message itself.

-Inbox is the part where the users read their “PM”s. The list of all the messages is displayed here.

Known issues: -The visual part needs to be revised. We didn’t touch the visual parts at all. -Some control problems must be fixed. -“Sent messages” is missing but it is the same as inbox with small differences in the SQL statement.

The android application can be loaded to a real phone by reading the tutorial from http://stackoverflow.com/questions/5266375/how-do-i-run-an-eclipse-helios-project-right-on-my-android-phone.

The main functionalities are working properly, the only problems the android applications has are bugs and cosmetics.