I am building a PHP/MySQL site for beginning runners (athletes), and want to give them users of the small community of athletes I hope will visit my site, the ability to:
1) have a buddy-list of one or more members of the community on the site that they can send private messages to (not through e-mail, but just on the site itself), and
2) I would also like them to be able to enter/view/edit/print their daily workouts in an electronic log.
I have the details (a list of basic requirements) in the Deliverables section.
## Deliverables
Here are the details I'm requesting:
Requirement 1. Build working PHP/MySQL pages that can perform the two features listed in the general description, above.
Requirement 2. The private messaging system must have:
a. A main page that contains the member's buddy list, and a Search button to look for new buddies, and a Remove button to allow users to remove buddies from their buddy list.
b. The buddy list on the main private messaging page should display next to each buddy's screen name, the number of unread messages from that buddy and the total number of messages on exchanged with the buddy.
c. When attempting to add a new buddy to the user's list, there should be a method of seaching the sports interests of members of the web site community (the community table could have the following fields: Member ID, real e-mail address (confidential), password, screen name, sports interests (a list of key words), athletic level (beginner, intermediate, seasoned amateur, semi-pro), age, gender.
d. Let users try to contact potential buddies, and if the other member approves, then both members should be placed on each other's buddy list.
e. Members should be able to compose new and reply messages to each of their buddys.
f. Members should be able to delete messages.
g. The interface should be simple - please.
h. The tables that support this function should be simple, please. I've mentioned some of the fields for the community member's table (above).
i. Here are some ideas that may help with this part of the app:
**[login to view URL]
[login to view URL]
[[login to view URL]
Requirement 3. The][1] workout log must have:
a. A main page that contains the last 5 workouts in a list
b. The workouts table might look like this: Member ID, Date (datetime), Description (like, 80 chars), Workout type (run, swim, cycle, weights, ..), KeyWord (VARCHAR 10), Workout intensity (low, medium, high), WorkoutTime (hh:mm:ss), URL (to any additional details about this workout)
c. a Member should be able to add workouts, edit existing workouts, and delete workouts.
d. (OPTIONAL, BUT REQUESTED) If possible, there should b e a graphical report that would let the user select a workout type, date range, and KeyWord, and plot those workouts (Date vs. WorkoutTime) on a graph.
NOTE: Let me know if you will be able to do the workout graph (3.d).**
Requirement 4. The programmer will need to create the MySQL database.
Also - Deliverables must include the following:
1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables):
a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment.
b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request.
3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement).
## Platform
Must work in IE (6/7) and FireFox.