Monday, May 7, 2012

Another day, another migraine

First off, I'd like to admit that I probably don't have a migraine. I do, however, have a headache that's been going on for at least a week and yesterday my eye started twitching. I've heard that stress can cause that, so figure at least I have a reason for feeling this lousy.

That being said, I am again hard at work on Chef Helper. I don't really know what I meant when I scheduled task number 5, so we'll just call it done in light of me getting closer to completion of the meal planning section. I've now got my UI to drill down to the level of Meals and Recipes and have realized I'll need to update the deletion scripts on the Meal Planner and Daily Planner as such:

  • If a meal plan is deleted, so is every daily plan associated with it and every meal associate with each of those.
  • If a daily plan is deleted, so is every meal associated with it.
  • If a meal is deleted, who cares. 
After an hour or so of work, I've got the code ready to accomplish each of these tasks. I've tested it a bit and it seems to work, but further testing/debugging will be needed down the line.

So I moved on to implementing the meal planner tab button logic. I've managed to come up with code to successfully save a recipe to the breakfast appetizer slot and update the tab. I've also managed to come up with code to successfully clear a recipe from the breakfast appetizer slot but I cannot seem to get the tab to update and I've tried a number of algorithms. For the time being, I'm just going to offload that work to another method and get all the other buttons working. Then I'll toy with that method and see if I can't get everything to refresh properly. What do you know, I found a workaround that works just as well without the overhead. I just set the associations on each daily plan as I updated it rather than trying to rebuild all the master lists from the database. 

And with that little bit of success, which has been copied to the other 34 buttons on the meal planner (yeah, that was a lot of copy/paste/update/pray there), I have completed the meal planner. Tomorrow work will begin on the randomizer logic and GUI. Hopefully that won't take more than a couple of days, and I'm taking Friday off to work on this thing. As you can see, that's followed by creating shopping lists which is followed by printing. Then the last step of the coding phase is to debug those pesky little errors on the recipe builder and Chef Helper will be done at last!



  1. Write the Recipe Builder update logic
  2. Write the Recipe Builder delete logic
  3. Write the HTML builder for Recipes
  4. Write the database interaction methods for the Meal, Meal Plan, and Daily Plan classes
  5. Update the meal planner tab based on the successes and failures of number 4
  6. Write the GUI logic for the meal planner tab (all three interaction methods)
  7. Write randomizer logic for meal plans
  8. Design GUI for meal plan randomizer
  9. Design GUI for shopping lists
  10. Design logic for shopping lists
  11. Design printer control for shopping lists and meal plans
  12. Debug remaining errors on Recipe Builder
  13. Write Capstone Project Paperwork and submit it.
  14. CELEBRATE!!!!!!!! (when I pass, anyway)

No comments:

Post a Comment