> Steve wrote: > > "Should that form field be a checkbox or a radio button?" They > won't know until they see it. Just thinking aloud: Does the client really care whether it's a checkbox or a radio button? Odds are, he doesn't know the difference. How can he "see it" in the subtlties that he doesn't understand?
> The answer dramatically changes the design of the database. Why should it? Why should your database design be so dependant on the user interface? Or are you just using the prototype to answer the real question: "Can multiple values be specified here, or just one?" I don't think the client needs to see anything to answer a question like that most of the time. But you need to record the answer and the prototype is the most efficient and reliable method you have for recording that answer, right? Patrick ==^================================================================ This email was sent to: [email protected] EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^================================================================
