emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ken Mankoff <mankoff@gmail.com>
To: Xebar Saram <zeltakc@gmail.com>
Cc: Erik Hetzner <egh@e6h.org>,
	Fletcher Charest <fletcher.charest@gmail.com>,
	org mode <emacs-orgmode@gnu.org>,
	Robert Horn <rjhorn@alum.mit.edu>
Subject: Re: org-cook
Date: Mon, 17 Mar 2014 10:34:55 -0400	[thread overview]
Message-ID: <m2y508evw0.fsf@gmail.com> (raw)
In-Reply-To: <CAOQHXPofjLsg0V-fYwOuCnsRXt8JX-WBQgOwGW6gO9AthYHDow@mail.gmail.com>

Hi,

This isn't directly related to Org, but I'll mention it anyway since
people are discussing quantities and "scale" for their
recipes. Various programming languages have "physical units" packages
that can make working with units quite fun. I use the python
"Quantities" package
http://pythonhosted.org/quantities/user/tutorial.html . It lets you
define custom quantities such as how many grams of butter are in a
stick, etc. A wrapper to this would let you convert Org recipe
shopping lists from units of "g" and "teaspoon" to units of "sticks"
and "fluid oz".

  -k. 


On 2014-03-17 at 10:26, Xebar Saram wrote:
> thank you all for the great answers
>
> Fletcher, your idea sounds great, but why not use  org tables as people
> suggested for ingredients. ive started using it yesterday and im very
> pleased, in example:
>
> *** COOK Pancakes    :American:
>
>
>     :PROPERTIES:
>     :Source: TV
>     :Serves:
>     :Time:
>     :Rating:
>     :Fav:
>     :END:
>
>     | Quantity | scale | Ingredient    | Instructions |
>     |----------+-------+---------------+--------------|
>     |        8 |       | eggs          |              |
>     |        1 | liter | milk          |              |
>     |      350 | g     | butter        | melted       |
>     |      730 | g     | flour         |              |
>     |       90 | g     | powderd sugar |              |
>     |       60 | g     | baking powder |              |
>     |       10 | g     | salt          |              |
>
> _*Directions*:_
>
>
> best
>
> Z
>
>
> On Mon, Mar 17, 2014 at 4:22 PM, Fletcher Charest <
> fletcher.charest@gmail.com> wrote:
>
>> Hello everyone,
>>
>> Since we are on this subject, are you aware of any package that would make
>> an 'automatic' shopping list based on recipes? My idea was to record
>> recipes in this format:
>>
>> * Name of the recipe          :tag:
>>
>> 1) Step one.
>> 2) Step two.
>> 3) Step three.
>>
>> :PROPERTIES:
>> :ingredient_1: quantity
>> :ingredient_2: quantity
>> :ingredient_3: quantity
>> :END:
>>
>> Tags could be anything, be mainly things like 'breakfast', 'main course'
>> or 'dessert'. Then, with the point on the headline, (in the file buffer or
>> in the agenda buffer), you could call a function that would add the
>> ingredient to a list, or increment its quantity if the ingredient is
>> already there. Maybe a function to add a random number of recipes (through
>> a filter or not) to the shopping list would be nice too, if you don't know
>> what to cook in a particular week.
>>
>> I'm planning to do this but my Elisp-fu is not great... Any tips of how
>> implementing this? Are lists a good data structure for stocking the
>> shopping list, before dumping it in a buffer?
>>
>> FC
>>
>>
>> On Sun, Mar 16, 2014 at 1:40 AM, Robert Horn <rjhorn@alum.mit.edu> wrote:
>>
>>> I also use tables, and have one big recipe.org file.  I considered
>>> ingredient properties, etc., but ended up just text and find recipes by
>>> using simple searches.  They look like this:
>>>
>>> * Texas Skillet Corn Bread
>>>
>>> | Ingredient             | Quantity | Instructions    |
>>> |------------------------+----------+-----------------|
>>> | Bacon drippings or oil | 1/4 cup  |                 |
>>> | Yellow CornMeal        | 1 cup    |                 |
>>> | All Purpose Flour      | 1 cup    |                 |
>>> | Salt                   | 1/2 tsp  |                 |
>>> | Baking Power           | 1 tsp    |                 |
>>> | Baking Soda            | 1 tsp    |                 |
>>> | Sugar                  | 1 tbs    | optional        |
>>> | Buttermilk             | 1 cup    |                 |
>>> | Eggs                   | 2        | slightly beaten |
>>> |------------------------+----------+-----------------|
>>>
>>>   1. Heat drippings in iron skillet
>>>
>>>   2. In large mixing bowl, mix cornmeal, flour, salt, baking x, and sugar.
>>>
>>>   3. Add buttermilk and stir rapidly.
>>>
>>>   4. Add eggs and mix
>>>
>>>   5. Add drippings
>>>
>>>   6. Pour into skillet, cover, and cook on low heat until lightly
>>>      browned and almost cooked through.
>>>
>>>
>>>
>>

  parent reply	other threads:[~2014-03-17 14:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-15  7:24 org-cook Xebar Saram
2014-03-15 17:38 ` org-cook Erik Hetzner
2014-03-15 18:03   ` org-cook Xebar Saram
2014-03-15 18:18     ` org-cook Erik Hetzner
2014-03-16  0:40       ` org-cook Robert Horn
2014-03-17 14:22         ` org-cook Fletcher Charest
2014-03-17 14:26           ` org-cook Xebar Saram
2014-03-17 14:30             ` org-cook Fletcher Charest
2014-03-17 14:34             ` Ken Mankoff [this message]
2014-03-17 14:52               ` org-cook Erik Hetzner
2014-03-15 18:25     ` org-cook Alan Tyree

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2y508evw0.fsf@gmail.com \
    --to=mankoff@gmail.com \
    --cc=egh@e6h.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=fletcher.charest@gmail.com \
    --cc=rjhorn@alum.mit.edu \
    --cc=zeltakc@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).