Do we want to change the name? I know someone mentioned that before... Anyone have any bright ideas?

YAC Handling

I noticed there was a new column added called balance. Isn't this handled by the yac table? So wouldn't there instead be a yac_id column in the user table would corresponding with an id in the yac table?

Okay here is my best shot at describing the code design:

Event Class: create event objects. Each event has a time (the starting time), an outcome, home team, home score, away team, and away score. Basic idea is there will be an array of events. Then for each event associated with a particular user's id we can tie it to the database and display. Need to explicitly call the parent constructor (like in the Login class).

Team Class: I'm still not sure if we need this. Nathan, I think we finally agreed that we did, right? Each team object would have an id, short_name, full_name, and conference. Just like in the database.

Generic System Class: should contain all data that is NOT specific to a particular user. For example, array of Event objects, array of Wagers, teams, etc.

Also, I think we need to add a Request Table to the database. It will hold the requester's and requestee's id. It will have a wager id (which will go in the Wager table before this anyway). Essentially, a user would get a pop up when they have a pending bet request and they can confirm or deny (probably a boolean value that gets set and is initially NULL until a user responds).

Also for now a valid time for betting should be set for an hour before the official start time of an event.

scaling between window sizes is not consistent. Maybe need to think about a javascript solution using zoom. This is because the text size needs to change and not the size of the divs. the divs are already scaled to percentages.

Something we probably should have is a Terms of Use page. We'd said we had one in our write-up last semester but that's when we thought we'd be using bitcoins. I was thinking the user would have to hit an accept button after registering or something or other.

Ok so the problem I'm running into is that each team posts their individual scheduels as a .csv but not all are put into one giant .csv like the NHL one Nathan found. So what I'm think is I might just import each individual team's schedule and then remove the duplicates using SQL queries. Any other suggestions are more than welcome. That web scraper is too old to work I think and no recent ones have been made.

User Interface

The UI is an ongoing effort throughout the duration of the developement. Here is a simple list of file that are involved in the main implementation of the UI:

• css/main.css
• css/icons.css this is a static (r/o) file that houses the icon fonts
• css/login.css main stylesheet for the login subsystem

css/main.css contains some generic style that can be used from page to page for example:

.widget {
  float: left;

  background: #FFF;
  box-shadow: 2px 2px 0px 0px #555; 
}

would be a generic class for any widget on any page. From there, in the page specific stylesheet you would add onto that generic styling by giving you new widget div and id and adding additional styling like so:

.widget#home {
  width: 15em;
  height: 8em;

  margin: 0 1em;
}

in this case the element being styled is
<div class="widget" id="home"></div>

http://tinyurl.com/q866soq
there is a feature of espn called bottomline that lists upcoming events, headlines, and scores.

Theres also a pretty good amount of stack overflow posts that go in depth about scraping/using regular expressions to parse both regular espn scores and just bottomline.

ex 1: http://tinyurl.com/lxmc6p6
ex2 : http://tinyurl.com/psrgpdm
(this one uses espn's mobile site to get scores)

fuck internet exploder...

but yeah this is an ongoing issue. guess we'll fix it sometime down the road.

We don't have to change the scope of our project at all, i think a good looking and functioning site where you could bet tokens on sports would be fine. But i think a cool thing that would make the site stand apart, is something that we talked about before, being able to bet on anything at all with your friends, or random people(both would just be queries to the DB, or using a "friend" system that we could implement. Like anything ranging from a coin flip to a friend kicking a tennis ball into a hoop.

yo, so these are some names i came up with at work, let me know if anything sounds cool.

1. VentureSport
2. Dice Sports
3. Gamblisto (i just thought this sounded cool)
4. Venture Gains
5. Betify or Sportify
6. Betport
7. eventmatic or betmatic
8. ezBet or ezWager

Event Handling

classes/Event.php

This class should handle all requests made to the database and asking for data related to the event table.

This class should most likely be a generic system module rather than being associated with a specific User

This task will mostly be based on new files.

Comment if I forgot to mention anything or you think there should be more to it

Ummmmmm... hmmmmm.... regarding the Event classssss......

haha ^^ mozart.

anyway, regarding your comment in the event class about the array of teams, why do you need that when you have private data members home_team and away_team. I'm assuming those will get set to the team id in the constructor then you could just have a set function for each of those private. variables that queries the DB and resets those variable to be Team objects.

So i created a new branch and i cloned master (to try and start fresh with updated UI and stuff) now I think I messed it up so you can roll back anything I did. Still getting the hang of this

Password Reset

Simple password reset module. This will be part of the Login subsystem. When a user requests to reset their password, they will have to provide their email. When that script executes a token will be generated and stored in the database in the reset table, along with some other information like a timestamp. There will also be an complete value stored in the DB. This will serve a boolean to tell if the token has been used already.

The user will then be sent an email including a link to the reset page with the token tacked on the end. The reset script will check the token against the database and if valid provide an opportunity to reset password, otherwise displaying the appropriate error message.

User Home Page

This would be the User home page showing various relevant data such as:

• currrent bets
• past bets
• 'watching' events
• current balance
• etc.

Git Workflow

I was reading about using git and good git workflows and I think this may workout a little better for us but I wanted a second opinion.

Basically its the same as we talked about before except for pulling changes. So on a per user basis, each developer has their own branch. They would commit to that branch and push to the corresponding remote branch. Rinse and repeat.

After some amount of commits and pushes from a single developer, when they feel their changes should be incorporated into the current dev branch, that user would then submit a 'Pull Request'. To do this, you would go to github, switch to your branch (with the drop down menu), then click 'Pull request'. From there you can describe the changes and submit the pull request. This creates an environment where each user can review the changes made and discuss them before the actual 'merge' is made. It is also a notification that your changes need to be pulled into dev.

At some point in time, whenever we feel like we have hit a milestone in developement, all of each individuals changes will be merged into dev and then dev will be pushed to master. Master can then be tagged as a 'release' with appropriate changelog.

After a release is made, each developer would then pull from master (instead of periodically, pseudo-randomly, pulling from dev like before), ensuring that we all begin work again with a copy of the code that contains all of the changes made by each developer.

Let me know what you think of this kind of workflow.

So now we have these global arrays from the datadase. I think we need to now categorize them further. For example, we should categorize the events into sports (which I have already done a little bit, but I think we may need to find a new way to do it) and then by league, etc. This may require some rework of the database. Its something to think about for sure.

The register button javascript doesnt work for some reason. It should work because it works in other places but it doesnt work when you click the link to register on the bottom of the login box. dont know why.