- Offline Storage
- If the application loses connection or has an error for any reason, it will store the data local on the device. Eventually I'll change to keep a full copy locally with an asynchronous push to the server and have an offline app, but that is a summer project. I still don't have the method of getting lost data back to the server just yet.
- Game Screen changes
- Roster now has tabs, one each for Attack, Defense, and Middies. Being on the list doesn't preclude a player from switching positions, it only helps me organize them better and minimize scroll.
- Added Primary Position
- Modified Team to reflect
- Modified Player to reflect
- New Team buttons (not completely implemented)
- Clear
- Team Goal
- Team Turnover
- Man Up
- Man Down
- Specialized buttons for Face Off Middie and Goalie
- Faceoff won
- Faceoff attempt
- Goalie Save
- Scored Upon
- Template
- Broke apart pages into commonality's and created a master template. I didn't do this early on because I wanted them to organically find its design and it mostly has at this point.
- Stats
- Game Stats
- Added Percentages for Scoring, Faceoff's and Goalie Saves
- Added Team Totals for individual stats
- Added Penalty report
- Fixed calculation for Shot on Goal to also include actual Goals.
- Player Stats
- All stats that exist for a team exist for player as a roll-up for the season (currently). Seems to be missing data for players who have played for a second team.
- Action Screen
- Removed Goalie Actions (save and scored) and Middie only actions (faceoffs)
- General
- I had several versions of the JQuery library listed throughout the application. With the template they are all on the latest version now.
- Removed some orphan pages
- Added a Favicon - sorta looks like a lacrosse head.
This blog is intended to document the development process of the Laxstats.me website which is software for recording live statistics during Lacrosse games.
Monday, March 25, 2013
Build .9032213
On Friday I deployed the latest build. Doing weekly builds has some risk and I'll be moving to more frequent builds instead. There are only a few people in the system so I'm not jeopardizing anything by doing so. The system is becoming very stable and the features are getting richer. I want to get more people involved but its hard to focus on marketing and development at the same time. Regardless, this is what was deployed.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment