[clug] Linux recipe management

[Daniel Pittman]

David Cottrill <cottrill.david at gmail.com> writes:

> Perhaps a Wordpress plugin? Was going to suggest Drupal but that seems like
> overkill.

I keep wondering if either of these is a good solution, but what I really want
the software to do really exploits the weaknesses of these tools.  I don't
want a time-linear set of recipes, even with tagging to attach categories to
them.

I want something that supports a *lot* of structured information about the
recipes, has a deep understanding of their content, and can do helpful things
like scale recipes, provide ingredient substitution information, search by
"what can I cook with what I have", and similar rich interactions.


This isn't a bad suggestion, though, and I could probably turn Drupal to the
purpose if I wanted to invest enough time (and PHP code) into building plugins
and integrating them.  I mostly lost heart at "PHP" though. :)

> Has anyone persisted with KRecipe?

Nope.  It was sufficiently poorly matched to my expectations that my three
trials have all ended in failure.  It just doesn't work the way I want it to.


> As a chef I can honestly say the most important thing is getting the
> ingredient list easy to navigate. Eg: 'plain flour' is impossible to find (I
> always search for flour under 'F') whereas 'flour, plain' is easier.

*nod*  When I talk about custom output, what I want is to have it generate
something in a few experimental styles, as well as the ones that I find
acceptable.  This is because, as you say, sensible access to the ingredients
in pretty crucial to the process.

        Danie
-- 
✣ Daniel Pittman            ✉ daniel at rimspace.net            ☎ +61 401 155 707
               ♽ made with 100 percent post-consumer electrons
   Looking for work?  Love Perl?  In Melbourne, Australia?  We are hiring.