Now, if I use this code my flash form will not come up, but if I use a regular input tag it works fine.
Can someone tell me if this is not allowed or if I№m doing something wrong?
Thanks, - Charles
PS: I№m using CFMX 7
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application
Why don't you try radio button instead of checkbox?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Hello, I'm trying to use the cfinput tag with a type of checkbox. The issue I'm having is that it won't let me use the same name more than once.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application
Now, if I use this code my flash form will not come up, but if I use a regular input tag it works fine.
Can someone tell me if this is not allowed or if I№m doing something wrong?
Thanks, - Charles
PS: I№m using CFMX 7
-- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 266.4.0 - Release Date: 22/02/2005
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application
Now, if I use this code my flash form will not come up, but if I use a> regular input tag it works fine.>
Can someone tell me if this is not allowed or if I№m doing something wrong?>
Thanks,> - Charles>
PS: I№m using CFMX 7>
--> No virus found in this outgoing message.> Checked by AVG Anti-Virus.> Version: 7.0.300 / Virus Database: 266.4.0 - Release Date: 22/02/2005>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67
Charles Heizer 24 February 2005 21:24:03 [ permanent link ]
I need to allow the user to select multiple items.
- Charles
On 2/24/05 3:25 AM, "Tarantor" <tarantor-Fa4p6Uz6hlDk1uMJSBkQmQ@public.gmane.org> wrote:
Why don't you try radio button instead of checkbox?>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~> Hello,> I'm trying to use the cfinput tag with a type of checkbox. The issue I'm> having is that it won't let me use the same name more than once.>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67
Sean Corfield 24 February 2005 21:42:43 [ permanent link ]
On Wed, 23 Feb 2005 16:52:26 -0800, Charles Heizer <heizer1-i2BcT+NCU+M@public.gmane.org> wrote:> I'm trying to use the cfinput tag with a type of checkbox. The issue I'm> having is that it won't let me use the same name more than once.
"If you're not annoying somebody, you're not really alive." -- Margaret Atwood
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67
Charles Heizer 24 February 2005 22:02:05 [ permanent link ]
Do you know why that is, since a regular input checkbox field does not have to be unique it's only when I use the format type as flash?
Thanks, - Charles
On 2/24/05 10:42 AM, "Sean Corfield" <seancorfield-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
On Wed, 23 Feb 2005 16:52:26 -0800, Charles Heizer <heizer1-i2BcT+NCU+M@public.gmane.org> wrote:>> I'm trying to use the cfinput tag with a type of checkbox. The issue I'm>> having is that it won't let me use the same name more than once.>
That's correct. Each field must have a unique name.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67
Brendan OHara 24 February 2005 22:09:51 [ permanent link ]
Well Flash has a Client-side state where as HTML doesn't.
HTML simple aggregates all inputs with the same name when its submitted. Flash already knows they are different controls and since you can bind data to a specific checkbox then they would have to be enforced as "unique".
Brendan
Charles Heizer wrote:
Do you know why that is, since a regular input checkbox field does not have>to be unique it's only when I use the format type as flash?>
Thanks,>- Charles>
On 2/24/05 10:42 AM, "Sean Corfield" <seancorfield-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:>
On Wed, 23 Feb 2005 16:52:26 -0800, Charles Heizer <heizer1-i2BcT+NCU+M@public.gmane.org> wrote:>>
I'm trying to use the cfinput tag with a type of checkbox. The issue I'm>>>having is that it won't let me use the same name more than once.>>>
That's correct. Each field must have a unique name.>>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67
S . Isaac Dealey 24 February 2005 23:20:05 [ permanent link ]
If HTML doesn't have a client-side state, how to radio buttons work?
Seems to me like a cop-out excuse for having made something that's easy with HTML difficult with flash forms.
Well Flash has a Client-side state where as HTML doesn't.
HTML simple aggregates all inputs with the same name when> its submitted.> Flash already knows they are different controls and since> you can bind> data to a specific checkbox then they would have to be> enforced as "unique".
Brendan
Charles Heizer wrote:
Do you know why that is, since a regular input checkbox>>field does not have>>to be unique it's only when I use the format type as>>flash?>>
Thanks,>>- Charles>>
On 2/24/05 10:42 AM, "Sean Corfield">><seancorfield-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:>>
On Wed, 23 Feb 2005 16:52:26 -0800, Charles Heizer>>><heizer1-i2BcT+NCU+M@public.gmane.org> wrote:>>>
I'm trying to use the cfinput tag with a type of>>>>checkbox. The issue I'm>>>>having is that it won't let me use the same name more>>>>than once.>>>>
That's correct. Each field must have a unique name.
s. isaac dealey 954.927.5117 new epoch : isn't it time for a change?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67
Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application
S . Isaac Dealey 24 February 2005 23:53:00 [ permanent link ]
Seems to me like a cop-out excuse for having made>> something>> that's easy with HTML difficult with flash forms.
Seems to me like maybe Flash and HTML are significantly> different. Why would> you expect something to work in Flash the same way it> works in HTML?
Because someone who's in all likelyhood very used to developing HTML forms designed it for other people who are predominantly rooted in the development of HTML forms. The underlying cfform/cfinput tags are written in java now -- dunno why the form tag couldn't just count up the number of elements with a given name and create them as an array of checkbox objects and then tie the values of those to a hidden input element under the hood -- seems to me like a perfectly reasonable and logical plan given the target audience.
s. isaac dealey 954.927.5117 new epoch : isn't it time for a change?
Joe Rinehart 24 February 2005 23:57:09 [ permanent link ]
Seems to me like maybe Flash and HTML are significantly different. Why would> you expect something to work in Flash the same way it works in HTML?
When I was exploring Flash forms I hit this and, because of my Flash background, didn't give it another thought.
However, the new Flash forms are sort of being interpreted as "Just like the old CFForm, but with the new format attribute." For someone without a Flash background who just wants to use Flash forms in CF, I can see why it'd be confusing to have Flash form inputs that don't act the same as their direct HTML equivalents.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67
well its something new so of course you may have to learn a few new things, especially when its not the same thing at all. If you want the benefits of using it then take a few extra mintues to learn it.
---------------------------------------- From: Joe Rinehart <joe.rinehart-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> Sent: Thursday, February 24, 2005 3:58 PM To: CF-Talk <cf-talk-2K/2x8RPSj9p9z4BATjFtQC/G2K4zDHf@public.gmane.org> Subject: Re: cfinput question...
Seems to me like maybe Flash and HTML are significantly different. Why would> you expect something to work in Flash the same way it works in HTML?
When I was exploring Flash forms I hit this and, because of my Flash background, didn't give it another thought.
However, the new Flash forms are sort of being interpreted as "Just like the old CFForm, but with the new format attribute." For someone without a Flash background who just wants to use Flash forms in CF, I can see why it'd be confusing to have Flash form inputs that don't act the same as their direct HTML equivalents.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67
Charles Heizer 25 February 2005 00:31:34 [ permanent link ]
This was true for me, I guess the really confusing part was that I did not get a error on screen or even with the debug turned on, it just won't show the flash form, and you have no idea what's wrong.
- Charles
On 2/24/05 12:57 PM, "Joe Rinehart" <joe.rinehart-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
Seems to me like maybe Flash and HTML are significantly different. Why would>> you expect something to work in Flash the same way it works in HTML?>
When I was exploring Flash forms I hit this and, because of my Flash> background, didn't give it another thought.>
However, the new Flash forms are sort of being interpreted as "Just> like the old CFForm, but with the new format attribute." For someone> without a Flash background who just wants to use Flash forms in CF, I> can see why it'd be confusing to have Flash form inputs that don't act> the same as their direct HTML equivalents.>
-Joe
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67
That message should have shown up, it's a compile error. Did you have the show flash compile errors debug option checked as well?
The reason the names have to be unique is because flex requires each component to have a unique id (which I believe is something flash forces on flex). And since we are using Flex under the covers we have to follow their rules for what a movie is and how it's defined.
There is one way to do this, use a repeator to generate the checkboxes. Since the checkboxes are created at runtime, they can share the same name.
---nimer
-----Original Message----- From: Charles Heizer [mailto:heizer1-i2BcT+NCU+M@public.gmane.org] Sent: Thursday, February 24, 2005 4:32 PM To: CF-Talk Subject: Re: cfinput question...
This was true for me, I guess the really confusing part was that I did not get a error on screen or even with the debug turned on, it just won't show the flash form, and you have no idea what's wrong.
- Charles
On 2/24/05 12:57 PM, "Joe Rinehart" <joe.rinehart-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
Seems to me like maybe Flash and HTML are significantly different. >> Why would you expect something to work in Flash the same way it works in
HTML?>
When I was exploring Flash forms I hit this and, because of my Flash > background, didn't give it another thought.>
However, the new Flash forms are sort of being interpreted as "Just > like the old CFForm, but with the new format attribute." For someone > without a Flash background who just wants to use Flash forms in CF, I > can see why it'd be confusing to have Flash form inputs that don't act > the same as their direct HTML equivalents.>
Charles Heizer 25 February 2005 01:01:57 [ permanent link ]
Nope, I did not have flash compile errors checked on the debug, my mistake. It probably would have helped.
I've already altered my code to support unique names, I guess it's just nice to know.
- Charles
On 2/24/05 1:42 PM, "Mike Nimer" <mnimer-14osZcCZf762oZ/6fjIToQ@public.gmane.org> wrote:
That message should have shown up, it's a compile error. Did you have the> show flash compile errors debug option checked as well?>
The reason the names have to be unique is because flex requires each> component to have a unique id (which I believe is something flash forces on> flex). And since we are using Flex under the covers we have to follow their> rules for what a movie is and how it's defined.>
There is one way to do this, use a repeator to generate the checkboxes.> Since the checkboxes are created at runtime, they can share the same name.>
---nimer>
-----Original Message-----> From: Charles Heizer [mailto:heizer1-i2BcT+NCU+M@public.gmane.org]> Sent: Thursday, February 24, 2005 4:32 PM> To: CF-Talk> Subject: Re: cfinput question...>
This was true for me, I guess the really confusing part was that I did not> get a error on screen or even with the debug turned on, it just won't show> the flash form, and you have no idea what's wrong.>
- Charles>
On 2/24/05 12:57 PM, "Joe Rinehart" <joe.rinehart-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:>
Seems to me like maybe Flash and HTML are significantly different.>>> Why would you expect something to work in Flash the same way it works in> HTML?>>
When I was exploring Flash forms I hit this and, because of my Flash>> background, didn't give it another thought.>>
However, the new Flash forms are sort of being interpreted as "Just>> like the old CFForm, but with the new format attribute." For someone>> without a Flash background who just wants to use Flash forms in CF, I>> can see why it'd be confusing to have Flash form inputs that don't act>> the same as their direct HTML equivalents.>>
Seems to me like a cop-out excuse for having made something > > > that's easy with HTML difficult with flash forms.>
Seems to me like maybe Flash and HTML are significantly > > different. Why would you expect something to work in Flash > > the same way it works in HTML?>
Because someone who's in all likelyhood very used to > developing HTML forms designed it for other people who are > predominantly rooted in the development of HTML forms. The > underlying cfform/cfinput tags are written in java now -- > dunno why the form tag couldn't just count up the number of > elements with a given name and create them as an array of > checkbox objects and then tie the values of those to a hidden > input element under the hood -- seems to me like a perfectly > reasonable and logical plan given the target audience.
While I might share your initial expectation that things might work the same way in both, I would take issue with your contention that if they don't it's a "cop-out excuse".
Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information!
I agree. I'll see what we can do to get this documented better in the docs.
---nimer
-----Original Message----- From: Charles Heizer [mailto:heizer1-i2BcT+NCU+M@public.gmane.org] Sent: Thursday, February 24, 2005 5:02 PM To: CF-Talk Subject: Re: cfinput question...
Nope, I did not have flash compile errors checked on the debug, my mistake. It probably would have helped.
I've already altered my code to support unique names, I guess it's just nice to know.
- Charles
On 2/24/05 1:42 PM, "Mike Nimer" <mnimer-14osZcCZf762oZ/6fjIToQ@public.gmane.org> wrote:
That message should have shown up, it's a compile error. Did you have > the show flash compile errors debug option checked as well?>
The reason the names have to be unique is because flex requires each > component to have a unique id (which I believe is something flash > forces on flex). And since we are using Flex under the covers we have > to follow their rules for what a movie is and how it's defined.>
There is one way to do this, use a repeator to generate the checkboxes.> Since the checkboxes are created at runtime, they can share the same name.>
---nimer>
-----Original Message-----> From: Charles Heizer [mailto:heizer1-i2BcT+NCU+M@public.gmane.org]> Sent: Thursday, February 24, 2005 4:32 PM> To: CF-Talk> Subject: Re: cfinput question...>
This was true for me, I guess the really confusing part was that I did > not get a error on screen or even with the debug turned on, it just > won't show the flash form, and you have no idea what's wrong.>
- Charles>
On 2/24/05 12:57 PM, "Joe Rinehart" <joe.rinehart-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:>
Seems to me like maybe Flash and HTML are significantly different.>>> Why would you expect something to work in Flash the same way it >>> works in> HTML?>>
When I was exploring Flash forms I hit this and, because of my Flash >> background, didn't give it another thought.>>
However, the new Flash forms are sort of being interpreted as "Just >> like the old CFForm, but with the new format attribute." For someone >> without a Flash background who just wants to use Flash forms in CF, I >> can see why it'd be confusing to have Flash form inputs that don't >> act the same as their direct HTML equivalents.>>
Adrian Lynch 25 February 2005 02:18:10 [ permanent link ]
Then why can you have radio inputs with the same name?
I thought the point of Flash forms was to map directly to HTML forms, of course with improvements also, but holding onto the way they work. I know that sounds like a simplistic view.
It's almost always the case that we use both radio and checkbox inputs to show related data with radio capturing one and checkbox capturing many. Are there any benefits with moving away from this?
Flash groups radio inputs, why not checkboxes? If name maps to ID why not have a group attribute? Identifying a form element with a unique ID makes sense, but why have a way of grouping these form elements which can then be referered to by another ID?
Have I missed the point with this?
Ade
-----Original Message----- From: Mike Nimer [mailto:mnimer-14osZcCZf762oZ/6fjIToQ@public.gmane.org] Sent: 24 February 2005 21:43 To: CF-Talk Subject: RE: cfinput question...
The reason the names have to be unique is because flex requires each component to have a unique id (which I believe is something flash forces on flex). And since we are using Flex under the covers we have to follow their rules for what a movie is and how it's defined.
---nimer -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 266.4.0 - Release Date: 22/02/2005
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67
Sean Corfield 25 February 2005 12:03:17 [ permanent link ]
On Thu, 24 Feb 2005 15:53:00 -0500, S. Isaac Dealey <info-lh3XLey14IJYi9NPxK1VTg@public.gmane.org> wrote:> Because someone who's in all likelyhood very used to developing HTML> forms designed it for other people who are predominantly rooted in the> development of HTML forms.
Strangely, it would never have occurred to me to have multiple HTML form fields with the same name... I'm actually surprised it even works... -- Sean A Corfield -- http://www.corfield.org/ Team Fusebox -- http://www.fusebox.org/ Breeze Me! -- http://www.corfield.org/breezeme Got Gmail? -- I have 48, yes 48, invites to give away!
"If you're not annoying somebody, you're not really alive." -- Margaret Atwood
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67
S . Isaac Dealey 25 February 2005 17:15:38 [ permanent link ]
On Thu, 24 Feb 2005 15:53:00 -0500, S. Isaac Dealey> <info-lh3XLey14IJYi9NPxK1VTg@public.gmane.org> wrote:>> Because someone who's in all likelyhood very used>> to developing HTML forms designed it for other>> people who are predominantly rooted in the>> development of HTML forms.>
Strangely, it would never have occurred to me to> have multiple HTML form fields with the same name...> I'm actually surprised it even works...> --> Sean A Corfield -- http://www.corfield.org/
You know, when I first started working with web applications, it was a bit of a surprise to me also... Though that was all over in a couple minutes... if that... but my thinking is that it ought to cater to people who've been working with them for a while, as newbies aren't already accustomed to much of anything.
Heck, the onTap framework has a whole library of XML tags that were invented originally to provide a syntax that would be familiar to developers who are accustomed to working with templated html (because the underlying API was foreign to them).
In retrospect I'm more fond of the xhtml syntax myself now because it provides some features beyond the function libraries which could only be created because the syntax offers some additional context not available to the underlying API - automated form validation (matching database meta-data) as an example.
s. isaac dealey 954.927.5117 new epoch : isn't it time for a change?
add features without fixtures with the onTap open source framework
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67
The radio buttons works as groups. Technically the group has 1 name with child radio components (basically an array of children). And only 1 child can be selected, so you don't need to differentiate between the kids. And like other fields you can't have multiple groups with the same name in a form.
I know it's odd that radio buttons can be grouped and checkboxes can't, I can see the point for and against it too. I have my own list of things I wished worked differently. But the flash designers who designed these components, with a lot of heated discussions, decided to implement them one way vs. another.
Submit an enhancement and I'll see if I can't get grouping of checkboxes added to the next release of flex (then we can use it in CF)
As for the point of flash forms - I wouldn't say the point was to map directly to, or replace completely, html forms. We are not expecting users to run and edit all of their existing html forms and change the attribute format="flash" and have them all work automatically. Flash forms are a new form type with it's own rules. It is these rules that allow the form to do more powerful and richer things, such as binding. Binding is one of the reason why duplicate id's aren't allowed. Imagine trying to bind a field to a check box and it's selected status, if you had 3 checkboxes with duplicate names .
The point we tried to achieve with the flash forms was to create richer forms for the web. And we did try to model them after the html forms, So they would be familiar and easy to use for the non-flash developer. Which I think we did pretty well. When we could go two ways with the forms and how they behaved we would choose the html path. But there were some things that had to be done 1 way for the form to work.
---nimer
-----Original Message----- From: Adrian Lynch [mailto:contact-6KWGFRktKfVVf96sC3x02Vpr/1R2p/CL@public.gmane.org] Sent: Thursday, February 24, 2005 6:18 PM To: CF-Talk Subject: RE: cfinput question...
Then why can you have radio inputs with the same name?
I thought the point of Flash forms was to map directly to HTML forms, of course with improvements also, but holding onto the way they work. I know that sounds like a simplistic view.
It's almost always the case that we use both radio and checkbox inputs to show related data with radio capturing one and checkbox capturing many. Are there any benefits with moving away from this?
Flash groups radio inputs, why not checkboxes? If name maps to ID why not have a group attribute? Identifying a form element with a unique ID makes sense, but why have a way of grouping these form elements which can then be referered to by another ID?
Have I missed the point with this?
Ade
-----Original Message----- From: Mike Nimer [mailto:mnimer-14osZcCZf762oZ/6fjIToQ@public.gmane.org] Sent: 24 February 2005 21:43 To: CF-Talk Subject: RE: cfinput question...
The reason the names have to be unique is because flex requires each component to have a unique id (which I believe is something flash forces on flex). And since we are using Flex under the covers we have to follow their rules for what a movie is and how it's defined.
---nimer -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 266.4.0 - Release Date: 22/02/2005
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application
Adrian Lynch 25 February 2005 19:17:42 [ permanent link ]
Thanks for the reply. I think I'm in the mindset that radio and checkboxes are the same but for the ability to select one or many. I also think users of these forms we build have the same mindset, although I've never asked :OP
I just noticed you're from Macromedia, can I just say, the free MM pen I got at the Ben Forta talk a few days back is amazing. It's a weighty little number, it's replaced the baseball bat I had next to my bed for when the burglars come knocking! :OD
Ade
-----Original Message----- From: Mike Nimer [mailto:mnimer-14osZcCZf762oZ/6fjIToQ@public.gmane.org] Sent: 25 February 2005 16:03 To: CF-Talk Subject: RE: cfinput question...
The radio buttons works as groups. Technically the group has 1 name with child radio components (basically an array of children). And only 1 child can be selected, so you don't need to differentiate between the kids. And like other fields you can't have multiple groups with the same name in a form.
I know it's odd that radio buttons can be grouped and checkboxes can't, I can see the point for and against it too. I have my own list of things I wished worked differently. But the flash designers who designed these components, with a lot of heated discussions, decided to implement them one way vs. another.
Submit an enhancement and I'll see if I can't get grouping of checkboxes added to the next release of flex (then we can use it in CF)
As for the point of flash forms - I wouldn't say the point was to map directly to, or replace completely, html forms. We are not expecting users to run and edit all of their existing html forms and change the attribute format="flash" and have them all work automatically. Flash forms are a new form type with it's own rules. It is these rules that allow the form to do more powerful and richer things, such as binding. Binding is one of the reason why duplicate id's aren't allowed. Imagine trying to bind a field to a check box and it's selected status, if you had 3 checkboxes with duplicate names .
The point we tried to achieve with the flash forms was to create richer forms for the web. And we did try to model them after the html forms, So they would be familiar and easy to use for the non-flash developer. Which I think we did pretty well. When we could go two ways with the forms and how they behaved we would choose the html path. But there were some things that had to be done 1 way for the form to work.
---nimer
-----Original Message----- From: Adrian Lynch [mailto:contact-6KWGFRktKfVVf96sC3x02Vpr/1R2p/CL@public.gmane.org] Sent: Thursday, February 24, 2005 6:18 PM To: CF-Talk Subject: RE: cfinput question...
Then why can you have radio inputs with the same name?
I thought the point of Flash forms was to map directly to HTML forms, of course with improvements also, but holding onto the way they work. I know that sounds like a simplistic view.
It's almost always the case that we use both radio and checkbox inputs to show related data with radio capturing one and checkbox capturing many. Are there any benefits with moving away from this?
Flash groups radio inputs, why not checkboxes? If name maps to ID why
