Cookbook/ Recipe Applications

Perhaps, when designing the program, I should keep in mind that it might build up to connecting online. Sharing recipes is caring.
 
Telkomisaloser said:
Maybe include level of difficultly for each recipe (E.G. Beginner, Novice, Professional )
Also include a "time required" feature
Click to expand...

Well, they will be in there. But I see that as standard protocol. :rolleyes: So I didn't bother mentioning them
 
foozball3000 said:
/Updated the list of features

C'mon guys. I need more user stories/ideas!
Click to expand...

That feature list is going to keep you really busy for a long time.... :D

How about an OCR feature where I can scan my till slip from Pick & Pay/Spar/Checkers/wherever and it automatically updates the stock items?
 
dequadin said:
That feature list is going to keep you really busy for a long time.... :D

How about an OCR feature where I can scan my till slip from Pick & Pay/Spar/Checkers/wherever and it automatically updates the stock items?
Click to expand...

Wanna bet? ;) Proper design means that the others will fall right in place. Most of the features are depending on the database system. I'm good at that, and I'm brilliant in designing software. Once the design is up, and the base version is working (the skeleton), it will grow easily.

But the items scanning idea can work... I'll keep it in mind. But it will take a lot of effort to make it user friendly.
 
foozball3000 said:
-And a feature for indecisive people (like H_C), so you just pick: "I want something... That I like/New/Quick/Daring... ect.
Click to expand...

:o

uhm, I can't really contribte to this discussion, as most of the stuff said in this thread just totally goes over my head.

It would be nice if it could be a separate pc that you can mount on the kitchen wall (but still connect up to your pc for updates, new recipe downloads etc). But it must be sealed, so if it does get full of butter finger prints, it can be cleaned easily :p

But seeing as it'll only be a program, it must be user friendly. So even if I have a blonde moment, I should still know what to do. :o Nice big picture icons :p (just to make it look nice for us women) And adding new recipes must be easy to do.

And it better not have any bugs. Nothing worse than getting that message: this program has encountered an error and needs to close :mad:
 
what about adding a function that warns you when certain stock is low (maybe only 2 left) and you need to buy more?
 
and how about you have a feature to work out a month's worth of meal times? But with the option to swop it around. Say for instance today is spaghetti bolognaise, but instead you want to make meatballs, mash and sauce and veggies. I must be able to swop it around and the program must keep track of it...
 
Hot_Chocolate said:
and how about you have a feature to work out a month's worth of meal times? But with the option to swop it around. Say for instance today is spaghetti bolognaise, but instead you want to make meatballs, mash and sauce and veggies. I must be able to swop it around and the program must keep track of it...
Click to expand...

That falls in line with the menu idea. Or, well, that's the point of it. :)
But that's a really nice way of phrasing it.
 
FYI a touch screen 19" is about R2000/R3000. So, setting one up for the kitchen can work great.
 
Might b handy to add function that shows u which substitutes to use when cooking for vegeterians, etc.
 
Last edited:
Good news! I've started building it's database. But version one will be quite basic. But that's the idea behind any version one. I'll see how it goes as I keep building.
 
I'm having a hard time designing the way that you input the recipes. Any ideas?
 
foozball3000 said:
I'm having a hard time designing the way that you input the recipes. Any ideas?
Click to expand...

1) Have a standard (expandable) input form with a fixed format for ingredients.
2) Have a standard (expandable) input form with a fixed format for the method.

i.e. all ingredients should generally take the form
<quantity> <ingredient>
e.g.
<1 Tsp> <salt>

and all method instructions should generally take the form
<operation> <operand> <duration>
e.g.
<Beat> <egg whites> <until they hold their peaks>
 
I like your thinking, but that type of input will be way too manual and slow to handle bulk recipies. I have over 200 from Jamie Oliver alone..

But perhaps I'm starting from the wrong end. The means of suggesting recipies and scheduling a eating plan is way more important than displaying the actual recipe. (For now)
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X