W3C home > Mailing lists > Public > public-xformsusers@w3.org > July 2012

recursive dispatch of actions

From: C. M. Sperberg-McQueen <cmsmcq@blackmesatech.com>
Date: Mon, 30 Jul 2012 21:00:33 -0600
Message-Id: <701269D5-E874-4572-BF1E-D02AD59101D4@blackmesatech.com>
Cc: "C. M. Sperberg-McQueen" <cmsmcq@blackmesatech.com>
To: public-xformsusers@w3.org
This may remind some of a popular quotation from Samuel Johnson:

  [it] is like a dog's walking on his hind legs. It is not done well; but you 
  are surprised to find it done at all.

But in case it is of any interest to other users of XForms, I have built
a simple demonstration page illustrating the implementation of 
recursive functions in XForms by the use of action, dispatch, insert, 
delete, and a document instance reserved for use as a stack:

  http://blackmesatech.com/2012/07/testcase/actions.xml

It may perhaps be regarded as a simple demonstration of the
fact enunciated in section 1.5.6 of the XForms 1.1 spec:

> All XForms actions, as well as sets of actions, can be executed conditionally or iteratively. Combined with the generalized insert and delete, this means that the information processing power of XForms 1.1 is Turing-complete.


In preparing the example, I learned a great deal.  Unfortunately, one 
of the things I learned is that I don't understand how the xforms-refresh
event is intended to be propagated, or how to use it (if one can) to
make a representation of the stack change as the recursive calls
proceed.

Can any reader of this list point me to a useful example of xf:refresh
or of xf:dispatch name="xforms-refresh"?

-- 
****************************************************************
* C. M. Sperberg-McQueen, Black Mesa Technologies LLC
* http://www.blackmesatech.com 
* http://cmsmcq.com/mib                 
* http://balisage.net
****************************************************************
Received on Tuesday, 31 July 2012 03:00:57 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:48:24 UTC