toTOW wrote:The wisest move would be to switch HFM to using the JSON interface ...
But I hope it won't take him two years to publish a new version this time ...
![Rolling Eyes :roll:](./images/smilies/icon_rolleyes.gif)
touché toTOW.
![Laughing :lol:](./images/smilies/icon_lol.gif)
I understand that sentiment. I actually wrote the code to pull from the JSON feed whilst working on this update... and when I move to the JSON feed I'll remove the value for the psummary url in the preferences since the JSON feed is equivalent to the psummaryC. Didn't want to make those preferences and UI changes right now. I wanted to do this quickly and the tweak to get the new psummary html working was simple, so I went with it.
The bottom line with me and supporting HFM is the fact that I have a family now with three grade school children. Between work, the wife, and the kids... I simply don't have the time to work on this project like I did years ago. That said, I want HFM to continue and be a viable tool for the community. I have plans to rework my build process and tooling then move the code to GitHub where others can more easily contribute.
Here's the primary list of updates I'm planning in the near-ish term... in no particular order.
v7 client interface speed (partial rewrite?)
WU History Export (csv, others?)
option to use STARTTLS. gmail seems to require it on port 587.
Right justify PPD and Credit columns
Move benchmark data to SQLite
Core17 and Core18 version detection
Remove upper limit on WU History page size (currently 1000)
Add basic Fold/Pause/Finish contols for v7 slots
Use the psummary JSON feed (remove psummary html preference)
Update psummary compatibility (maybe use the JSON version)
Thanks for the support everyone! Nice to know there's a lot of you guys out there still rockin' HFM.
![Very Happy :D](./images/smilies/icon_biggrin.gif)