On 6/2/05, Chris Boget <[EMAIL PROTECTED]> wrote:
> What's 'ajax'? Link please?
http://en.wikipedia.org/wiki/AJAX
I've been playing with it using Ruby on Rails, it's built-in.
--
Greg Donald
Zend Certified Engineer
http://destiney.com/
--
PHP General Mailing List (http://www.php.net/)
To uns
Hello Chris,
Thursday, June 2, 2005, 4:43:09 PM, you wrote:
>> That being the case, you may want to consider ajax, so that users
>> answers are recorded as soon as they make them.
CB> What's 'ajax'? Link please?
It's a way of using the XML HTTP Request object in JavaScript to
provide a very dy
Sorry I thought I'd sent this to the list.
On 6/1/05, Rory Browne <[EMAIL PROTECTED]> wrote:
> http://www.adaptivepath.com/publications/essays/archives/000385.php
>
> www.wikipedia.org/wiki/AJAX
>
>
> On 6/1/05, Ryan A <[EMAIL PROTECTED]> wrote:
> >
> > > That being the case, you may want to co
On 6/2/05, Chris Boget <[EMAIL PROTECTED]> wrote:
> > That being the case, you may want to consider ajax, so that users
> > answers are recorded as soon as they make them.
>
> What's 'ajax'? Link please?
www.google.com
>
> thnx,
> Chris
>
>
--
PHP General Mailing List (http://www.php.net/)
T
> That being the case, you may want to consider ajax, so that users
> answers are recorded as soon as they make them.
What's 'ajax'? Link please?
thnx,
Chris
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
On Mon, May 30, 2005 11:08 pm, Rory Browne said:
> Assuming it would be nice to cross-reference answers with other
> answers from the same answerer, putting them in the DB initially will
> not solve your problem. Unless you use sessions, then you know that
> somebody answered questions 1 - 20, and
That being the case, you may want to consider ajax, so that users
answers are recorded as soon as they make them.
On 5/31/05, ...helmut <[EMAIL PROTECTED]> wrote:
> Hello All,
>
> Thank you for all the wonderful ideas, there are so many things that can be
> over look when working by yourself.
>
Hello All,
Thank you for all the wonderful ideas, there are so many things that can be
over look when working by yourself.
When I asked help for a questionary, in reallity I meant a long form. With
that said I apologize for having some people in mind more like a question
answer type of thing(scho
On 5/31/05, Richard Lynch <[EMAIL PROTECTED]> wrote:
> On Sat, May 28, 2005 10:08 am, ...helmut said:
> > I have a form that contains 100 questions. To make it easier on the user,
> > I
> > will divide it into 5 sections (20 questions per section), then all the
> > information will be written to a
On Sat, May 28, 2005 10:08 am, ...helmut said:
> I have a form that contains 100 questions. To make it easier on the user,
> I
> will divide it into 5 sections (20 questions per section), then all the
> information will be written to a db. What is the best way to carry along
> through the pages the
If you insist on doing this serverside, then personally I'd probably
use hidden form fields. If you're open to doing it client side, then
I'd probably out the information into five sections, only one of
which would be visible at any one time. using dhtml. What you want is
the CSS visibility attrib
I have a form that contains 100 questions. To make it easier on the user, I
will divide it into 5 sections (20 questions per section), then all the
information will be written to a db. What is the best way to carry along
through the pages the information that has already been submitted? Cookies?
I have a form that contains 100 questions. To make it easier on the user, I
will divide it into 5 sections (20 questions per section), then all the
information will be written to a db. What is the best way to carry along
through the pages the information that has already been submitted? Cookies?
I have a form that contains 100 questions. To make it easier on the user, I
will divide it into 5 sections (20 questions per section), then all the
information will be written to a db. What is the best way to carry along
through the pages the information that has already been submitted? Cookies?
I have a form that contains 100 questions. To make it easier on the user, I
will divide it into 5 sections (20 questions per section), then all the
information will be written to a db. What is the best way to carry along
through the pages the information that has already been submitted? Cookies?
Wr
15 matches
Mail list logo
