PantherX wrote:Today I was babysitting the uploading of my 6041 WU which was 54 MB and took roughly 1.25 hours. During this time, I was getting some ideas about some "features" - if you may call it- that would be interesting to have in the future versions of the Client: (programming is easier said than done so I do respect all your handwork and dedication that you have put in to making such amazing software that too for FREE
)
1) WU History: This would be an interesting feature where the Client records all the successfully completed WU done by the Client. It could be grouped according to the Projects done. Something that was initially available in the Official Stats but was later removed. The idea is that F@H users complete unique WUs so there isn't any duplication on general basis unless you miss the Preferred Deadline or got errors. Now I am expecting this to be low on the list of your to-do as this doesn't really have any actual usage but would be interesting.
2) The feature of showing the FAHLog for the selected WU is an interesting one but it only works for FAHLog.txt. It would be interesting if it could also read the FAHLog-Prev.txt Also the color coding is nice but not uniform, maybe in later versions, this would be fixed completely (looking forward to that). Also I would like to add when the WU is over, the Fahlog should be displayed till "[14:46:53] + Number of Units Completed: X" as it indicates a successful completion rather than "[14:49:46] + Closed connections" as this is technically the next WU (I don't mean to be rude or anything rather telling what I think would be more appropriate). The rest of the Log should be displayed for the next WU. Also when I fail to receive WU from the Server, and restart the Client, HFM.NET displays "No Log Available". While it is true for the selected WU, (I got scared the first time I saw it and took me some time to figure out) I would suggest that the WU Info be automatically blank when the displaying the FAHLog. I hope this is on you to-do list once the Client is out of BETA Stage.
Well these are my observations and I decided to share them. Feel free to comment.
Thanks for those kind words.
1) I think you've got your answer. But to answer your second question, if you mess with the layout of that file HFM isn't going to respect it. It will continue writing the values in the order in which they are seen.
2a) FAHlog-Prev parsing is something I will tackle later... much later. See the list of Issues I already have planned for the next point release:
http://code.google.com/p/hfm-net/issues/list
2b) What is wrong with the log coloring exactly? I'm aware that things can be colored incorrectly due to word wrap on the log... which will be fixed in the next version.
2c) Oh no my friend... the WU "boundaries" will remain the same. This is truly a matter of opinion I realize. Really, to HFM it's more a question of where a WU starts rather than where one ends. The indicator of "+ Processing Work Unit..." (or whatever it is) is very consistent across all clients and has served me well. There's a lot more to do here than just what is displayed to the user. What is displayed is what is actually parsed as well, making the log section you see actually where any data is gathered for that particular WU.
2d) Whats wrong with "No Log Available"? Because you started the client and it doesn't show anything yet? Maybe your client continually tried to receive work but could not... then you don't know what's going on? Confirm that's what you're saying... I think I have an Issue entered on something like this already or I remember making a change to the effect of... "show the entire FAHlog.txt if no WU has started since the last client start".
