PDA Timer Hack
May 12, 2006 11:37 AM Subscribe
Would it be possible to turn an old PDA into a multi-item timer?
I work as a cook, and I was thinking of purchasing an Old Palm, or similar model and making it a timer. Everything on our line has to be finished-off in the oven, where there can be over a dozen items at once. In the back, we have two bakers ovens where we may have as many as 20 souffles going in at different times. The way I was thinking, was that if you could place something in the oven, enter the item's table number, then the time it is to come out. An icon (preferably the table number) would flash on the screen, with an accompanying sound/alarm. Also, since the screen can handle many icons, to show where in the oven each item is. Possible? And if so, for someone who's not all that program savvy?
I work as a cook, and I was thinking of purchasing an Old Palm, or similar model and making it a timer. Everything on our line has to be finished-off in the oven, where there can be over a dozen items at once. In the back, we have two bakers ovens where we may have as many as 20 souffles going in at different times. The way I was thinking, was that if you could place something in the oven, enter the item's table number, then the time it is to come out. An icon (preferably the table number) would flash on the screen, with an accompanying sound/alarm. Also, since the screen can handle many icons, to show where in the oven each item is. Possible? And if so, for someone who's not all that program savvy?
It would certainly be possible to write such a thing, but it would take being pretty program savvy. I know of no application closely resembling your description. TikTok is the closest I know.
But do you really want the fate of 20 souffles resting on a single piece of electronics? Which could run out of batteries, or crash? (Palms aren't especially crash-prone, but it happens.) Or where any existing timer or its data can get accidentally screwed up while someone's entering a new table number and starting a new timer?
Why not 20 magnetic kitchen timers stuck to a whiteboard where you write the table number over the timer?
posted by Zed_Lopez at 11:49 AM on May 12, 2006
But do you really want the fate of 20 souffles resting on a single piece of electronics? Which could run out of batteries, or crash? (Palms aren't especially crash-prone, but it happens.) Or where any existing timer or its data can get accidentally screwed up while someone's entering a new table number and starting a new timer?
Why not 20 magnetic kitchen timers stuck to a whiteboard where you write the table number over the timer?
posted by Zed_Lopez at 11:49 AM on May 12, 2006
It's a cool concept! probably the most realistic way to implement would be using a normal pc (running Linux, even) with a goo-proof touchscreen, set up at a central location.
posted by Artful Codger at 12:07 PM on May 12, 2006
posted by Artful Codger at 12:07 PM on May 12, 2006
I know it's low tech, but what about a whiteboard with a diagram of oven locations on it, with time in written in the area where the souffle is? Do you have space?
Ive been in a few kitchens, and I just don't think anything electronic would survive for long. If the heat and moisture don't get it, someone will knock it over and step on it, bash into it with a pan...
posted by Mr. Gunn at 12:29 PM on May 12, 2006
Ive been in a few kitchens, and I just don't think anything electronic would survive for long. If the heat and moisture don't get it, someone will knock it over and step on it, bash into it with a pan...
posted by Mr. Gunn at 12:29 PM on May 12, 2006
I've done some programming for PDAs, and would agree that it's more difficult than for a regular PC.
My instinct would be to go with an old PC: if anything fails, replacement parts are ubiquitous and cheap, the coding is easier and can be done by more people, and workers are more likely to be familiar with the UI of a destop application.
posted by alex_reno at 1:31 PM on May 12, 2006
My instinct would be to go with an old PC: if anything fails, replacement parts are ubiquitous and cheap, the coding is easier and can be done by more people, and workers are more likely to be familiar with the UI of a destop application.
posted by alex_reno at 1:31 PM on May 12, 2006
Response by poster: Sorry for the late thank yous, but I lost my connection until now. It was just a thought. I already have a couple Polder Timers, but they're $20 a shot. Space is very tight, and there'd be nowhere to put a PC. And my main worry with a computer is the way the place is wired; we blow circuit breakers all the time.
Mr. Gunn, we already have a whiteboard, but it's used for "needs" and "prep." We currently write the times on the tickets we get. An ideal spot for one would be the side of the oven (only space available...), but it's not cool-touch, and would look like a potato chip by the end of one evening. The idea for the PDA had been gnawing at me for some months, and I thought I'd ask. At least I knew who to ask. Thank you all!
posted by JABof72 at 6:10 AM on May 13, 2006
Mr. Gunn, we already have a whiteboard, but it's used for "needs" and "prep." We currently write the times on the tickets we get. An ideal spot for one would be the side of the oven (only space available...), but it's not cool-touch, and would look like a potato chip by the end of one evening. The idea for the PDA had been gnawing at me for some months, and I thought I'd ask. At least I knew who to ask. Thank you all!
posted by JABof72 at 6:10 AM on May 13, 2006
This thread is closed to new comments.
I would consider an industrial touch-screen display instead, connected to an ordinary PC. This sort of thing would be designed for your application and would be much easier to use and take care of. Implementing the software part would be pretty simple in something like Visual Basic, where timers and icons and such are all built in.
posted by pocams at 11:47 AM on May 12, 2006