This blog is intended to document the development process of the Laxstats.me website which is software for recording live statistics during Lacrosse games.
Friday, March 29, 2013
Build .9032913
I found a really nice JQuery plugin that allows for tables to be reordered. Unfortunately I had to convert all of my nice div tables into actual HTML tables. It works like a charm for IOS. I've deployed these changes to the live site for the team oriented stats and player career stats. I want to have for the game stats for the game tomorrow. It will be a long work night tonight.
Wednesday, March 27, 2013
Build .9032713
As promised, more frequent pushes. Today I pushed:
- New Team Page
- Schedule moved to top and made prominent ala ESPN. Calculates record on the fly.
- Team Info and Coaches moved to top of page beside Schedule.
- Edit Team Info now a Dialog box that pops up instead of going to another page.
- Bug - New team info is broken
- New Tab System for Players
- Default tab is for Player info (still needs a bit more work to include all player data. I may put this into an editable table structure.
- Player Season Statistics - gives full stats for all players who have played on a team during the season with full counts for all games completed.
- Player Game Average - calculates the X per game stat for all players.
- Played Time - tab is there, report is not complete
Monday, March 25, 2013
Feature Focus - March 25 - 29
All of our games got rained out over the weekend so there was no new data to cause me sleepless nights. This week I'm going to focus on some left-over features.
- Offline Storage
- Get back to server
- Home Page
- Start Marketing
- Game Screen
- Lines?
- Timer
- Hook up new Team buttons
- Determine how to handle man up/down situations. With a modifier to main action???
- Game Info
- Set players to unavailable
- Set players to be "borrowed"
- Team Screen - major overhaul needed, want this page to look like it came from ESPN
- W/L
- Team Stats for the Season
- Player link should go to master player page with stats
- Stats
- Game Stats
- need more of the team data (clears, turnover, etc).
- Time line report
- Team Stats
- Create based on game, but do rollup for entire season
- Allow break down by game?
- Additional stats
- shots per game
- saves per game
- avg FOW percentage
- Player stats
- Fix bug
- Combine with player page
- Organization/Program Screen
- Match US Lax types
- Custom CSS for Orgs
- Better layout - ala ESPN or CBSSports
- Following
- Add team follow
- Post to facebook when following has action?
- Offline Stats
- Add offline entry of stats - important for those who can't get a live tablet and for players/teams to have a running record in a single location
- Girls variations - get with a girl's coach to be sure I understand the primary differences.
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.
- 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.
Monday, March 18, 2013
Feature Focus - March 18-22
With the major bug from yesterday weighing on my mind, I'm certain that it will take the bulk of my week to get implemented. However, there is still a ton to get done. Again in no particular order...
- Offline Storage
- Save copy locally
- When game finishes, compare the two results, update local to server at that time.
- Home Page
- Start creating a marketing version of the home page
- Game Screen
- Better Roster organization
- Lines/grouping of players
- Timer (still looking into longer term solution)
- Better user feedback for Clears
- Man Up/Down button
- Team Activities - Goal, Turnover
- Better way to record Face Offs
- Better way to record Goals
- Game Info
- Set players to unavailable (will help the roster organization)
- Set players to be Defense, Attack, or Middie to help minimize screen scroll
- Team Screen
- W/L Box
- Stats Screen
- Game report
- Remove Penalties from current game table
- Create secondary report for team actions, including totals for all actions.
- Create timeline report.
- Create time on field/shot percentages, etc.
- Team report
- Create team rollup of all games, same as game report, may need way to dive into game report from here.
- Create additional stats, Shots per game, saves per game, etc.
- Player report
- Individual statistics for the player, use same report as game, just limit per person, very important for followers
- Organization report - although important in the future, putting on hold for now, I only have 2 teams from a single organization at the moment.
- Action Screen
- Hide goalie actions for non- goalies
- Organization/Program Screen
- Set types to match US Lax
- Custom CSS for Orgs
- Better layout and design
- Following
- Add Team Follow
- Offline Stats
- Need ability for those without wireless tablet to enter data after a game.
- Deployment
- Better way to keep in synch
That's enough for a week. If you have a feature request that you would like to see on this list, please leave me a comment.
Offline Storage
I guess it goes to show you that you shouldn't mention what could be a serious problem before you've addressed it. During the first game yesterday, the app performed as expected with no issues (at least none that weren't already known). However, during the second game I started getting "bad proxy" errors. I'm not sure if this was a connectivity issue from ATT or something on GoDaddy's side. Since neither have claimed the issue I'm certain that I will never know. Thus the second game ended up missing approximately 1/3 of its data. That being said, Offline Storage just became my number 1 priority for the week.
Sunday, March 17, 2013
Beta - Week 3
Yesterday was another busy day, with 2 teams stats being taken back to back. Many of the issues that I noticed last week weren't addressed this week due to having the Follow function up and running and Facebook integration. The Follow function allows for Parents and Fans to keep up with their favorite Player or Team real time. Since the entirety of the Beta is currently U11 Boys, the data will be skewed a little, but its better than nothing. I'm still quite pleased with how its gone but there is easily as much work left as has already been completed. I've two more games to do today, so after this point I'll be a lot more comfortable and will look to expand the beta to more teams. Also this week I added the "login with Facebook" feature which virtually eliminates any barrier to entry for someone looking to follow a player. It also helps to eliminate cracking attempts at my low level authentication. I don't have any huge features to be added this week (short of the timer, but I'm happy with how it currently works) so I should be able to enhance what is already there and eliminate some of the bugs.
Yesterday, I had the situation where one team needed to "borrow" a player from another team. Fortunately, I was prepared for that, at least for the addition. I'm not so sure that I can gracefully hide at this point and I'm not going to worry about it today. I'll think that through a little better tomorrow. I did notice that the individual Player stats don't appear to be calculating for teams other than the original team. I must have an error in the SQL because it should calculate across all teams. I do need a better Player page, and that will be second on the priority list for this week.
I will eventually need the concept of game validation. As it stands the stat recording is a "fire and forget" methodology. It is necessary to keep from getting behind in the recording (which still happens). What that means is that the AJAX Get is pushed, but no request is required, which means that I could lose a stat here of there based on the whims of ATT. I think that I'll also write a manifest locally and upon game completion do a comparison against the two and if any are missing to add them then. That will have a heavy payload and its something that will require a lot of thought. I'm putting into the parking lot for the Fall release.
That's if for now, got a game to go to. I'll update with my feature list in the morning. Have a good St. Paddy's day!
Yesterday, I had the situation where one team needed to "borrow" a player from another team. Fortunately, I was prepared for that, at least for the addition. I'm not so sure that I can gracefully hide at this point and I'm not going to worry about it today. I'll think that through a little better tomorrow. I did notice that the individual Player stats don't appear to be calculating for teams other than the original team. I must have an error in the SQL because it should calculate across all teams. I do need a better Player page, and that will be second on the priority list for this week.
I will eventually need the concept of game validation. As it stands the stat recording is a "fire and forget" methodology. It is necessary to keep from getting behind in the recording (which still happens). What that means is that the AJAX Get is pushed, but no request is required, which means that I could lose a stat here of there based on the whims of ATT. I think that I'll also write a manifest locally and upon game completion do a comparison against the two and if any are missing to add them then. That will have a heavy payload and its something that will require a lot of thought. I'm putting into the parking lot for the Fall release.
That's if for now, got a game to go to. I'll update with my feature list in the morning. Have a good St. Paddy's day!
Wednesday, March 13, 2013
Build .9031313
Yesterday I completed the Facebook Login integration. With this in place, I no longer need registration, one can simply "login with Facebook" and I capture everything I need from them. This makes registration and authentication a breeze for both me and the user. I'm going to get the "Follow" portion completed next so that Parents can watch their kids stats.
Monday, March 11, 2013
Feature Focus March 11-15
I'll be working on the following this week, in no particular order.
- Facebook login
- Home Page
- Start creating a marketing version of the home page
- Game Screen
- Better Roster organization
- Lines/grouping of players
- Timer (still looking into longer term solution)
- Better user feedback for Clears
- Man Up/Down button
- Team Activities - Goal, Turnover
- Better way to record Face Offs
- Better way to record Goals
- Game Info
- Set players to unavailable (will help the roster organization)
- Team Screen
- W/L Box
- Stats Screen
- Game report
- Remove Penalties from current game table
- Create secondary report for team actions, including totals for all actions.
- Create timeline report.
- Create time on field/shot percentages, etc.
- Team report
- Create team rollup of all games, same as game report, may need way to dive into game report from here.
- Create additional stats, Shots per game, saves per game, etc.
- Player report
- Individual statistics for the player, use same report as game, just limit per person, very important for followers
- Organization report - although important in the future, putting on hold for now, I only have 2 teams from a single organization at the moment.
- Action Screen
- Hide goalie actions for non- goalies
- Organization/Program Screen
- Set types to match US Lax
- Custom CSS for Orgs
- Better layout and design
- Following
- Base setup
- Allow Parents, etc, ability to follow player (youth protected)
- Deployment
- Better way to keep in synch
That's enough for a week. If you have a feature request that you would like to see on this list, please leave me a comment.
Live Beta Test #2
Saturday was a very busy day. We started early with the first test of the day. The second test of the application went better than the first. With some of the changes I made, it was easier to get the players onto the field. I'm still annoyed with the screen scroll when a roster is too large. I've shrunk the names as much as I can and it still be usable. I've got to come up with another way. Also this is iPad only ATM and other tablets it may be worse. I've got someone with an Android tablet that wants to help test so maybe that will help answer that question.
Feature Request #1 - Come up with way to stop the scroll.
During the first game, I had no issues and everything worked really well. It also helped knowing the players names a bit better. Some things to consider is that currently it takes 2 entries to record a Face Off Won. As you know, that is the fastest part of the game so often the steps were, record Face off Attempt, record Face off Won, and record who picked up the ground ball. If there was an assist and a score there, that would be a tough stretch to keep up with. Similar issue with a goal. Often there was an assist, shot on goal, and then a goal. Currently I haven't been counting a Goal as a shot on goal although I should. I can either calculate that post action, or build it in. Not sure which way to go just yet.
Feature Request #2 - Determine better way to record Face Off process.
Feature Request #3 - Determine better way to record Goals/SOG's/Assists.
Although I separated Clears from the individual stats and put it on the field as a team stat. Recoding it had no feedback. It was a direct record to the database and as such didn't notify the user that it had done its work. Perhaps I need some indicator that a Clear did happen.
Feature Request #4 - User Feedback for Clears
Still the biggest problem I had was on line swaps. Getting 3 new players on the field, especially during a score and then a face off opportunity was too slow. At least twice I had missed a middie (fortunately he didn't do anything during that time). What I need to have is the concept of lines, just like the teams have. That way I can activate a line and it would still give me the flexibility to rotate individuals in and out.
Feature Request #5 - Create Position "Lines"
At the end of the game, the statistics were quickly and easily calculated and put into my nice new tabular format. I had left a spot for Penalties, but I can't easily integrate them into the table, and because they won't be calculated by type, don't fit anyway. I'm going to remove that from the table and do a secondary report for the team as a whole where I report penalties. I need a team report anyway, so this works out well.
Feature Request #6 - Team report, calculate totals for all, report on clears and man up/down opportunities, Team Goals, Team Turnovers, and Penalties.
I was asked to do a second game for a different team and I was happy to oblige since this gave me more data. Fortunately I did know a lot of the Player by name already as they practice with my son, and/or have played on his team in the past. Still, it was much harder to keep up with than it was during the first game, just because of my lack of knowledge for the boys. One bug surfaced. Although it was recording the scores correctly, on the field screen, it had the home and away as the same team. Not sure why this occurred as I wasn't able to reproduce on the spot.
Defect - Away team on both sides of the scoreboard.
Last week I stood with the parents to take the stats which helped greatly when I was struggling with names, etc. This week I stood with the boys. Once they figured out what I was doing, I was having to answer the same question every 5 minutes "what are my stats?" After learning my lesson, my answer became, "I can't get that until the end of the game", but the truth is that I can refresh the report as the game goes on, which was a nice way for me to validate that the program was working as intended. It also helped to validate that the real time push to Facebook that I want to integrate will work nicely.
Now with 2 games under our belt for my son's team, Parents are now getting interested in seeing the stats. This week's number one priority is to complete the Facebook login integration and to get "Following" working properly. If it is anything like the Google Maps integration, it shouldn't take more than a day to get implemented.
That's my thoughts for now. As always if you have any suggestions for the application, I'm very grateful to hear them.
Feature Request #1 - Come up with way to stop the scroll.
During the first game, I had no issues and everything worked really well. It also helped knowing the players names a bit better. Some things to consider is that currently it takes 2 entries to record a Face Off Won. As you know, that is the fastest part of the game so often the steps were, record Face off Attempt, record Face off Won, and record who picked up the ground ball. If there was an assist and a score there, that would be a tough stretch to keep up with. Similar issue with a goal. Often there was an assist, shot on goal, and then a goal. Currently I haven't been counting a Goal as a shot on goal although I should. I can either calculate that post action, or build it in. Not sure which way to go just yet.
Feature Request #2 - Determine better way to record Face Off process.
Feature Request #3 - Determine better way to record Goals/SOG's/Assists.
Although I separated Clears from the individual stats and put it on the field as a team stat. Recoding it had no feedback. It was a direct record to the database and as such didn't notify the user that it had done its work. Perhaps I need some indicator that a Clear did happen.
Feature Request #4 - User Feedback for Clears
Still the biggest problem I had was on line swaps. Getting 3 new players on the field, especially during a score and then a face off opportunity was too slow. At least twice I had missed a middie (fortunately he didn't do anything during that time). What I need to have is the concept of lines, just like the teams have. That way I can activate a line and it would still give me the flexibility to rotate individuals in and out.
Feature Request #5 - Create Position "Lines"
At the end of the game, the statistics were quickly and easily calculated and put into my nice new tabular format. I had left a spot for Penalties, but I can't easily integrate them into the table, and because they won't be calculated by type, don't fit anyway. I'm going to remove that from the table and do a secondary report for the team as a whole where I report penalties. I need a team report anyway, so this works out well.
Feature Request #6 - Team report, calculate totals for all, report on clears and man up/down opportunities, Team Goals, Team Turnovers, and Penalties.
I was asked to do a second game for a different team and I was happy to oblige since this gave me more data. Fortunately I did know a lot of the Player by name already as they practice with my son, and/or have played on his team in the past. Still, it was much harder to keep up with than it was during the first game, just because of my lack of knowledge for the boys. One bug surfaced. Although it was recording the scores correctly, on the field screen, it had the home and away as the same team. Not sure why this occurred as I wasn't able to reproduce on the spot.
Defect - Away team on both sides of the scoreboard.
Last week I stood with the parents to take the stats which helped greatly when I was struggling with names, etc. This week I stood with the boys. Once they figured out what I was doing, I was having to answer the same question every 5 minutes "what are my stats?" After learning my lesson, my answer became, "I can't get that until the end of the game", but the truth is that I can refresh the report as the game goes on, which was a nice way for me to validate that the program was working as intended. It also helped to validate that the real time push to Facebook that I want to integrate will work nicely.
Now with 2 games under our belt for my son's team, Parents are now getting interested in seeing the stats. This week's number one priority is to complete the Facebook login integration and to get "Following" working properly. If it is anything like the Google Maps integration, it shouldn't take more than a day to get implemented.
That's my thoughts for now. As always if you have any suggestions for the application, I'm very grateful to hear them.
Friday, March 8, 2013
Build .9030813
Build .9030813 will be deployed later today. Included in this build are:
- Finish Game Button
- Completes all Player actions
- Flips Game Status
- Event Dialog
- Minimize Penalties list - toggle to be invisible, only viewable when needed
- Make Actions larger
- Add other events - defaulted to the NCAA rule book
- Update Event Dialog to break out per NCAA rules
- Team Page
- Updated Game list to reflect completed games
- Added Stats button once game has started
- "Start Game" changes to "Continue Game" once started
- Game Page
- need to be able to set players as unavailable for the game - completed database work, not hooked up on page yet
- Order by Jersey number
- Player name aligned to button
- Jersey numbers as draggable instead of full name
- Stats
- Take data and create Pivot output - may be completed by launch
- Added Like button to each page, authentication not ready yet
- Game Info Page
- Google Maps integrated
- DEFECT - only works on new game, existing games won't change map.
- Template
- Added Footer to all pages
- Include Google Analytics via footer
- Facebook like via footer
- Database
- Added Game Unavailable table - for players who won't be at game
- Added GameTime table - to time box game via actual time
- Updated Events with new Events (TurnOver, Caused TurnOver, Face off Attempt)
- Updated Game with Points For and Points Against
Sunday, March 3, 2013
Feature Focus - March 3-8
This week I'll be focusing on the following features (not prioritized yet):
- Finish Game Button
- Completes all Player actions
- Flips Game Status
- Event Dialog
- Minimize Penalties list (dropdown?)
- Make Actions larger
- Add other events (interceptions, turn over, etc. - find better resource)
- Game Timer
- Freeware was inadequate, need a full system. This is likely too big for a single week.
- Team Page - needs a W/L box
- Game Page
- need to be able to set players as unavailable for the game
- Order by Jersey number
- Truncate name or other methodology
- Jersey numbers as draggable instead of full name
- Stats Page
- Game
- Replicate standard game sheet familiar to most coaches
- Create timeline report
- Team
- Create rollup team stat report (for all games [with a filter to each individual game])
- Create advanced reports (time per goal, etc.)
- Player
- Create single player stat report linkable from player id
- Also linkable to followers (youth protected)
- Filter by Lifetime/Year/Season/Team/Game
- Organization/Program
- Full report for season broken down by gender, age level, team
- Need to determine need for larger long time report (may be helpful as players advance careers)
- Organization/Program
- Set types to match US Lax
- Custom CSS for Organizations
- Better layout and design
- Facebook integration
- Following
- Base setup
- Allow parents, etc. ability to follow player (youth protected)
- Deployment
- Better way to keep DB in synch
- Better file deployment (Git?)
First Beta Test
I spent the week frantically trying to get enough pieces into place that would allow me to take the stats for the Saturday game. Some features had to be scrapped for less functionality just so it would work well enough (not be a stopper). No other beta testers have come online yet, so it was just me on Saturday (in hindsight this was the better way to approach it).
First, let me say that it is one thing to come up with an idea and code it, but once you are forced to see it in action at the speed of a Lacrosse game, one can see some immediate improvements. The previous game ran over so the refs were on a fast pace to get the game started. I had anticipated having a few minutes to populate the field for the first time. Sadly I didn't get that time and was rushed to get players on the field as the game started within seconds of them taking the field. They won the faceoff which gave me time to get everyone on the field. I may have missed a ground ball, but otherwise was able to catch up. The other thing was that without knowing each players name well, I was forced to rely on other parents to help me fill out the roster. What I mean by that is that I just struggled quickly finding a number with a name which pointed out my first real bug in the system. I designed it to be number specific, so that all you needed to do was see the Jersey to tell what happened. But since I neglected to sort my list (either alphabetically or numerically) finding players was a bit of a strain.
Defect 1 - sort by jersey number.
My player list is setup on the right hand side of the screen (which is great for right handers - need to address for lefties at some point), but I had originally designed it to be a fixed width. Some of the names causes wrapping and thus made if more confusing as I couldn't see the numbers neatly lined up on the left hand side of the box.
Defect 2 - eliminate wrapping (either by truncating the name, allowing for an indent on the wrap, or something else).
Although the dragging idea is sound, the problem I had was that the entire name and jersey number were part of the draggable item. The drop point was the center of the draggable item, so players with long names had drop points to the right of where my finger tip was. I missed dragging a couple of players that way. Perhaps this needs a smaller, more reliable draggable item, such as a button with only the jersey on it.
Defect 3 - make jersey the draggable item.
During the game the app worked as expected. The one annoying thing was that on an event, the focus was to a drop down list that I had (which I had already fixed, but not deployed to the live site). Also, the text list was a little small and didn't allow a lot of room for error. This was partially due to my having so many entries for Penalties.
Defect 4 - separate penalties better, make events bigger.
It also occurred to me that I may be missing some event items. I was missing things such as interceptions and turn-overs, but that was due to the reference material I used. My son is U11 and some of those things don't show up until later in his career. But I could have easily recorded that during the game.
Feature Request - more inclusive events.
Lastly, I only had a rudimentary statistics page up, it was the last thing I did on Friday night before the game, and it was raw at best. However, it allowed me to give good stats, but since I had each position on the field as a separate entity, I had to do some adding on the fly (not an issue, but obviously something to address). So not a bug per se, but functionality to complete. One thing I did notice is that a touchable application is tough on a 39 degree day (my poor finger was all but frozen).
I did get a chance to introduce my app to a few new people. Although we lost, I noticed that the opposing team stat keeper was doing everything by hand, literally a list of who did what when and then he would have to add everything up at the end. I showed him the app and asked him if he would like to be part of the beta. He was very interested and I expect to hear from him before next week's game.
That's it for now. I'll update you as things continue to progress.
First, let me say that it is one thing to come up with an idea and code it, but once you are forced to see it in action at the speed of a Lacrosse game, one can see some immediate improvements. The previous game ran over so the refs were on a fast pace to get the game started. I had anticipated having a few minutes to populate the field for the first time. Sadly I didn't get that time and was rushed to get players on the field as the game started within seconds of them taking the field. They won the faceoff which gave me time to get everyone on the field. I may have missed a ground ball, but otherwise was able to catch up. The other thing was that without knowing each players name well, I was forced to rely on other parents to help me fill out the roster. What I mean by that is that I just struggled quickly finding a number with a name which pointed out my first real bug in the system. I designed it to be number specific, so that all you needed to do was see the Jersey to tell what happened. But since I neglected to sort my list (either alphabetically or numerically) finding players was a bit of a strain.
Defect 1 - sort by jersey number.
My player list is setup on the right hand side of the screen (which is great for right handers - need to address for lefties at some point), but I had originally designed it to be a fixed width. Some of the names causes wrapping and thus made if more confusing as I couldn't see the numbers neatly lined up on the left hand side of the box.
Defect 2 - eliminate wrapping (either by truncating the name, allowing for an indent on the wrap, or something else).
Although the dragging idea is sound, the problem I had was that the entire name and jersey number were part of the draggable item. The drop point was the center of the draggable item, so players with long names had drop points to the right of where my finger tip was. I missed dragging a couple of players that way. Perhaps this needs a smaller, more reliable draggable item, such as a button with only the jersey on it.
Defect 3 - make jersey the draggable item.
During the game the app worked as expected. The one annoying thing was that on an event, the focus was to a drop down list that I had (which I had already fixed, but not deployed to the live site). Also, the text list was a little small and didn't allow a lot of room for error. This was partially due to my having so many entries for Penalties.
Defect 4 - separate penalties better, make events bigger.
It also occurred to me that I may be missing some event items. I was missing things such as interceptions and turn-overs, but that was due to the reference material I used. My son is U11 and some of those things don't show up until later in his career. But I could have easily recorded that during the game.
Feature Request - more inclusive events.
Lastly, I only had a rudimentary statistics page up, it was the last thing I did on Friday night before the game, and it was raw at best. However, it allowed me to give good stats, but since I had each position on the field as a separate entity, I had to do some adding on the fly (not an issue, but obviously something to address). So not a bug per se, but functionality to complete. One thing I did notice is that a touchable application is tough on a 39 degree day (my poor finger was all but frozen).
I did get a chance to introduce my app to a few new people. Although we lost, I noticed that the opposing team stat keeper was doing everything by hand, literally a list of who did what when and then he would have to add everything up at the end. I showed him the app and asked him if he would like to be part of the beta. He was very interested and I expect to hear from him before next week's game.
That's it for now. I'll update you as things continue to progress.
Build .9022813
Features added:
- Statistics Page - shows after game is started (very limited functionality - just enough to run first beta test)
- Events write to database asynchronously.
- Score dynamically updates on game screen and records to database, no round trip needed. Upon refresh, sets from database to keep in synch.
- Draggable functions working for iPad (need Android to test).
- Events are variable based on position.
- Game spawns in separate window to eliminate back.
Defects addressed:
- Event orphans addressed.
- Timer changed to Time of Day clock - need to find longer term solution
- Player reset turned off, killed draggable action, couldn't find a way to reset draggable
Subscribe to:
Posts (Atom)