> But it's not CF's fault (it's just that in my view CF > doesn't help much). We are trying to build web apps > with HTML elements that are fundamentally flawed. Aside > from lack of widgets, lack of persistence of data in a > form, automatic validation, key filtering, required > fields, etc, the tags are ill-conceived. Why for example > does the HTML for a select box look so different from > the HTML for a set of radio buttons, which is effectively > the same thing? Were they designed by different committees??
While I've never been a big fan of HTML interfaces, to say the least, radio buttons are individual elements - you can put them one right after the other, or you can separate them with line breaks. So I don't really see how the syntax for radio buttons could be that similar to the syntax for select boxes. I'd also hazard a guess that no one expected people to actually use HTML forms, really. At least, not for this long. Yecch. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
