Gourmet

A Few Suggestions

Asked by jdmark

1. The adding and editing recipe tabs need to be all in one window and not in tabs. That is preventing me from using this software due to the fact that having tabs *greatly* slows down my ability to input recipes.

2. A file format that includes the ability to embed photographs so they are not lost.

  I decided, after hours of reading, to use Evernotes to store recipes. It supports automatic syncing (which isn't that big of an issue if you save the files to the cloud), a desktop program for editing (there is software that emulates Android and even allows syncing to Google Play.), and I can import/export my Evernotes for other programs to use. The only issue is everything isn't broken down into sections and I won't be able to scale my recipes up and down which is going to be a big issue while I'm at work. Time is money and if it is spent scaling recipes using a calculator I've wasted 5-10 minutes per recipe.

Question information

Language:
English Edit question
Status:
Answered
For:
Gourmet Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Thomas M. Hinkle (thomas-hinkle) said : 		#1

JDMark,

Not entirely sure why tabs are such an issue, but if you'd prefer one giant scrolling window of editing stuff to the tabbed on we have now, that would be pretty trivial to implement as a plugin, or simply by changing a few lines in a few files in your own branch.

You could also just type your recipes as text and then use the plain text import to import them much more quickly if you simply want super-fast unstructured input.

Revision history for this message
Bernhard Reiter (ockham-razor) said : 		#2

JDMark, Tom,

1. I personally also feel that an interface that allows editing a recipe with fewer clicks would be desirable. What about modifying the recipe card display as to allow in-place editing of the different sections (description, ingredients, instructions, notes) by adding a little pencil icon or so to each to switch between read-only and editing mode (as found e.g. in the GitHub issues tracker UI)? I think that such a change would make editing recipes feel much more light-weight, and would entail dropping the recipe editor window altogether. (I've posted this at https://github.com/thinkle/gourmet/issues/757, where we can have follow-up discussion.)

2. Embedding photos has been requested over at GitHub already. As a first step, we might enable adding multiple images to a recipe, which is also a recurring feature request.

Both modifications are somewhat complex to implement, though. I'm currently working on https://github.com/thinkle/gourmet/issues/712, which I hope will make for a simpler structure of some core components, and is going to take some more time. I'd like to finish that and release 0.18 (and possibly migrate to PyGI/Gtk+3 and Python 3, which are my 0.19 goals) before dealing with any (possibly large-scale) UI redesign ideas.

Can you help with this problem?

Provide an answer of your own, or ask jdmark for more information if necessary.

To post a message you must log in.