Posted by
Jency Chackummoottil on
URL: https://discuss.orbeon.com/XFDL-Integration-tp32484p32500.html
Thanks a lot Alex. The code has now become generic so that it is
applicable for any controls.
Now, the issue is with the <format> tag.
<format>
<datatype>string</datatype>
<constraints>
<length>
<min>0</min>
<max>20</max>
</length>
</constraints>
</format>
We need to convert all the constraints in the <format> tag in XFDL to
the corresponding xforms:bind attributes in XForms.
Another issue is that the width and height of an input control cannot be
set using <xhtml:div style="position:absolute; top: 53; left: 131;
width: 154; height: ;>.
Hope you can help me in solving these issues.
Thanks in advance
Jency
-----Original Message-----
From:
[hidden email] [mailto:
[hidden email]] On Behalf Of
Alessandro Vernet
Sent: Wednesday, February 07, 2007 1:28 PM
To:
[hidden email]
Subject: Re: [ops-users] XFDL Integration
Hi Jency,
I took your pipeline and updated it; the updated pipeline attached. A
few comments:
- Not that it matters much, but since the XSL file was very simple, I
just got rid of it. So you can call this pipeline from your
page-flow.xml with view="xfdl-to-xhtml.xpl" (no model).
- It is now "generic" in the sense that it supports any level of
nesting (see how templates are being used)
- Alerts for controls display next to the control (not at the top left
of the page)
- It copies some of the styles defined in XFDL over to XHTML (in
particular the background color, font face and size)
Things not yet taken care of:
- There is a second language selection drop-down at the bottom of the
page. That second drop-down is copied over from the XFDL file. Is it
supposed to be there?
- Repeats are not handled.
You can see what it looks like in the attached screenshot. I hope this
helps, and let us know how things are going with your conversion from
XFDL to XHTML.
Alex
On 2/5/07, Jency Chackummoottil <
[hidden email]>
wrote:
> Alex,
>
> I'm attaching my source code to transform XFDL to XHTML+ XForms along
> with this. Apply this XSL to the attached XFDL. You can see that the
> constraints in the <format> tag are not applied. We need to convert
all
> these constraints in the <format> tag in XFDL to the corresponding
> xforms:bind attributes in XForms. Also, see the alert icon coming in
the
> top left corner. Also, the width for input controls is not set.
>
> Another problem with this code is that it is not generic. As branching
> increases, (eg, xforms:group has got more number of branches than
> xforms:output), the looping too goes deeper. I don't think this is a
> good way to write XSL. For eg, there can be any number of xforms:group
> control under another xforms:group. Is there any generic way, so that
we
> can optimize the code for any controls?
>
> Hope you can help me out in solving the issues.
>
> Thanks in advance
> Jency
>
> -----Original Message-----
> From:
[hidden email] [mailto:
[hidden email]] On Behalf Of
> Alessandro Vernet
> Sent: Monday, February 05, 2007 1:04 PM
> To:
[hidden email]
> Subject: Re: [ops-users] XFDL Integration
>
> Hi Jency,
>
> On 1/31/07, Jency Chackummoottil
> <
[hidden email]> wrote:
> > One difficulty I faced during the transformation of XFDL to XHTML
> using
> > XSLT is that in XFDL, we can set the datatype for an input field,
its
> > min length, max length etc using a non-xform tag (<format>). Please
> > refer the attached XFDL document. But in xforms, we add this in
> > xforms:model using xforms:bind. So, using XSLT, we need to convert
all
> > these constraints in the <format> tag in XFDL to the corresponding
> > xforms:bind attributes in XForms.
>
> Now I see the <format> element which I overlooked the first time I
> went through your XFDL example. So we can have things like:
>
> <format>
> <datatype>string</datatype>
> <constraints>
> <length>
> <min>0</min>
> <max>20</max>
> </length>
> </constraints>
> </format>
>
> > Another problem I faced is related to the alert icon. I have set
some
> > constraints on certain fields and using XSLT, I placed all the
> controls
> > in correct position. But if a constraint failed, the alert icon is
> shown
> > at the top left corner.
>
> Are you saying that you would like the alert icon to be displayed next
> to the field but that it gets displayed at the top left corner? If
> this is the case, I don't know why this would happen. I would have to
> try this out.
>
> > Also, not all the controls are positioned with absolute coordinates.
> For
> > eg, the controls placed inside a xforms:repeat are not positioned
> using
> > absolute coordinates.
>
> Yes, that is an interesting case. And I don't fully understand yet how
> the repeat works in XFDL just by looking at the example. But before we
> tackle this down, we can start with the 2 other issues you mentioned.
>
> I have some ideas on how to convert the <format> into binds, but the
> devil lies in the details of the implementation. So rather than trying
> to describe it, I would like to give it a try. Do you have some code
> already to do this conversion in XSLT? Would you be willing to
> contribute it and share it with the community so we can build on it?
> And who knows, if this experiment is successful, this could even ship
> out of the box with Orbeon Forms.
>
> Alex
> --
> Orbeon Forms - Web Forms for the Enterprise, Done the Right Way
>
http://www.orbeon.com/>
>
>
> --
> You receive this message as a subscriber of the
mailing list.
> To unsubscribe: mailto:
[hidden email]
> For general help: mailto:
[hidden email]?subject=help
> ObjectWeb mailing lists service home page:
>
>
>
--
Orbeon Forms - Web Forms for the Enterprise, Done the Right Way
http://www.orbeon.com/--
You receive this message as a subscriber of the
[hidden email] mailing list.
To unsubscribe: mailto:
[hidden email]
For general help: mailto:
[hidden email]?subject=help
ObjectWeb mailing lists service home page:
http://www.objectweb.org/wws