[directory structure hans@fugal.net**20051012174744] [the beginnings of a model hans@fugal.net**20051012174834] [view/qt initial hans@fugal.net**20051012212743 This is just the .ui files, the makefile, and the qt.rb from the old neelix. qt.rb will need major reworking, or maybe I'll just start from scratch. ] [+/- hans@fugal.net**20051013014017 Added +/- buttons for adding and deleting ingredients, a la OS X. ] [more gui tweaks hans@fugal.net**20051013023857 Just refining stuff. I really should stop playing with designer and get to coding. :) ] [tweaks hans@fugal.net**20051013024726] [testing framework hans@fugal.net**20051013032008] [execution framework hans@fugal.net**20051013032112] [test framework hans@fugal.net**20051013150113 Set up a versatile test framework based on the rails one (but not so complicated), and learned the basics of Rake in the meantime. ] [rake ui hans@fugal.net**20051013163935] [model associations hans@fugal.net**20051013163949 Jacob noticed we needed has_many :ingredients. Oops :-) He also noted that food and measure don't really belong_to ingredient, which is true. I don't think any of the AR association methods really fit, so after reading the API docs I decided it looks like has_one should still work without a reciprocating belongs_to, so that's what we'll do. ] [test fixtures and some meaningful tests hans@fugal.net**20051014025722 Note that these tests probably will not pass without the forthcoming model changes. ] [model associations figured out hans@fugal.net**20051014025920 Thanks again to minam for helping me wrap my brain around AR's funny association names. Here's an extract from our conversation: minam: okay, the belongs_to thing can be misleading. It just indicates a particular style of relation. if A belongs to B, then A has b_id. If A has_one B, then B has a_id minam: don't let the english mess you up :) Then he gave me this link which was invaluable. Actually I saw this page before, but when I read it the Example image didn't load, and that made all the difference. http://ar.rubyonrails.com/classes/ActiveRecord/Associations/ClassMethods.html ] [path stuff hans@fugal.net**20051014184157 Path stuff is always a pain. I've decided we'll want to allow people to create new "cookbooks" (sqlite databases) and we'll want to populate these new dbs with the contents of data/create.sql. But of course after installation, what is that? And then, if you code for the installed case what about the uninstalled (testing) case? This code deals with that in I think the best way. Apparently rubygems doesn't use Config::CONFIG['datadir'] so that's another bridge to cross if/when we gemify it. I'd like to think that most people will be happy to download, untar, and run, though. For now, run it using "rake run" (or leave off the run) ] [autopopulate db hans@fugal.net**20051014193726 We can now (with Neelix#open) create a database if it doesn't exist already. We also mkdir -p ~/.neelix, and did some refactoring dealing with configuration, and kept windows in mind for the future, although we don't do the windows code yet. ] [populate shelf hans@fugal.net**20051016195516 It's a modest beginning, but it's a beginning. ] [add/delete recipes hans@fugal.net**20051017050633 But what do you call a recipe without ingredients? We've got recipe creation (but doesn't save to the db, need to decide where to call save()), and deletion (destroy however does apply to the db so we're ok there). You also see the shelf and counter are dancing nicely together, except no ingredients yet. Changing things on the counter does nothing yet. ] [populate ingredients hans@fugal.net**20051017135533 We can now add ingredient rows (but no ingredient added to the table) and see the ingredients for a recipe. Still thinking about the best interface for the ingredients table. Tell me your ideas. ] [more flexible than rake run hans@fugal.net**20051018173249 although I'd be happy to move this back into rake if I could figure out how to pass parameters via rake. ] [readme hans@fugal.net**20051023225840] [minor hans@fugal.net**20051023225846] [hunk o' gui work hans@fugal.net**20051030033849 Now recipes work, except for the ingredients table. Add recipe works too (but not delete yet). Next up is the ingredients table, delete recipe (that was mostly an oversight I just realized I had forgotten), then create/open/save as, and then finally the menus. Then will be the fun part of adding meal plans and calendar stuff... ] [ingredients table hans@fugal.net**20051030220251 This is a big one. Lots of GUI progress, not the least of which is that ingredients table working just exactly as we had always dreamed. It's beautiful. It might make you cry. Lots of interesting tricks in this one, including the obligatory 'class << something' trick. Lots of mind-numbing nitty-gritty details that are likely to hide an infestation of UI bugs, too. ] [oops hans@fugal.net**20051030221312] [menus and refinements hans@fugal.net**20051031011736 Menus work as they should, and various UI refinements. I'm happy to say that this is the most functionaly UI neelix has ever had! Break out the smarties cigars! ] [db creation works hans@fugal.net**20051031020129 I kind of wanted to do this in AR, but pragmatism won out when AR wasn't making it easy. ] [tweaks hans@fugal.net**20051031020230] [osx bundle hans@fugal.net**20051107034344] [logging hans@fugal.net**20051107232644] [crash bug hans@fugal.net**20051107232711] [more saving hans@fugal.net**20051107235037] [switch to directions tab when changing recipes hans@fugal.net**20051107235135] [von cleaned up the icon hans@fugal.net**20051113202904] [new icon hans@fugal.net**20051113203433] [todo hans@fugal.net**20060523161145]