From: Franky V. L. <lie...@te...> - 2008-01-25 15:38:35
|
Maybe another way would be to have a possibility to define a css class per question, so that class is used instead of the default class if wanted for that question ... Then you could use all kind of classes and layout as wanted, without the follow-up issue maybe ... On 1/25/08, Bishop Bettini <ph...@id...> wrote: > > I think the clarity is the current problem. I don't like the > use-the-name business. It's fine, I suppose, that it's implemented > that way under the hood, but the user should be able to click a check > box that says "This question is a follow-up to the previous question". > No one but we programmers would remember that you need to do "q1" > and "q1_followup" to make it work. > > bishop > > Quoting Franky Van Liedekerke <lie...@te...>: > > > I already figured that out :-) > > I don't object to it myself, but it should be clear to the survey > designer > > when creating his questions ... > > > > Franky > > > > > > On 1/25/08, Bishop Bettini <ph...@id...> wrote: > >> > >> I started with !other (yes, changing its label with !other=Foobarbaz), > >> but that wasn't what I needed ... unless I was mis-using it. > >> > >> As I understand it, !other allows you to add in write-in responses > >> **to a list of predetermined choices**. I don't want the respondent > >> to write in another choice, I want them to explain their choice. So, > >> in my case, I want to give them a list of say 5 options. I want to > >> require them to choose from that list. Then, I want to give them the > >> option of explaining their choice in greater detail. That explanation > >> is a follow-up to the first question, not a question that stands alone > >> of its own merit. > >> > >> Thoughts? > >> bishop > >> > >> > >> Quoting Matthew Gregg <mat...@gm...>: > >> > >> > It won't look like an essay question and may not be what you want but > >> > !other does something like this. Maybe you could expand that? > >> > > >> > On Fri, 2008-01-25 at 07:26 -0500, Bishop Bettini wrote: > >> >> Hi Franky, > >> >> > >> >> In my case, it's visual. Showing the follow-up question isn't > >> >> "conditional" on the previous answer, but rather allows "expansion" > on > >> >> the previous answer. > >> >> > >> >> Like, suppose you have these two question: > >> >> > >> >> Please tell us how satisfied you were with our service: > >> >> ( ) Very satisfied > >> >> ( ) About usual > >> >> ( ) Very dissatisfied > >> >> > >> >> Please list any particular experiences you had that led you to that > >> >> response: > >> >> /----------------------\ > >> >> | | > >> >> | | > >> >> \----------------------/ > >> >> > >> >> > >> >> > >> >> The second question doesn't stand on its own -- it's answer is only > >> >> meaningful in light of the first answer. Similarly, the choice made > >> >> for the first answer doesn't drive whether to show the second > >> >> question: you always show it, but you want to visually indicate that > >> >> the essay box question "follows up" to the radio question. > >> >> > >> >> > >> >> Thoughts? > >> >> bishop > >> >> > >> >> > >> >> Quoting Franky Van Liedekerke <lie...@te...>: > >> >> > >> >> > Hi Bishop, > >> >> > > >> >> > doesn't conditions already foresee such a functionality (show a > >> question > >> >> > when the answer to a previous question meets some conditions)? Or > is > >> this > >> >> > only a visual thing? > >> >> > > >> >> > Franky > >> >> > > >> >> > On 1/25/08, Bishop Bettini <ph...@id...> wrote: > >> >> >> > >> >> >> All, > >> >> >> > >> >> >> I've made the following modification to my local branch, but I > >> didn't > >> >> >> know if it was something the community wanted. If so, I'll > commit > >> to > >> >> >> trunk. There's an example screen-shot attached. > >> >> >> > >> >> >> Issue 940: > >> >> >> In some scenarios, one question follows up another. For example, > you > >> >> >> might ask to rate your experience with a particular subject, then > >> >> >> provide an open-ended justification for that rating. These > aren't > >> >> >> logically "next" questions, and should not therefore be numbered > as > >> >> >> such. They should also be visually "tied" the previous question, > so > >> >> >> as to form a mental association between the two. Finally, these > >> >> >> aren't new question types, but a relationship between questions. > >> >> >> > >> >> >> Implement this by name sequencing. If this question name begins > >> with > >> >> >> exactly the same name as the previous question, it's a > >> follow-up. For > >> >> >> example "q1" followed by a "q1_comments" question will key that > >> >> >> "q1_comments" is a follow-up. There are, however, still two > >> separate > >> >> >> questions in the database. We are simply indicating the > association > >> >> >> by the question names. > >> >> >> > >> >> >> bishop > >> >> >> > >> >> >> -- > >> >> >> Bishop Bettini > >> >> >> ideacode, Inc. > >> >> >> (main) +1 919 341 5170 / (fax) +1 919 521 4100 > >> >> >> > >> >> >> Visit us on the web at: > >> >> >> ideacode.com Professional software research and > development > >> >> >> reviewmysoftware.com Improve sales! Review your software before > you > >> >> >> release > >> >> >> bytejar.com Solutions to those annoying development > >> problems > >> >> >> > >> >> >> > >> > ------------------------------------------------------------------------- > >> >> >> This SF.net email is sponsored by: Microsoft > >> >> >> Defy all challenges. Microsoft(R) Visual Studio 2008. > >> >> >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >> >> >> _______________________________________________ > >> >> >> phpESP-devel mailing list > >> >> >> php...@li... > >> >> >> https://lists.sourceforge.net/lists/listinfo/phpesp-devel > >> >> >> > >> >> >> > >> >> >> > >> >> > > >> >> > >> >> > >> >> > >> > > >> > > >> > >> > >> > >> -- > >> Bishop Bettini > >> ideacode, Inc. > >> (main) +1 919 341 5170 / (fax) +1 919 521 4100 > >> > >> Visit us on the web at: > >> ideacode.com Professional software research and development > >> reviewmysoftware.com Improve sales! Review your software before you > >> release > >> bytejar.com Solutions to those annoying development problems > >> > >> > >> > > > > > > -- > Bishop Bettini > ideacode, Inc. > (main) +1 919 341 5170 / (fax) +1 919 521 4100 > > Visit us on the web at: > ideacode.com Professional software research and development > reviewmysoftware.com Improve sales! Review your software before you > release > bytejar.com Solutions to those annoying development problems > > > |