Couple simple UI requests
Re: Couple simple UI requests
mpettitt - I am curious about one thing. You say when a batter comes up, and is listed as "Ground out, fly out" that you want to see the details. Can you not get that info from the graphic showing where the ball went? If you aren't seeing those, then tap the text where it lists what the batter did previously.
Re: Couple simple UI requests
First, the iscorecast play back experience is Not the same on flash vs HTML player, And it is more than just the visual, the text is not the same either. (is this by design ftm?, at some point will both players give the same textual description). Curently The flash player provides more text detail than then the html player. Ie HTML says ground out, flash may say ground out to shortstop throw to first base.. S
Second, in My experience the ball in play is more visible in the Html player than the flash player even though html graphics are much smaller. Also At times the flash player even seems to miss displaying ball at all.
Third and most important, in both players, the ball disappears on next play. If you do not see it as play happens, you miss it. Looking back to prior play, all you see is text, you loose the graphic clues. That alone is a reason to describe where the ball went in addition to the graphic. On the html player, you get player x grounds out, or player y flies out. But not ground out to short, 6-3 out. Or player y flies out to center, f8. This is an even bigger 'miss' when talking hits.. If you miss the ball placement graphic moment, no idea where the ball went, if ball hit to left side right side, up middle infield or outfield, or what. Would be nice to see line drive hit, up the middle, or grounder to left side, or fly to center
Having the graphs is nice but should also have the text.
In sum, 1) adding to the playback the same shorthand you already have and are putting on scorecard (eg f8' or 6-3) would be nice and add clarity in a very compact way. 2) be nice if the text played back in iscorecast players HTML and flash were the same, so the only difference between the two was look and feel, not content.
Second, in My experience the ball in play is more visible in the Html player than the flash player even though html graphics are much smaller. Also At times the flash player even seems to miss displaying ball at all.
Third and most important, in both players, the ball disappears on next play. If you do not see it as play happens, you miss it. Looking back to prior play, all you see is text, you loose the graphic clues. That alone is a reason to describe where the ball went in addition to the graphic. On the html player, you get player x grounds out, or player y flies out. But not ground out to short, 6-3 out. Or player y flies out to center, f8. This is an even bigger 'miss' when talking hits.. If you miss the ball placement graphic moment, no idea where the ball went, if ball hit to left side right side, up middle infield or outfield, or what. Would be nice to see line drive hit, up the middle, or grounder to left side, or fly to center
Having the graphs is nice but should also have the text.
In sum, 1) adding to the playback the same shorthand you already have and are putting on scorecard (eg f8' or 6-3) would be nice and add clarity in a very compact way. 2) be nice if the text played back in iscorecast players HTML and flash were the same, so the only difference between the two was look and feel, not content.
Re: Couple simple UI requests
Yes, of course, IFF you took the time to place it on that play. But sometimes either I don't press the ball placement or it doesn't register (don't know which), so you're left not quite sure. With the extra play description, it's not a problem.jcbeckman wrote:Can you not get that info from the graphic showing where the ball went?
Of course, also, it's nice to have the ball placement as well since 4-3 can mean up the middle or in hole, short or deep, etc. (Not that anyone can take much from such a small sample as one game.)
Thanks
Re: Couple simple UI requests
I've got one more, minor UI suggestion that I've noticed during that last two practice games we had. I just started using iScore and am still getting use to it.
After a ball is in play, there is always another window asking "What happened to the runner on ..." I inevitably am making mistakes in these windows simply because I am speed reading everything to get thru the scoring. The small change/preference I'm suggesting is;
Change the words "first," "second," and "third" at the end of the "What happened..." questions to "1st," "2nd" and "3rd" to make it pop a little better. Maybe make them bold or stand out a just little more to differentiate the windows for the different runners.
I don't read the word "STOP" on stop signs, I just recognize the graphic and associate an action. This is a minor UI suggestion that would make it easier for me to quickly comprehend the question and score accurately.
Thanks.
After a ball is in play, there is always another window asking "What happened to the runner on ..." I inevitably am making mistakes in these windows simply because I am speed reading everything to get thru the scoring. The small change/preference I'm suggesting is;
Change the words "first," "second," and "third" at the end of the "What happened..." questions to "1st," "2nd" and "3rd" to make it pop a little better. Maybe make them bold or stand out a just little more to differentiate the windows for the different runners.
I don't read the word "STOP" on stop signs, I just recognize the graphic and associate an action. This is a minor UI suggestion that would make it easier for me to quickly comprehend the question and score accurately.
Thanks.
- FTMSupport
- Site Admin
- Posts: 13193
- Joined: Sat Mar 28, 2009 7:25 pm
Re: Couple simple UI requests
Thank you for the suggestion...we will add it to our list.
Check out the new iScore Baseball documentation page!
Includes videos and user manual.
http://iscoresports.com/baseball/training.php#docs
Includes videos and user manual.
http://iscoresports.com/baseball/training.php#docs
Re: Couple simple UI requests
I was just scheduling future games for our youth LL team and appreciate the Scheduled Date feature on the 'New Game' screen in v3.0 that allows us to enter future game dates which show up on the Game Info screen under 'Game Dates.'
I'd like to suggest to also include "Location" and "Notes" on the 'New Game' screen. The content for these fields would then show up on the Game Info screen under Game Details. When we schedule a future game, we (usually) know well ahead of time where it will be (1 of 4 fields for us) and usually have some notes to go along with it (something as simple as the Game #).
Thanks.
I'd like to suggest to also include "Location" and "Notes" on the 'New Game' screen. The content for these fields would then show up on the Game Info screen under Game Details. When we schedule a future game, we (usually) know well ahead of time where it will be (1 of 4 fields for us) and usually have some notes to go along with it (something as simple as the Game #).
Thanks.
- FTMSupport
- Site Admin
- Posts: 13193
- Joined: Sat Mar 28, 2009 7:25 pm
Re: Couple simple UI requests
We will add this request to our list as well... thank you. In the meantime, you can always go to the Game Info screen even for future games and fill this information in.
Check out the new iScore Baseball documentation page!
Includes videos and user manual.
http://iscoresports.com/baseball/training.php#docs
Includes videos and user manual.
http://iscoresports.com/baseball/training.php#docs
- Jaskegreen
- Posts: 88
- Joined: Thu May 06, 2010 3:32 pm
- Location: San Diego North
Re: Couple simple UI requests
There have been some Scorecast suggestions here, so I thought I'd add one as well.
I have labeled all the teams in our league with the division they are in and the team name. For example, teams are labeled as Mustang Rays and Bronco Padres. After logging into the Flash player Scorecast, half of the game title is cut off due to the date of the game and the long team names, making it difficult for viewers (like Grandma & Grandpa) to know which game is the one they want to watch.
I suggest that after so many characters, the text line gets wrapped to the next line down but with the same background color. That way my Dad, I mean Grandma & Grandpa
, are able to choose the correct game that their grandson is playing in.
Cheers,
Jason
I have labeled all the teams in our league with the division they are in and the team name. For example, teams are labeled as Mustang Rays and Bronco Padres. After logging into the Flash player Scorecast, half of the game title is cut off due to the date of the game and the long team names, making it difficult for viewers (like Grandma & Grandpa) to know which game is the one they want to watch.
I suggest that after so many characters, the text line gets wrapped to the next line down but with the same background color. That way my Dad, I mean Grandma & Grandpa

Cheers,
Jason
- FTMSupport
- Site Admin
- Posts: 13193
- Joined: Sat Mar 28, 2009 7:25 pm
Re: Couple simple UI requests
Thank you for the suggestion... we will add it to our list. We are hoping to do several improvements to the iScorecast viewer this season.
Check out the new iScore Baseball documentation page!
Includes videos and user manual.
http://iscoresports.com/baseball/training.php#docs
Includes videos and user manual.
http://iscoresports.com/baseball/training.php#docs
Re: Couple simple UI requests
I know this is an older post, but I think many of these issues remain open. The OP makes some great observations/suggestions. I completely agree with many of these.1) Number of Ks/BBs for the current pitcher. There are constant requests for this information and I find myself either having to keep it on a paper or trying to remember.
2) Defensive Position of the current hitter to the right/left of the plate with his/her jersey number. This would make announcing much easier since we announce the jersey number and position along with the name.
3) In the list of what a batter did in earlier PAs, it would be very nice to give the F9/6-3 kind of description in parens after Flied Out or Grounded out.
4) Need to be able to record Blown Saves/Holds or at the very least have a field where this can be written and which is displayed in the box score.
5) Number of pitches pitched in the box score would be very helpful since managers must adhere to strict rules regarding pitch counts. It doesn't need to be a column- just listed for each pitcher in the free-form section where 2Bs, etc, are listed.
6) We don't use the pitch location and speed section of the screen. It seems to be a real waste of precious real estate on the screen- even on the iPad. It would be VERY nice to have a list of the lineup with maybe an "0-4" or "1-3 2B RBI" kind of thing next to the player's number and name. Or am I missing an easy way to get to this information so we can see quickly who is the hitting star of the game? It would be nice if there was a toggle to switch from Home/Visitor for this information.
7) Some scoring is very awkward and clumsy and the program just doesn't seem to help by disallowing things that just make no sense. (For example: when the batter hits a single and there's a button you can press that says "Advanced by batter". Of course he was advanced by the batter- he IS the batter. Another example: when a hit is recorded and there are buttons still for WP and BP. You can't have a wild pitch on a single. Things like that.) Other things like it being quite happen to record a SB where the runner at first isn't advanced to 2nd.
8) Dropped 3rd Strike- there are situations that I can't seem to get right. When the catcher tags the batter (or the batter gives himself up and walks to the dugout and the ump calls him out with/without a tag and without a play at first) the scoresheet has Kd but no play and the play-by-play description says "Dropped 3rd strike - Thrown out".
9) It would be much more intuitive if swiping the strike button with two strikes would just record a Ks instead of asking. If it's the first or second strike it records a swinging strike. Seems to follow that on the third strike it should do the same.
#7 would be at the top of my list. I totally agree that non-possible selections should be eliminated from selection menu.
I would love it if iscore would not allow me to select the runner at first and choose stolen base while leaving the runner on first, creating an entry of "runner steals 1st base".
For that matter, I would like for the safe tab to not be an option when I select Out.
#1-#3 - posted a suggestion elsewhere (and specifically with the ipad in mind where the real estate exists) would like to see inclusion of batter information and picture, including things discussed in OP's 1-3.
#6 - like the idea that has been discussed where this would be a user option. Would further like the option of being able to use pitch location w/o the pitch type selector visible.
Mark.
Mark
iScore Baseball 4.533 on iOS8-iPad4 and iPhone 6-Plus
iScore Baseball User Manual:
http://iscoreleagues.com/manual/ <- Check it Out!
iScore Baseball 4.533 on iOS8-iPad4 and iPhone 6-Plus
iScore Baseball User Manual:
http://iscoreleagues.com/manual/ <- Check it Out!