On Mar 12, 5:32 am, Yaron Koren <[email protected]> wrote:
> Oh - by "for-template" fields, do you mean fields contained in
> multiple-instance templates, the ones that use "remove" and "add another"?
> Or are you talking about all templates?
I'm requesting that all templates should have this switch. As for its
name, I was thinking of
{{for template |templatename |no-null-call}}
where no-null-call = suppresses output of the template call when *all*
args are null
>
> The second issue I didn't understand either - what's an argument formulated
> from a value?
>
The value of the input widget is transformed into the value of the
argument passed to the template.
I'm requesting that all fields should have this switch. As for its
name, I was thinking of
{{field |fieldname |no-default-arg}}
where no-default-arg = suppresses output of arg when user has not
changed the field's default value
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Semantic Forms" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/semantic-forms?hl=en
-~----------~----~----~----~------~----~------~--~---
