A Cook's Books - 1.2.8recipe management & nutrition analysis tool |
|
||||||||||||||||
|
|||||||||||||||||
Feedback Summary:
| This Version: | |||||
| Overall Rating: | Not rated (0.0) | Features: | Not rated (0.0) | Support: | Not rated (0.0) |
| Ease of Use: | Not rated (0.0) | Quality / Stability: | Not rated (0.0) | Price: | Not rated (0.0) |
Key to Types of Feedback:
Reviews
Troubleshooting
Usage Tips
Developer Notes
Commentary
Featured Reviews
Switching from A Cook's Book 



- Version: 1.2, 11/11/2007 11:07AM PST
(2 of 2 users found this comment useful)
walt7
Continues to get only better! 



- Version: 0.9.24, 6/19/2006 03:12AM PST
(4 of 5 users found this comment useful)
thaiwestHaving been an avid MasterCook Mac user in years past, I had more than 10,000 recipes on my Mac. A Cook’s Books imported them all almost seamlessly. It removed the shear panic I was experiencing with the discontinuation of MasterCook for OS X!
A Cook’s Books provides some features MasterCook never thought of and misses a few MasterCook had. Those that are missing, I do not notice.
For any serous recipe collector, from the person who only wants a reliable data base for their recipes to the professional chef who needs every detail of a recipe available and readable, A Cook’s Book handles the need.
I must wonder... when will A Cook’s Books get out of being “beta?” It seems in all respects to me, to have already moved out of the beta stag and in to the “released” versions... but, I am not privy to the “to do” list of the developer.
One thing I’d like to see attention given to is the On Line Help. Because of this I give the “Support/Documentation” field less than excellent.
Reply to developer - Version: 0.9.23, 6/6/2006 09:21AM PST
(7 of 10 users found this comment useful)
kalstaIn relation to your repeated assertions that I misrepresented your product, I would just say this ... You are the developer -- I won't pretend to understand your software as well as you do. But that's the whole point to user feedback -- if a user reports having problems using your program, before jumping to the conclusion that they are either (a) lying, or (b) an idiot, try to understand the reasons why they had trouble, and consider how the software (not the instruction manual) might address these issues -- be they real or perceived in your view. Like I said before 'If I have overlooked any feature, it's possibly an indication that the feature was difficult to find or unintuitive to use'...
I'll respond specifically to some of your points:
>Me: The main navigation tabs read vertically — this adds nothing to the interface and impairs readability
>Comment: Lot's of of cookbooks have side-tabs.
And lot's don't have side-tabs -- who cares? The point is, there is absolutely no good reason why the tabs need to be vertical when it makes them more difficult to read.
>Me:'Print' shouldn't be one of the main navigation tabs
>Comment: Why not? This allows the user to view/edit the page(s) prior to printing. You can also save the resulting text in a number of formats.
It's a question of logical association of interface elements by proximity. The print button simply doesn't belong in a group alongside 'Reference', 'Planner' and 'Recipes' (in my opinion!)
>Me: The program doesn't make it at all obvious that the user has to manually save cookbook file to work with recipes (Save dialogues come up at various times if you have not done this, with no explanation as to why, or what is being saved.)
>Factually incorrect: The save dialog comes up in exactly one circumstance: when a user clicks the 'Save Changes' button and there's no active cookbook open.
No, not 'factually incorrect'. I just tested the product again briefly, and yes -- it gave me a 'save as' dialogue after deleting a recipe (I selected cancel) and then again after I added a new recipe.
I stand by what I said. The version I tested gave me save dialogues on a number of occasions and at first I had no idea what I was being asked to save. It is not immediately obvious that the program works with multiple documents (called cookbooks) which you have to manually save -- and I don't recall this confusion with the other software I tested. (I suspect most simply maintain a single database per user -- much like iTunes, iPhoto, etc.) Familiar applications that are geared more towards document creation, like Word, Photoshop, etc, seem to manage this without the confusion that I first felt in your program. At very least, you could title the window of a new unsaved document 'Untitled.acbk' or similar.
>Kalsta didn't follow the Getting Started instructions (Help Menu or Help pdf) that suggest creating a cookbook to work in.
You're darn tootin I didn't! Nor did I for the other products -- aside from features, I was most interested in comparing ease of use and the intuitiveness of each interface. The best designed products tends to require less explaining. I use a myriad of programs on a daily basis to accomplish tasks far more complex than recipe management, and have done so for over 10 years on the Mac. If I can't figure out how to drive this baby without consulting a manual, the interface probably needs improving. If that sounds arrogant, remember: a good user interface accommodates the way people work, not the other way around.
>Me: Editing and creating recipes is not intuitive
>Factually incorrect: Editing and creating recipes is quite intuitive.
Factually incorrect? How can my opinion of what is intuitive be 'factually incorrect'? It's my opinion!
>Me: e.g. Course categories should pop up or auto-fill when you enter this field or start typing — you have to try and remember what categories you use.
>Comment continued: A Cook's Books doesn't use popups for recipe meta-data like Author, course, region, etc. For the most part I don't see people having the issue Kalsta alludes to.
No? They're all just text fields. What's to say I won't accidentally give a recipe a rating of '8' (meaning 8 out of 10) one day, '80%' another, or even 'Good' another? What if I call the course 'dessert' one day and on another 'supper', or 'sweets', or 'desert' (misspelled)? The usefulness of such data is questionable.
>Plus, forcing users to use popups slows down recipe entry.
Then use auto-fill in the text fields.
>Me: Drop down lists of ingredients don't jump to the item you have currently selected (they take you back to the start of the list)
>That is standard behavior for a drop-down box. I don't know why Apple chose that behavior.
Yes, that is weird if that's how Apple has made it. Even standard drop down menus in HTML forms start at the currently selected item when you click on them. Standard drop downs also allow you to start typing to jump to another word, whereas the drop-down ingredient box does not seem to allow this.
>Me: Individual serve scaling is not intuitive — number of servings not visible in main window
>Factually incorrect: The Individual serving is listed in the title bar like this: My Cookbook: African Peanut Soup - Serves 4.
You're right -- there it is. Was it there in version v.9.19? (which I can't test now) -- perhaps I just missed it.
>Me: Nutritional information for each recipe is rendered useless when your ingredients are not included because 'the unit of measurement can't be converted' or 'not found in the food list'.
>Comment: This is true: if A Cook's Books can't find the food, it can't find the nutrition. I'm curious how that's a criticism.
I do agree it's a good feature. I simply pointed out the limitations of the feature as quickly evident in even some of the sample recipes provided.
>You don't even need to look at the nutrition results to know that has occurred because A Cook's Books provides visual feed back right in the ingredient list. (Preferences:Auto-fill:Ingredients:Tint when not fount)
Perhaps I'm missing something -- I have 'tint' turned on, but I don't see any obvious tinting in the ingredient list.
>Comment continued: Nutrition is not an easy thing to do. Plenty of programs let you look up a food and see the nutrition, but very few attempt to calculate recipe nutrition the way A Cook's Books does. Getting accurate nutrition from A Cook's Books does require setup and effort, but those interested in accurate results typically don't mind the effort.
Yes, I agree that yours is quite an ambitious implementation -- and useful if people can make it work for them.
>Me: If you quit application before saving your planner, no warning is given and the data appears to be lost.
>Comment: A known issue with a fix planned for the near future
Glad to hear it.
Most Recent Replies: View All 4 Replies
- Reply to developer (1 replies)
Comments on previous review - Version: 0.9.23, 5/21/2006 01:30PM PST
(2 of 4 users found this comment useful)
TopcatGood:
Filtering/classification with 'quick list'
Individual serve scaling
Meal planner
Shopping list
Nutritional database
Comment: How about:
A Pantry (food and non-food), Extensive,
Recipe Import options (including a Text import Service),
easy conversion between Metric and US Standard measurements,
and the ability to use recipes as ingredients.
Bad:
The main navigation tabs read vertically — this adds nothing to the interface and impairs readability
Comment: Lot's of of cookbooks have side-tabs.
'Print' shouldn't be one of the main navigation tabs
Comment: Why not? This allows the user to view/edit the page(s) prior to printing. You can also save the resulting text in a number of formats.
The program doesn't make it at all obvious that the user has to manually save cookbook file to work with recipes (Save dialogues come up at various times if you have not done this, with no explanation as to why, or what is being saved.)
Factually incorrect: The save dialog comes up in exactly one circumstance: when a user clicks the 'Save Changes' button and there's no active cookbook open. A Cook's Books can be set to open a default cookbook, or you can use the File>Open menu to open one. Kalsta didn't follow the Getting Started instructions (Help Menu or Help pdf) that suggest creating a cookbook to work in. Failing that, A Cook's Books does prompt you to save the cookbook the first time you save a new recipe.
Useful information about each recipe, which should be included in the main window, is hidden away in drop-down sheets which are accessed via a menu command — not very efficient! (Although I since discovered that preferences allow you to change this to an 'Inspector' window which can be visible at all times.)
Comment: People work in different ways, some people want to see every bit of info about a recipe all the time. Other people just want to see the raw recipe. A Cook's Books doesn't force you into either mode. Instead, it take the flexible approach of allowing the user to choose. (By the way, there is also a keyboard short-cut for the Recipe Info sheet.)
Editing and creating recipes is not intuitive: e.g. Course categories should pop up or auto-fill when you enter this field or start typing — you have to try and remember what categories you use.
Factually incorrect: Editing and creating recipes is quite intuitive. Use cmd-n or Recipes>New Recipe to start a new recipe. That causes the Recipe Info sheet to come out. Fill in what you want and close it, then fill in ingredients, instructions, and notes if you have them. In fact, entering ingredients in A Cook's Books is easier and faster, by far, than any other program out there (I've tried most of them). Editing is not intuitive? Double-click the recipe tile, double-click an ingredient, use the Recipe>Edit Recipe menu.
Comment continued: A Cook's Books doesn't use popups for recipe meta-data like Author, course, region, etc. For the most part I don't see people having the issue Kalsta alludes to. Plus, forcing users to use popups slows down recipe entry.
Auto-fill on ingredients sometimes works, sometimes doesn't.
Factual incorrect: Ingredient auto-fill works if it's turn on in preferences. This feature has been in A Cook's Books for a couple of years. Being a core part of recipe entry, problems would have been reported if they existed. There have been no reports of problems.
Drop down lists of ingredients don't jump to the item you have currently selected (they take you back to the start of the list)
Factually incomplete Type a letter or two so the drop-down makes a guess. Then press the down arrow and the list jumps right to the spot. Plus, you have the speed benefit of not needing to use the mouse. If you click the arrows, the list opens at the top of the list. That is standard behavior for a drop-down box. I don't know why Apple chose that behavior. A guess would be, if a person is going to take their hands off the keyboard to click the arrows they want to start at the top of the list.
Individual serve scaling is not intuitive — number of servings not visible in main window
Factually incorrect: The Individual serving is listed in the title bar like this: My Cookbook: African Peanut Soup - Serves 4.
Nutritional information for each recipe is rendered useless when your ingredients are not included because 'the unit of measurement can't be converted' or 'not found in the food list'.
Comment: This is true: if A Cook's Books can't find the food, it can't find the nutrition. I'm curious how that's a criticism. You don't even need to look at the nutrition results to know that has occurred because A Cook's Books provides visual feed back right in the ingredient list. (Preferences:Auto-fill:Ingredients:Tint when not fount)
Comment continued: This is true: if A Cook's Books can find the food, but the unit of measure can't be converted, the nutrition of the food can't be used. A simple example: 1 large egg. The nutrition database certainly has egg in it. The problem is USDA uses 1 cup and 1 Extra Large as conversion points. The process needs a weight reference for a large egg and it doesn't exist. A Cook's Books provides a solution. You can create new foods and supply a conversion point. Since I use this example in the Help documents I happen to know that an extra-large egg is 58 grams and a medium egg is 50 grams. By the way, I count this as a strength of A Cook's Books. You can completely customise the nutrition database.
Comment continued: Nutrition is not an easy thing to do. Plenty of programs let you look up a food and see the nutrition, but very few attempt to calculate recipe nutrition the way A Cook's Books does. Getting accurate nutrition from A Cook's Books does require setup and effort, but those interested in accurate results typically don't mind the effort.
If you quit application before saving your planner, no warning is given and the data appears to be lost.
Comment: A known issue with a fix planned for the near future. Kalsta didn't happen to mention that you can save an individual day menu, or a full week of menus, or a full month of menus (people really do use it). Individual days in the menu can have an unlimited number of recipes in it. Plus, you can generate shoppings lists for any number of weeks in the planner. It's a pretty cool feature that some institutional users really love.
Shopping list is buggy — when I first generated shopping list form weekly planner, units of measurement were appearing in the ingredient column with enormous quantities beside them. When I generated shopping list again, the problem was gone.
Comment: As the developer of A Cook's Books I have a pretty good reputation for producing a stable program and fixing issues quickly when they do crop up. I personally use the program and produce shopping lists practically daily. I haven't experienced this issue, and I don't recall any user reports of this nature. That being said, any program can suffer an occasional hiccup, including A Cook's Books.
Most Recent Replies: View All 1 Replies
Feature rich (Review and product comparison) 



- Version: 0.9.19, 4/25/2006 08:53AM PST
(12 of 18 users found this comment useful)
kalstaGood:
- Filtering/classification with 'quick list'
- Individual serve scaling
- Meal planner
- Shopping list
- Nutritional database
Bad:
- The main navigation tabs read vertically — this adds nothing to the interface and impairs readability
- 'Print' shouldn't be one of the main navigation tabs
- The program doesn't make it at all obvious that the user has to manually save cookbook file to work with recipes (Save dialogues come up at various times if you have not done this, with no explanation as to why, or what is being saved.)
- Useful information about each recipe, which should be included in the main window, is hidden away in drop-down sheets which are accessed via a menu command — not very efficient! (Although I since discovered that preferences allow you to change this to an 'Inspector' window which can be visible at all times.)
- Editing and creating recipes is not intuitive: e.g. Course categories should pop up or auto-fill when you enter this field or start typing — you have to try and remember what categories you use.
- Auto-fill on ingredients sometimes works, sometimes doesn't.
- Drop down lists of ingredients don't jump to the item you have currently selected (they take you back to the start of the list)
- Individual serve scaling is not intuitive — number of servings not visible in main window
- Nutritional information for each recipe is rendered useless when your ingredients are not included because 'the unit of measurement can't be converted' or 'not found in the food list'.
- If you quit application before saving your planner, no warning is given and the data appears to be lost.
- Shopping list is buggy — when I first generated shopping list form weekly planner, units of measurement were appearing in the ingredient column with enormous quantities beside them. When I generated shopping list again, the problem was gone.
This program has tried to incorporate all the right features. In fact it's probably the most fully-featured program I have tested. What a shame it's not easier to use. If a user-friendly interface is more important to you and you can do without the meal planner and nutritional database, you might consider Connoisseur instead. Keeping in mind that A Cook's Books is still beta software, it shows lots of promise.
The programs I tested, roughly in order of preference were:
- Connoisseur 1.1.7 (great interface)
- A Cook's Books 0.9.19 (feature rich)
- Shop'NCook 3.1 (includes nutritional database)
- Organized Gourmet 1.2 (calendar based meal planning)
- MacGourmet 1.1.7 (attractive interface, includes wine notes)
- iCuistot 1.1.1 (includes nutritional database — sort of)
- Kitchen 1.0 (simple interface)
- Yum 0.7.8 (simple recipe manager)
- Measuring Cup 1.1.1 (simple interface)
- CookWare Deluxe 2.1 (includes a very basic meal planner)
- The Computer Cookbook 3.1
Note: There are many others that I didn't test at all because they looked less promising, based on their descriptions and other people's reviews. There is one commercial product (TheRecipeManager) I refuse to test because of the developer's crazy policy of buy before you try. While I have tried to give a fair and honest appraisal of each product, I don't pretend that each review is exhaustive or totally without error. If I have overlooked any feature, it's possibly an indication that the feature was difficult to find or unintuitive to use — so in any case the reviews are a valid record of my opinion and individual experience.
Otay buckwheat 



- Version: 0.9.14a, 8/31/2005 11:07PM PST
(2 of 9 users found this comment useful)
Hockpooh777
Open says me - Version: 0.9.14a, 8/31/2005 10:59PM PST
(0 of 7 users found this comment useful)
Hockpooh777Most Recent Replies: View All 1 Replies
Looks Good... - Version: 0.9.13, 8/7/2005 07:50PM PST
(0 of 1 users found this comment useful)
cntrytwist
A Tremendous Application 



- Version: 0.9.11, 6/26/2005 08:38PM PST
(2 of 2 users found this comment useful)
victor_lipp
Support email issue... - Version: 0.9.9a, 5/22/2005 04:49AM PST
(1 of 1 users found this comment useful)
Topcat
At the time of purchase, it was very promising, and still is, as long as you don't mind the interface. Many people do like it, and claim it sheds the "cutsey" goodness that is Aqua and eyecandy and all that. That's where it loses me now. The main window seems like nothing but a regular program's preference pane turned on its side. Check it out. Go to Mail, open preferences, click on Accounts. There's your A Cooks Book interface minus the toolbar along the top and the list along the left side. And of course it's right side up instead of on the side. I always put up with it because I was a lifetime licensee, and it is a solid program.
Since Leopard, the annoying tabbing issue caused me to look at other options out there. I just finished up trying out many listed here and MacGourmet has stole my heart. I used it for about 5 minutes and I immediately fell in love with it. It is very Mac like, in that it is visually just like using Mail, iTunes, iCal iLife and iWork (all programs which I enjoy using).
Is adding a toolbar eyecandy? I don't know. But it sure would be useful in A Cook's Book to enter a new recipe instead of having to choose it from the menu or keyboard shortcut. When I compose a new message in Mail, I don't use the keyboard shortcut to initiate it.
So, farewell A Cook's Book for now. You have served me well in the past, and I will continue to look in on you time to time. But I have found something I like better right now, and you know what I am looking for should you ever want to bring in other users like me.