The Editor wrote:
Also, I had hoped to allow multiple actions to occur when a condition
is passed, something like this:
(:zap if=condition||field=value,field=value,field=value:)
parenthesized maybe?
(:zap if=condition||(field=value)(field=value)(field=value):)
or some character sequence
On 3/8/07, SteP [EMAIL PROTECTED] wrote:
The Editor wrote:
Also, I had hoped to allow multiple actions to occur when a condition
is passed, something like this:
(:zap if=condition||field=value,field=value,field=value:)
parenthesized maybe?
(:zap
Dear Dan,
Two questions/suggestions.
1/ What about (:zap condition=something action=field=value:)?
2/ Would it be possible to chain such entries within the same zapform (for
inclusion in pagelist templates)? With such a solution, you would not have
to handle several actions per entry.
Cheers,
Dan wrote,
I wanted to ask a quick question to see if anyone has
any suggestions for syntax of the zap conditional processing (and form
validation also).
I would really like to see the ||s gone from ZAP's conditional syntax,
unless they mean or. Or a table boundary. Likewise the |s unless
On 3/8/07, Ben Stallings [EMAIL PROTECTED] wrote:
Dan wrote,
I had previously suggested using standard ?: syntax, like so:
(:zap field=condition ? true value : false value:)
with spaces surrounding the ? and : to distinguish them from punctuation.
Ah! Hadn't thought about the spaces.
Ben Stallings napsal(a):
Dan wrote,
I wanted to ask a quick question to see if anyone has
any suggestions for syntax of the zap conditional processing (and form
validation also).
...
(:zap condition=condition fields=field1,field2 true=value1,value2
false=value3,value4:)
...
Dan replied to Jiri,
(:zap condition=condition fields=field1,field2 true=value1,value2
false=value3,value4:)
Can't really do that without creating a new markup which I would
rather avoid. According to my markup definition, it has to look like
(:zap if*=text...:).
At the risk of getting
On 3/8/07, Ben Stallings [EMAIL PROTECTED] wrote:
Dan replied to Jiri,
(:zap condition=condition fields=field1,field2 true=value1,value2
false=value3,value4:)
Can't really do that without creating a new markup which I would
rather avoid. According to my markup definition, it has to
While I'm at it, (working on some new stuff for ZAP over the next
couple days), I wanted to ask a quick question to see if anyone has
any suggestions for syntax of the zap conditional processing (and form
validation also).
Currently it looks like:
(:zap if=condition||field|value:)
One problem
