I’ve been going round and round on several options for the LambTracker® Desktop app.
Initial choices include Swing and Java FX. I had just about settled on Swing because I really don’t want to keep supporting Oracle. Then, there was using Cards or not as a structure.
We’re about to start our major sheep evaluation cycle. I’ve added most of the NSIP EBV data points into the database. Now I’m writing the queries to display the data along with the most recent evaluation.
Note: this blog post was originally posted on lambtracker.com and has been moved here for preservation. Some information may be outdated. We built our own EID reader to interface with our early LambTracker® system. Unfortunately, FCC rules make it so we can’t sell these homemade readers to our users, but we can teach you how
Lambing finished on July 3rd. I’ve now started going back over each module and working on the user interface issues and bugs we identified earlier this year.
We are now in the lull between batches of lambs. We had nine ewes left to go, but we’re down to eight now.
My focus is shifting to working on the desktop and cleaning up the mobile application.
Bug fixing of the Lambing module is going well. A few things took a bit of time to correct, but it’s all working as expected now. I do keep a running log on Twitter of most of the work on LambTracker®, as well as our farm status. I’ve added a follow button in case anyone wants a running commentary.
We’ve been using LambTracker® to document all the births during this lambing season. I’ve uncovered several bugs and a few workflow issues, but by and large, everything is working as planned.
The LambTracker® Lambing module encountered live sheep for the first time today. We had two sets of twins! We did uncover a few workflow issues.
The Lambing module went to feature freeze about a week ago, and I’ve since been working on bug fixes. As of yesterday, the main Lambing module and AddLamb activity are both working properly.
