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 and Classifieds

Phorum is the open source php forum software we used for this project. For detailed information or for support refer to www.phroum.com. The classifieds do have the same content as forum. We can think of them as two different headlines for two different kinds of forums. So classifieds is just another forum. Classifieds is the place where the user can discuss selling and buying things and Forum is the place where they can discuss any other topic. First of all, almost everything works properly in forum. Users create another account on the forum database on first log-in. There are two different database tables for the main webpage and for the forum this is necessary, because the first design of the webpage and the tables did not match with the forums, so we had to use two different tables. Please note that the second data in the forum tables are created after first log-on to the forum. Therefore any other user will not be able to send a message to new users until initial login to the forum. This is something that needs to be fixed. Also another issue is the passwords. The forum keeps the user password encrypted but the main website keeps user info as plain text. Every time we pass user information to the forum, the password field gets re-written. That is another problem that still needs to be fixed. Another issue is the admin page. As you will notice Phorum has very powerful tools. This includes spam detection. To use them you have to configure the admin page. You can access the admin page by using “/admin.php”. Still because of the password issue I just talked about, you need to hardcode your admin information to “hook_user_session_restore.php” And to file in “forum\mods\external_authentication\plugins_bin\comm_external_auth_plugin”directory . Lastly the whole of the forum look should change. This can be challenging since there is millions of lines of code that you need to get familiar with. You can use some plug-ins for this purpose. Also anytime you have a problem you can get support at www.phroum.com Integration of the web page and forum is done by “external_authentication” plug-in, it is located at “forum\mods\external_authentication”. In external_authentication plug in there is a folder called “comm_external_auth_plugin”. This is the folder that contains all the files that makes integration possible for our web-site and forum. I did edit “hook_user_session_restore.php” to make it work with main web-site. We used session information for this integration. But as the project develops this file will need further additions. I highly recommend that you check this file out and understand how it works.

Pros : • Working forum • Powerful admin tool • Easy to get support from www.phroum.com • Lots of Plug-ins for various purposes

Cons: • Needs a better look (interface) • Needs better synchronization with main web-sites data bases.

Working Parts: • Opening new topics • Writing on topics • Editing posts and topics • Admin panel • Direct transition between forum and main web-site • Message Center(mostly)

Parts that need work : • Interface needs to be changed • Integration needs work • Password field synced with main web-site • Massage center (initial login problem)

Pros : • Working forum • Powerful admin tool • Easy to get support from www.phroum.com • Lots of Plug-ins for various purposes

Cons: • Needs a better look (interface) • Needs better synchronization with main web-sites data bases.

Working Parts: • Opening new topics • Writing on topics • Editing posts and topics • Admin panel • Direct transition between forum and main web-site • Message Center(mostly)

Parts that need work : • Interface needs to be changed • Integration needs work; • Password field synced with main web-site • Massage center (intial login problem)

• Blog

Mr. Frisbie is going to open a blog in one of the blogging sites. When he does you can just add a hyperlink to that page. Since blogging sites have more flexibility and tools, this is what we agreed to do for now. As the project develops, developers may need to create a blog page in the web-site.

• My Communities

Trophies

Appearance of the Trophies section depends on user's login status. If you are a guest and you clicked on the Trophies tab, you see the latest trophy's picture and information on the screen and by clicking to the blue arrows you can browse other trophies back and forth. If you are already registered and logged in you only see your successful hunts on the Trophies page.

Message Center

We are using Forum message center for messaging activities. There is one minor problem with this, which I mentioned in the Forum and Classifieds part of this page. But other than that the message center works perfectly. Users can send and receive messages with no problem using that. The flags work properly. There is also a full list of usernames that is provided to them. That makes it easy to find the people they want to send messages to.

My Journal

---

• Personal Profile

When you click on the My Journal tab, your Personal Profile comes up to the screen. In your profile you see your picture, your address and a button to edit your profile. Profile section has a search property but it is not working right now. Also in the Buddies section , you can see your other friends and if you click on their name you can see their profile and all other stuff they have.

• Hunt

In this part, users can create a new hunt or can see his/her previous hunts.

-hunt.php

Shows previous hunts of the user and a button at the top that allows to create a new hunt.

-newHunt.php

Users can create a new hunt with the information(date, location, time, comment etc.) they provide.

-add_hunt.php

This file has no visual part, it adds the new hunt to the database.

-editHunt.php

Shows one of the previous hunt that user choose and allow the user to change the information about that hunt.

-updateHunt.php

This file has no visual part, it updates the selected hunt from the database.

• Scouting

Has 7 parts: Scrape, Bed, Rub, Track, Animal, Dropping, Other

1) Scrape

In this part, users can create a new scrape or can see his/her previous scrapes.

-scrape.php

Shows previous scrapes of the user and a button at the top that allows to create a new scrape.

-newScrape.php

Users can create a new scrape with the information(date, location, description etc.) they provide.

-add_scrape.php

This file has no visual part, it adds the new scrape to the database.

-editScrape.php

Shows one of the previous scrape that user choose and allow the user to change the information about that scrape.

-updateScrape.php

This file has no visual part, it updates the selected scrape from the database.

2) Bed

In this part, users can create a new bed or can see his/her previous beds.

-bed.php

Shows previous beds of the user and a button at the top that allows to create a new bed.

-newBed.php

Users can create a new bed with the information(date, location, description etc.) they provide.

-add_bed.php

This file has no visual part, it adds the new bed to the database.

-editBed.php

Shows one of the previous bed that user choose and allow the user to change the information about that bed.

-updateBed.php

This file has no visual part, it updates the selected bed from the database.

3) Rub

In this part, users can create a new rub or can see his/her previous rubs.

-rub.php

Shows previous rubs of the user and a button at the top that allows to create a new rub.

-newRub.php

Users can create a new rub with the information(date, location, description etc.) they provide.

-add_rub.php

This file has no visual part, it adds the new rub to the database.

-editRub.php

Shows one of the previous rub that user choose and allow the user to change the information about that rub.

-updateRub.php

This file has no visual part, it updates the selected rub from the database.

4) Track

In this part, users can create a new track or can see his/her previous tracks.

-track.php

Shows previous tracks of the user and a button at the top that allows to create a new track.

-newTrack.php

Users can create a new track with the information(date, location, description etc.) they provide.

-add_track.php

This file has no visual part, it adds the new track to the database.

-editTrack.php

Shows one of the previous track that user choose and allow the user to change the information about that track.

-updateTrack.php

This file has no visual part, it updates the selected track from the database.

5 )Animal

Awating the information about this part from Mr.Frisbie.

6) Dropping

Awating the information about this part from Mr.Frisbie.

• Locker

Users can create a locker which is containing of weapons, clothings and equipments. User can add multiple items to their locker or delete multiple items from their locker. They can select these items from weapons, clothing and equipment tables from the database.

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.