All of these problems seemed intractable at first with decisions made about one influencing, detrimentally, a decision made elsewhere. Mirroring
the
<t:index entry="Cocoon"/>
Cocoon forms template,
<link:link type="uri" ref="http://cocoon.apache.org/2.1/userdocs/basics/index.html" target="cforms">CForms</link:link>
was initially desirable for commonality with
<t:index entry="Cocoon"/>
Cocoon. But it soon became apparent that
this was going to make the whole approach far too complicated for what I wanted. Much code was wasted in exploring this but I believe it was the
right decision. In the end I based the Paloose forms (
<link:link type="uri" ref="pforms.html">PForms</link:link>
) on the JXForms that older version
of
<t:index entry="Cocoon"/>
Cocoon used. (I had produced some sites with this in the past so I was reasonably familiar with it).
<link:link type="uri" ref="pforms.html">PForms</link:link>
is not radically different from JXForms but it does not slavishly follow the latter. I believe
that
<link:link type="uri" ref="pforms.html">PForms</link:link>
is suitable for the restrictions I had set on Paloose and, as I have said elsewhere,
if you have a site that requires all the facilities of
<link:link type="uri" ref="http://cocoon.apache.org/2.1/userdocs/basics/index.html" target="cforms">CForms</link:link>
then you should probably be using
<t:index entry="Cocoon"/>
Cocoon anyway.
</t:p>