On Fri, 2009-05-29 at 19:24 -0400, PJ wrote:
Michael A. Peters wrote:
Bob McConnell wrote:
like a web based front end,
exclusion of specific ingredients due to allergies and being able to
attach dated notes about alterations or substitutions I try each time
That sounds wicked.
Ashley Sheridan wrote:
On Fri, 2009-05-29 at 19:24 -0400, PJ wrote:
Michael A. Peters wrote:
Bob McConnell wrote:
like a web based front end,
exclusion of specific ingredients due to allergies and being able to
attach dated notes about alterations or substitutions I try
On Sat, 30 May 2009 14:31:26 -0400, af.gour...@videotron.ca (PJ) wrote:
So, if corn is bad, eating it will get rid of it faster right? :p
No it will turn you into a corn cob! ;-)
Which is why Christopher Columbus found the Americas uninhabited! ;-)
--
PHP General Mailing List
I'd like to get some input on how to deal with recipes.
use html pages to store and display, XML or db or... ? And what about
clips, like flvs ? TIA.
--
Hervé Kempf: Pour sauver la planète, sortez du capitalisme.
-
Phil Jourdan ---
Hi,
I'd like to get some input on how to deal with recipes.
use html pages to store and display, XML or db or... ? And what about
clips, like flvs ? TIA.
Actual recipes? As in a pork roast? I would put them on the file
system in .html files. You could use a PHP file to serve them, and
have a
From: PJ
I'd like to get some input on how to deal with recipes.
use html pages to store and display, XML or db or... ? And what about
clips, like flvs ? TIA.
There are as many ways to do cookbooks as there are cooks. I am familiar
with half a dozen, without counting the professional
Bob McConnell wrote:
From: PJ
I'd like to get some input on how to deal with recipes.
use html pages to store and display, XML or db or... ? And what about
clips, like flvs ? TIA.
There are as many ways to do cookbooks as there are cooks. I am familiar
with half a dozen, without
From: PJ
Bob McConnell wrote:
From: PJ
I'd like to get some input on how to deal with recipes.
use html pages to store and display, XML or db or... ? And what
about
clips, like flvs ? TIA.
There are as many ways to do cookbooks as there are cooks. I am
familiar
with half a
PJ wrote:
I'd like to get some input on how to deal with recipes.
use html pages to store and display, XML or db or... ? And what about
clips, like flvs ? TIA.
I believe there is already an xml format for recipes.
I would either use that format to store them, or use equivalent database
PJ wrote:
Thank you gentlemen. Basically, that's what I figured. But this does
give me some more stuff to mull over. The only thing I'm really
wondering is if it's worth doing anything with XML.
For display in a web browser, the only thing you should do with xml is
what browsers know how
Bob McConnell wrote:
like a web based front end,
exclusion of specific ingredients due to allergies and being able to
attach dated notes about alterations or substitutions I try each time
That sounds wicked.
One of my brothers is allergic to corn.
Being able to flag ingredients that contain
Michael A. Peters wrote:
Bob McConnell wrote:
like a web based front end,
exclusion of specific ingredients due to allergies and being able to
attach dated notes about alterations or substitutions I try each time
That sounds wicked.
One of my brothers is allergic to corn.
Being able to
Michael A. Peters wrote:
Bob McConnell wrote:
like a web based front end,
exclusion of specific ingredients due to allergies and being able to
attach dated notes about alterations or substitutions I try each time
That sounds wicked.
One of my brothers is allergic to corn.
Being able to
Shawn McKenzie wrote:
Michael A. Peters wrote:
Bob McConnell wrote:
like a web based front end,
exclusion of specific ingredients due to allergies and being able to
attach dated notes about alterations or substitutions I try each time
That sounds wicked.
One of my brothers
14 matches
Mail list logo
