Actually, I've discovered it is probably easier to just add a
'labelTerminator' attribute to all of the form display/input control
tags and then add the attribute call to the right of the label.
<cfparam name="Attributes.label" type="string"
default="#Attributes.column#">
<cfparam name="Attributes.labelTerminator" type="string" default=":">
Then, when the label is called in the tag:
<td class="fieldlabel#Iif(Attributes.required, DE(' required'),
DE(''))#">#Attributes.label##Attributes.labelTerminator# </td>
This lets you set it either way, and override the default. Of course it
requires the addition of another attribute to the tag editor/completion code
SOT: I am moving to PrimalScript as my primary CFML editor. If anybody
else out there is using PS with Plum, I have the Plum custom tags
integrated and you are welcome to them. My set also has the current
CFMX7 tags and functions updated as well.
I think it would be nice to have a project preference that would allow
you to specify globally that you do or don't want colons appended to
the end of all of your field label names, e.g., 'label:'
Some clients like them, some don't. This would allow you to flip them
on and off with an Application scoped variable, and have qForms
validation ignore the colon during validation.
Anybody else have any thoughts on this?
Jeff
**********************************************************************
You can subscribe to and unsubscribe from lists, and you can change
your subscriptions between normal and digest modes here:
http://www.productivityenhancement.com/support/DiscussionListsForm.cfm
**********************************************************************
**********************************************************************
You can subscribe to and unsubscribe from lists, and you can change
your subscriptions between normal and digest modes here:
http://www.productivityenhancement.com/support/DiscussionListsForm.cfm
**********************************************************************
