select() with grouped output/optgroup

[funaroma]

I need a CFW select() but I need the options to be able to be grouped so that I can have states fall under a "country" optgroup.  It still needs to be a select so I can do validations with my object.  Do i have any way to feed the options in other than a straight recordset?

[Andrew Bellenie]

You don't need to use select() to do validations. Just ensure a <select> tag is named appropriately, using modelname[property] format, e.g.

<select name="post[author]">

<option...

On 23 March 2016 at 04:46, funaroma <advan...@gmail.com> wrote:

I need a CFW select() but I need the options to be able to be grouped so that I can have states fall under a "country" optgroup.  It still needs to be a select so I can do validations with my object.  Do i have any way to feed the options in other than a straight recordset?

--
You received this message because you are subscribed to the Google Groups "CFWheels" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cfwheels+u...@googlegroups.com.
To post to this group, send email to cfwh...@googlegroups.com.
Visit this group at https://groups.google.com/group/cfwheels.
For more options, visit https://groups.google.com/d/optout.

[funaroma]

meh.  time for a plugin.

[Per Djurner]

Let me know if you get that working because it sounds like something we'd eventually like to add to the framework itself.

[funaroma]

Will do.  I'd prefer being able to base it off the existing code for select() and selectTag() - advice on how i might do that?

[Per Djurner]

Not sure but perhaps it's easier to just build it into core straight away and not do a plugin?

If so, you can send a pull request when done :)

[Chris Peters]

Any ideas on what the arguments syntax should look like? Should it have some sort of group argument that would work a little bit like how includePartial works?

Chris Peters
Web Developer
Liquifusion Studios
chris....@liquifusion.com
Skype: liquifusion.support
www.liquifusion.com

[Per Djurner]

How about something like this (groupField being the new functionality)?

q = model("state").findAll(include="country") // assumes we get name and countryName back

#select(objectName="x", property="x", options=q, textField="name", groupField="countryName")#

[Chris Peters]

I like it. 👍

[Thorsten Eilers]

The tag cfoutput has the group argument. Maybe it should be named accordingly? But i like the idea.

[Chris Peters]

I think the idea of groupField is to name it similarly to other arguments in select/selectTag: valueField and textField. Make sense?

On Wed, Mar 23, 2016 at 11:04 AM, 'Thorsten Eilers' via CFWheels <cfwh...@googlegroups.com> wrote:

The tag cfoutput has the group argument. Maybe it should be named accordingly? But i like the idea.

--
You received this message because you are subscribed to the Google Groups "CFWheels" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cfwheels+u...@googlegroups.com.
To post to this group, send email to cfwh...@googlegroups.com.
Visit this group at https://groups.google.com/group/cfwheels.
For more options, visit https://groups.google.com/d/optout.

[Thorsten Eilers]

Also a viable option.

[funaroma]

groupField could be a list, if you want to get existentially hierarchical