Well this is a small update to let you all know that things are really moving forward. Version 0.39 is just around the corner and should be out the door soon. To let you know what is due I will include what I have already completed.
V0.39
1) Fixed a problem where the country information was not updated to show net training on Saturdays
2) Fixed a problem in the settings form where the treeview was not being saved properly
3) Fixed a problem with importing a FC game that ended in a Tie.
4) Fixed a problem on some imports where Polish characters were causing problems.
5) Fixed a spelling error on the matches page.
6) Added in Top 10 innings list for batting and bowling.
7) Added a delete button to the select player list.
8) The training predictors now take a fielding and wicket net into account when calculating concentration and consistancy.
9) Added in Top 10 Appearances to records page.
10) Added in the training Overflow options. Now controlled by a setting in the settings form.
I'm looking forward to this release, as it covers a fair number of things that have been bugging me in AtStumps. I also know this version is going to upset a fair number of people, as I have changed some of the way that AtStumps loads. What this means is that there is a lot more data loaded during the splash screen. There were a lot of ways of looking at doing the loading and I can down to 2 options. The first was to put as much of the loading in the splash screen, this would make AtStumps appear to load slower. The second was to do late loading. What this would mean would be to load only the main players page, then only load the other pages as and when you click on their tab. This would make AtStumps load faster, but would slow down the tab changing when you are in the application. Both methods have their pros and cons, and I decided to take the simpler of the 2 and do most of the loading in the splash screen. I just felt that the amount of data that I would have to change for option 2 would just not be worth the benefit at this moment in time.
What I really need to do is to try and build in a metrics library so that I can actually get a fell for how much of AtStumps people actually use. This would then allow me to make a better decision on the late loading. Basically if people are only using the main player page, and using the other tabs only 10% of the time, then the late loading would be of huge benefit to AtStumps. I guess I will just have to live with what I have at the moment.
Now some bad news, I have been trying to find a way to build in a "copy from x" for the other browsers out there, and the bad news is that the other browsers just don't support a nice neat automation interface to the browser. This means that I would have to do a large amount of development for very little gain. Yes I know that it would make importing of data a lot easier and simpler, but I just don't have the time to try and make it all work. I have already spent 2 days trying to understand and find decent documentation of FireFox and it really is just not there. It is a real shame as I would have hoped that being a OS app that there would be more there. Microsoft are just far too far ahead in terms of proper documentation and samples. It could just be that I was not looking in the right places, but after 2 days of walking through web sites and not finding what I was really looking for I have decided to shelve it for the time being. I have how ever decided to look at building in a browser to AtStumps, that will handle automatic importing of pages and data as you surf the Battrick site. I will expand on this in another post in the future.