Form Tool - hidden field

View: New views
7 Messages — Rating Filter:   Alert me  

Form Tool - hidden field

by AJ Mercer :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Attached is a new field type for hidden

deploy to
    /core/packages/formtools

usage
<cfproperty ...   fttype="hidden" bLabel="false"  ftShowLabel="false" />

--
AJ Mercer
Web Log: http://webonix.net


Once you come to the realisation that everyone is crazy,
You will never be surprised or disappointed ever again.
AJM 2008

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "farcry-beta" group.
To post to this group, send email to farcry-beta@...
To unsubscribe from this group, send email to farcry-beta+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/farcry-beta?hl=en
-~----------~----~----~----~------~----~------~--~---



hidden.cfc (5K) Download Attachment

Re: Form Tool - hidden field

by Jeff Coughlin :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


There have been several times where I could have used something like  
this.  Is there a feature request in the bug tracker I can vote for?

--
Jeff Coughlin
Web Application Developer
http://jeffcoughlin.com

On Sep 22, 2008, at 4:04 AM, AJ Mercer wrote:

> Attached is a new field type for hidden
>
> deploy to
>     /core/packages/formtools
>
> usage
> <cfproperty ...   fttype="hidden" bLabel="false"  
> ftShowLabel="false" />


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "farcry-beta" group.
To post to this group, send email to farcry-beta@...
To unsubscribe from this group, send email to farcry-beta+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/farcry-beta?hl=en
-~----------~----~----~----~------~----~------~--~---


Re: Form Tool - hidden field

by AJ Mercer :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

polls are open ;-)


On Mon, Sep 22, 2008 at 5:55 PM, Jeff Coughlin <jeff@...> wrote:

There have been several times where I could have used something like
this.  Is there a feature request in the bug tracker I can vote for?

--
Jeff Coughlin
Web Application Developer
http://jeffcoughlin.com

On Sep 22, 2008, at 4:04 AM, AJ Mercer wrote:

> Attached is a new field type for hidden
>
> deploy to
>     /core/packages/formtools
>
> usage
> <cfproperty ...   fttype="hidden" bLabel="false"
> ftShowLabel="false" />






--
AJ Mercer
Web Log: http://webonix.net


Once you come to the realisation that everyone is crazy,
You will never be surprised or disappointed ever again.
AJM 2008

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "farcry-beta" group.
To post to this group, send email to farcry-beta@...
To unsubscribe from this group, send email to farcry-beta+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/farcry-beta?hl=en
-~----------~----~----~----~------~----~------~--~---


Re: Form Tool - hidden field

by modius :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


On Sep 23, 12:41 pm, "AJ Mercer" <ajmer...@...> wrote:
> polls are open ;-)    http://bugs.farcrycms.org/browse/FC-1514

I've voted -- cos i like to encourage everyone to contribute :)  But
I'm not sure why you would want a hidden field through formtools.
Typically if you need a hidden field you build your own form using the
ft:form/ft:object and related tags.

-- geoff
http://www.daemon.com.au/
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "farcry-beta" group.
To post to this group, send email to farcry-beta@...
To unsubscribe from this group, send email to farcry-beta+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/farcry-beta?hl=en
-~----------~----~----~----~------~----~------~--~---


Re: Form Tool - hidden field

by AJ Mercer :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

This is for cases when you are happy with the edit form being created by Farcry, but need a couple of exceptions.

On Fri, Sep 26, 2008 at 8:44 AM, modius <modius@...> wrote:

On Sep 23, 12:41 pm, "AJ Mercer" <ajmer...@...> wrote:
> polls are open ;-)    http://bugs.farcrycms.org/browse/FC-1514

I've voted -- cos i like to encourage everyone to contribute :)  But
I'm not sure why you would want a hidden field through formtools.
Typically if you need a hidden field you build your own form using the
ft:form/ft:object and related tags.

-- geoff
http://www.daemon.com.au/




--
AJ Mercer
Web Log: http://webonix.net


Once you come to the realisation that everyone is crazy,
You will never be surprised or disappointed ever again.
AJM 2008

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "farcry-beta" group.
To post to this group, send email to farcry-beta@...
To unsubscribe from this group, send email to farcry-beta+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/farcry-beta?hl=en
-~----------~----~----~----~------~----~------~--~---


Re: Form Tool - hidden field

by Jeff Coughlin :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


> I've voted -- cos i like to encourage everyone to contribute :)  But
> I'm not sure why you would want a hidden field through formtools.
> Typically if you need a hidden field you build your own form using the
> ft:form/ft:object and related tags.


I've had cases where the formtools are perfect for generating the  
forms (quick and easy), but the client wants an extra field of data  
(created from the FourQ ORM) that they use for other purposes and that  
don't want that data displayed in the form.

Real Example (for one of my clients): When the form is saved, I'll run  
the beforeSave method and do a little extra math/work to determine  
data for the extra field(s). The client then uses that data for some  
purpose on their website (or maybe reports, or something).  However,  
when the average content editors go to modify the data for the type,  
they see the extra fields (that make no sense to them) and are  
confused.  To make sure they can't modify the data I currently tell  
formtools to make the fields display-only and tell the formtools not  
to modify the data.  If I could set those fields to be hidden in the  
form, then there would be a lot less clutter and confusion to the  
content editors.

Possible Example: You decide to record the number of downloads for one  
of the attached files in a type (the download count in the field is  
modified using a custom download.cfm), but don't want that data  
displayed when editing a record (nor would you allow the formtools to  
modify that data - which is already possible).

I'm sure I could come up with more examples.  Needless to say, it's a  
useful setting/option to have.

Having a simple boolean (like ftHidden="true|false") would be very  
helpful (suggest allowing it to be used on all form items and simply  
applying css "display:none") - the advantage to using this method  
instead of using type="hidden" also gives the developer the option to  
hide any field (say he/she needs to hide/disable a select field for a  
day due to some bug he's working on, but doesn't want to delete the  
field or data).  These are just random thoughts, but hopefully there  
is something useful in there :)

--
Jeff Coughlin
Web Application Developer
http://jeffcoughlin.com

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "farcry-beta" group.
To post to this group, send email to farcry-beta@...
To unsubscribe from this group, send email to farcry-beta+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/farcry-beta?hl=en
-~----------~----~----~----~------~----~------~--~---


Re: Form Tool - hidden field

by Mat Bryant :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Is the option of simply removing ftSeq and ftFieldset from the relevent <cfproperty /> which remove them from the form sufficient?

Cheers, Mat.



On Fri, Sep 26, 2008 at 12:06 PM, Jeff Coughlin <jeff@...> wrote:

> I've voted -- cos i like to encourage everyone to contribute :)  But
> I'm not sure why you would want a hidden field through formtools.
> Typically if you need a hidden field you build your own form using the
> ft:form/ft:object and related tags.


I've had cases where the formtools are perfect for generating the
forms (quick and easy), but the client wants an extra field of data
(created from the FourQ ORM) that they use for other purposes and that
don't want that data displayed in the form.

Real Example (for one of my clients): When the form is saved, I'll run
the beforeSave method and do a little extra math/work to determine
data for the extra field(s). The client then uses that data for some
purpose on their website (or maybe reports, or something).  However,
when the average content editors go to modify the data for the type,
they see the extra fields (that make no sense to them) and are
confused.  To make sure they can't modify the data I currently tell
formtools to make the fields display-only and tell the formtools not
to modify the data.  If I could set those fields to be hidden in the
form, then there would be a lot less clutter and confusion to the
content editors.

Possible Example: You decide to record the number of downloads for one
of the attached files in a type (the download count in the field is
modified using a custom download.cfm), but don't want that data
displayed when editing a record (nor would you allow the formtools to
modify that data - which is already possible).

I'm sure I could come up with more examples.  Needless to say, it's a
useful setting/option to have.

Having a simple boolean (like ftHidden="true|false") would be very
helpful (suggest allowing it to be used on all form items and simply
applying css "display:none") - the advantage to using this method
instead of using type="hidden" also gives the developer the option to
hide any field (say he/she needs to hide/disable a select field for a
day due to some bug he's working on, but doesn't want to delete the
field or data).  These are just random thoughts, but hopefully there
is something useful in there :)

--
Jeff Coughlin
Web Application Developer
http://jeffcoughlin.com





--
--
-- Matthew Bryant
Product Development Manager
Daemon Internet Consultants
Adobe Solutions Partner
http://www.daemon.com.au/
p. 02 8302 4600
f. 02 9380 4204

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "farcry-beta" group.
To post to this group, send email to farcry-beta@...
To unsubscribe from this group, send email to farcry-beta+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/farcry-beta?hl=en
-~----------~----~----~----~------~----~------~--~---