Hello,

Thank you for your answer.

After studying AJAXForms, I have been able to integrate its main Java 
parts inside a unique XSLT 1.0 stylesheet. I have already tested it 
successfully, on client-side transformation, with Internet Explorer, 
FireFox and Safari (there is some nasty bug in Opera XSLT engine about 
embedded apply-template with select attribute within call-template...) 
and loading time is good !

AJAXForms performs a conversion of every XPath expression to Javascript 
objects using Jaxen capabilities so I had to analyze XPath expressions 
with XSLT 1.0 only (some named templates with a stack mecanism based on 
strings manipulations...).

It is now an only pre-alpha version at 
http://sourceforge.net/projects/xsltforms/ (axis not supported,- unary 
operator not well supported, ..., different bugs in Javascript parts,...).

Alain COUTHURES
<agenceXML>
http://www.agencexml.com
Bordeaux, France

G. Ken Holman a écrit :
> At 2008-10-10 11:19 +0200, COUTHURES Alain wrote:
>> I just saw old threads about XForms to XHTML conversion using XSLT 
>> and I think this could still be a good idea for client-side XForms or 
>> for PHP only server-side XForms
>
> For many years I've been doing XML->PHP for all of the forms on 
> Crane's web site.  One investment in writing the XSLT to get the 
> necessary server-side PHP to run the form and then I forgot all the 
> PHP I learned because every form I need I just express in XML.
>
> Here is an example form, and you wouldn't know that I wrote it in XML:
>
>   http://www.CraneSoftwrights.com/forms/interest.php
>
> All field validation and retrying of the form is done in PHP.  And 
> when bots started filling out my forms I only had to add the 
> "staleness" and challenge question to my XSLT and instantly all of my 
> forms were updated with the need for someone to think about one of the 
> values to validate the form wasn't being filled out by a bot.
>
>> and there are today opensource solutions which are performing this 
>> conversion in Java.
>>
>> What would the main problems rewriting a conversion tool with XSLT ? 
>> Effective full XSLT 1.0 support by browsers ? XForms specific CSS 
>> rules to translate ?
>
> For server-side PHP implementation of XForms, I don't think those 
> questions matter ... although many years ago I used XSLT 1, if I had 
> to do it today I would use XSLT 2 and the end result is just a PHP 
> form that runs independent of the browser used to access the server.
>
> I hope this helps.
>
> . . . . . . . . . . . . Ken
>
> -- 
> Upcoming XSLT/XSL-FO hands-on courses:      Wellington, NZ 2009-01
> Training tools: Comprehensive interactive XSLT/XPath 1.0/2.0 video
> Video sample lesson:    http://www.youtube.com/watch?v=PrNjJCh7Ppg
> Video course overview:  http://www.youtube.com/watch?v=VTiodiij6gE
> G. Ken Holman                 mailto:gkholman@C...
> Crane Softwrights Ltd.          http://www.CraneSoftwrights.com/x/
> Male Cancer Awareness Nov'07  http://www.CraneSoftwrights.com/x/bc
> Legal business disclaimers:  http://www.CraneSoftwrights.com/legal
>
>
> _______________________________________________________________________
>
> XML-DEV is a publicly archived, unmoderated list hosted by OASIS
> to support XML implementation and development. To minimize
> spam in the archives, you must subscribe before posting.
>
> [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
> Or unsubscribe: xml-dev-unsubscribe@l...
> subscribe: xml-dev-subscribe@l...
> List archive: http://lists.xml.org/archives/xml-dev/
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
>
>


_______________________________________________________________________

XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.

[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: xml-dev-unsubscribe@l...
subscribe: xml-dev-subscribe@l...
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php