Use case cookbook
This is the basic Cookbook app. I will be the guinea pig for it; the theory is that it will replace the existing Waks Family Cookbook. It should be capable of everything in there.
This should probably be an ancestor App of the Use Case Cooks guild cookbook; think about how that works structurally.
This is the motivating Use Case for several features, including multi-column layout and units of measure. It may be the first Use Case that uses Tagging.
Ideally, this should be able to automatically scale up a recipe, to change the number served. (With caveats that not everything scales perfectly.)
I'm finding that I'm also going to need a scriptlet button, that is simply "Add this recipe to my Cookbook", for all those times when Kate sends me a link. The trick here is going to be creating a general concept of scriptlet buttons, so that any App can define its own.
-
Feature -- Units of Measure: The system should be smart about units, and understand concepts like Volume, Weight and Time. To scale up a recipe implies that the "number served" is a magic field, linked to certain measures, and it understands that Volume and Weight are implicitly "per n people".
-
Feature -- Tagging: Although Use Case Cooks will use Tags far more, this at least wants to be able to tag for things like App/Entree/Dessert, as well as more free-form tags like Pizza or Soup.
-
Feature -- Multi-Column: Ingredient lists are one of the most obvious places where I really want to be able to render a List in multi-column. This should be implemented in a general way in QL.
-
Scriptlets: So that I can just press a bookmark/button in my browser, from a page showing a recipe, and have the outline of that recipe get added to my Cookbook.