> But it is still processed at page build time. Not form submission
> time... The thought never occurred to me of having a way to evaluate
> markup in form fields at time of form submission. Never had that in
> zap either. We could escape it easily enough, but then would need some
> syntax to indicate: "evaluate the markup on this form value". It is a
> very intriguing idea. I'm open to suggestions for syntax.
I found it useful for posts where it was important that the latest
information was used, like for a new page creation using latest seial
number, or time-stamping of posting time, instead of time the form was
loaded, or doing some maths, like increasing a number used in a
field, etc.
Maybe there are other ways to achieve this, like you can add commands
to be processed after form submission as a series of steps after the
submit field.
For Fox I used a similar markup as is used in the templates:
replacement variables in templates are like {$$var},
standard expressions are like {(expr ......)},
and expressions to be evaluated when posting are like {$$
(expr ......)} in Fox.
To keep in line with the variable and function markup in BoltWire,
perhaps something like this:
{+(function parameters)}
A function marked like this could be equally used in a form field or
in a template, to be evaluated when the form is submitted, or the
template processed (same thing if a template is used). Just make sure
the expression gets evaluated after variable replacements in the
template process.
~Hans
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"BoltWire" 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/boltwire?hl=en
-~----------~----~----~----~------~----~------~--~---
