xsltforms-support Mailing List for XSLTForms (Page 49)
Brought to you by:
alain-couthures
Menu
▾
▴
xsltforms-support — XSLTForms support list
You can subscribe to this list here.
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(6) |
Jun
(9) |
Jul
(16) |
Aug
(5) |
Sep
(43) |
Oct
(36) |
Nov
(58) |
Dec
(43) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2010 |
Jan
(79) |
Feb
(81) |
Mar
(107) |
Apr
(93) |
May
(85) |
Jun
(54) |
Jul
(64) |
Aug
(54) |
Sep
(45) |
Oct
(53) |
Nov
(34) |
Dec
(77) |
| 2011 |
Jan
(56) |
Feb
(53) |
Mar
(52) |
Apr
(66) |
May
(44) |
Jun
(16) |
Jul
(28) |
Aug
(5) |
Sep
(15) |
Oct
(21) |
Nov
(51) |
Dec
(46) |
| 2012 |
Jan
(16) |
Feb
(38) |
Mar
(47) |
Apr
(45) |
May
(41) |
Jun
(41) |
Jul
(72) |
Aug
(17) |
Sep
(10) |
Oct
(16) |
Nov
(29) |
Dec
(30) |
| 2013 |
Jan
(25) |
Feb
(13) |
Mar
(20) |
Apr
(25) |
May
(34) |
Jun
(8) |
Jul
(12) |
Aug
(9) |
Sep
(21) |
Oct
(19) |
Nov
(6) |
Dec
(2) |
| 2014 |
Jan
(14) |
Feb
(8) |
Mar
(7) |
Apr
(13) |
May
(33) |
Jun
(13) |
Jul
(6) |
Aug
(5) |
Sep
(5) |
Oct
(34) |
Nov
(7) |
Dec
|
| 2015 |
Jan
(1) |
Feb
(6) |
Mar
(17) |
Apr
(12) |
May
(10) |
Jun
(18) |
Jul
(31) |
Aug
(9) |
Sep
(3) |
Oct
(6) |
Nov
(19) |
Dec
(1) |
| 2016 |
Jan
(18) |
Feb
(4) |
Mar
(13) |
Apr
(19) |
May
|
Jun
(17) |
Jul
(7) |
Aug
|
Sep
(3) |
Oct
(6) |
Nov
(3) |
Dec
|
| 2017 |
Jan
(5) |
Feb
(17) |
Mar
(4) |
Apr
(8) |
May
(3) |
Jun
|
Jul
(8) |
Aug
(2) |
Sep
|
Oct
(5) |
Nov
(6) |
Dec
(4) |
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(6) |
Nov
|
Dec
(1) |
| 2019 |
Jan
|
Feb
|
Mar
(4) |
Apr
(2) |
May
(4) |
Jun
|
Jul
|
Aug
(2) |
Sep
(7) |
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
(13) |
Feb
(17) |
Mar
(8) |
Apr
(11) |
May
(15) |
Jun
(11) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(6) |
| 2021 |
Jan
(9) |
Feb
(26) |
Mar
(17) |
Apr
|
May
(7) |
Jun
(18) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(10) |
| 2022 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
(2) |
Sep
(3) |
Oct
(2) |
Nov
(10) |
Dec
(1) |
| 2023 |
Jan
(10) |
Feb
|
Mar
(7) |
Apr
(8) |
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
(8) |
Oct
(11) |
Nov
(8) |
Dec
(5) |
| 2024 |
Jan
(7) |
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2025 |
Jan
(4) |
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Benoit V. <bvi...@la...> - 2012-03-19 20:36:18
|
Hi Alain, I’m trying the very interesting AVT feature, but I have a small problem with host language attributes like @class when they are included in xforms elements. Example : <?xml-stylesheet href="xsltforms/xsltforms.xsl" type="text/xsl"?> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:xf="http://www.w3.org/2002/xforms" xmlns:ev="http://www.w3.org/2001/xml-events" xmlns:sample="http://www.agencexml.com/sample"> <head> <style typr="text/css"> .red_class { color: red; } </style> <title>Test AVT in @class</title> <xf:model> <xf:instance id="colors"> <data xmlns=""> <c>red</c> </data> </xf:instance> </xf:model> </head> <body> <xf:output ref="c" class="{c}_class"></xf:output> <p class="{c}_class">RED</p> </body> </html> The first @class (in <xf :output>) is never instanciated but the second (in <p>) works fine. Is that a normal behaviour for AVT ? Regards Benoit |
|
From: Alain C. <ala...@ag...> - 2012-03-15 22:18:36
|
Could you please check with this minimal test case?
<html
xmlns="http://www.w3.org/1999/xhtml"
xmlns:xf="http://www.w3.org/2002/xforms"
>
<head>
<title>Select1 appearance="full"</title>
<xf:model>
<xf:instance id="volume">
<data xmlns="">
<is-orphan/>
</data>
</xf:instance>
</xf:model>
</head>
<body>
<xf:select1 ref="instance('volume')/is-orphan" appearance="full">
<xf:label>Orphan</xf:label>
<xf:item>
<xf:label>Yes</xf:label>
<xf:value>true</xf:value>
</xf:item>
<xf:item>
<xf:label>No</xf:label>
<xf:value>false</xf:value>
</xf:item>
</xf:select1>
</body>
</html>
Is the XSLT transformation performed at server-side?
-Alain
Le 15/03/2012 22:59, Joe Wicentowski a écrit :
> Hi Alain,
>
> Sorry, I just realized you said you could *not* reproduce the error.
> I'll do some more testing. If I still have the error, is there a
> more complete error message that I could send to help you?
>
> Thanks again,
> Joe
>
> Sent from my iPhone
>
> On Thursday, March 15, 2012 at 4:47 PM, Alain Couthures wrote:
>
>> Hi Joe,
>>
>> I tested again with Chrome (17.0.963.79) and your code but didn't
>> succeed in reproducing this issue (Please have a look at the attached
>> browser capture on Windows).
>>
>> The stack dump provided in your capture is pointing to a function used
>> to locate the Javascript object for the select1 control from an item.
>>
>> Are you using Windows??
>>
>> Thank you for your feedbacks!
>>
>> -Alain
>>
>> Le 15/03/2012 18:52, Joe Wicentowski a écrit :
>>> Hi Alain and Conal,
>>>
>>> Thanks for your replies. I've just now had the chance to check out
>>> XSLTForms from SVN trunk (rev. 534) and try my code again in Chrome.
>>> Alain - unfortunately, I am still seeing the same error, even using
>>> rev. 534. I've attached an updated image showing the error I see in
>>> Chrome (17.0.963.46 m). The code that is responsible for the error in
>>> Chrome is:
>>>
>>> <xf:select1 ref="instance('volume')/is-orphan" appearance="full">
>>> <xf:label>Orphan</xf:label>
>>> <xf:item>
>>> <xf:label>Yes</xf:label>
>>> <xf:value>true</xf:value>
>>> </xf:item>
>>> <xf:item>
>>> <xf:label>No</xf:label>
>>> <xf:value>false</xf:value>
>>> </xf:item>
>>> </xf:select1>
>>>
>>> The same code works fine in Firefox (4.0). Removing
>>> @appearance="full" eliminates the error in Chrome, but I would prefer
>>> to see the radio buttons.
>>>
>>> Thanks in advance for any suggestions!
>>> Joe
>>>
>>> p.s. Conal - you were correct in thinking that my @full="appearance"
>>> was just a typo in my email, not in my code - but apologies for the
>>> error.
>>>
>>> On Thu, Feb 16, 2012 at 7:37 PM, Conal
>>> Tuohy<con...@ve...> wrote:
>>>> Maybe this is just a typo in your email, Joe, but shouldn't you have
>>>> @appearance="full"?
>>>>
>>>>
>>>> On 16/02/12 08:40, Joe Wicentowski wrote:
>>>>> Hello,
>>>>>
>>>>> I have a form that fails in Chrome (17.0) when I add the
>>>>> @full="appearance" attribute on a select1 element. Without the
>>>>> attribute, the form displays without error, but with the attribute, I
>>>>> get an error - please see my attached image.
>>>>>
>>>>> When I use Firefox (4.0), the form works whether I have this
>>>>> attribute or
>>>>> not.
>>>>>
>>>>> Could you please let me know if this is a known issue with XSLTForms
>>>>> Beta 3, or suggest some troubleshooting steps? I'm happy to test.
>>>>>
>>>>> Thanks,
>>>>> Joe
>>>>
>>>> --
>>>> Conal Tuohy
>>>> eResearch Business Analyst
>>>> Victorian eResearch Strategic Initiative
>>>> +61-466324297
>>
>> Attachments:
>> - select1-chrome.png
>
|
|
From: Joe W. <jo...@gm...> - 2012-03-15 21:59:35
|
Hi Alain,
Sorry, I just realized you said you could *not* reproduce the error. I'll do some more testing. If I still have the error, is there a more complete error message that I could send to help you?
Thanks again,
Joe
Sent from my iPhone
On Thursday, March 15, 2012 at 4:47 PM, Alain Couthures wrote:
> Hi Joe,
>
> I tested again with Chrome (17.0.963.79) and your code but didn't
> succeed in reproducing this issue (Please have a look at the attached
> browser capture on Windows).
>
> The stack dump provided in your capture is pointing to a function used
> to locate the Javascript object for the select1 control from an item.
>
> Are you using Windows??
>
> Thank you for your feedbacks!
>
> -Alain
>
> Le 15/03/2012 18:52, Joe Wicentowski a écrit :
> > Hi Alain and Conal,
> >
> > Thanks for your replies. I've just now had the chance to check out
> > XSLTForms from SVN trunk (rev. 534) and try my code again in Chrome.
> > Alain - unfortunately, I am still seeing the same error, even using
> > rev. 534. I've attached an updated image showing the error I see in
> > Chrome (17.0.963.46 m). The code that is responsible for the error in
> > Chrome is:
> >
> > <xf:select1 ref="instance('volume')/is-orphan" appearance="full">
> > <xf:label>Orphan</xf:label>
> > <xf:item>
> > <xf:label>Yes</xf:label>
> > <xf:value>true</xf:value>
> > </xf:item>
> > <xf:item>
> > <xf:label>No</xf:label>
> > <xf:value>false</xf:value>
> > </xf:item>
> > </xf:select1>
> >
> > The same code works fine in Firefox (4.0). Removing
> > @appearance="full" eliminates the error in Chrome, but I would prefer
> > to see the radio buttons.
> >
> > Thanks in advance for any suggestions!
> > Joe
> >
> > p.s. Conal - you were correct in thinking that my @full="appearance"
> > was just a typo in my email, not in my code - but apologies for the
> > error.
> >
> > On Thu, Feb 16, 2012 at 7:37 PM, Conal Tuohy<con...@ve...> wrote:
> > > Maybe this is just a typo in your email, Joe, but shouldn't you have
> > > @appearance="full"?
> > >
> > >
> > > On 16/02/12 08:40, Joe Wicentowski wrote:
> > > > Hello,
> > > >
> > > > I have a form that fails in Chrome (17.0) when I add the
> > > > @full="appearance" attribute on a select1 element. Without the
> > > > attribute, the form displays without error, but with the attribute, I
> > > > get an error - please see my attached image.
> > > >
> > > > When I use Firefox (4.0), the form works whether I have this attribute or
> > > > not.
> > > >
> > > > Could you please let me know if this is a known issue with XSLTForms
> > > > Beta 3, or suggest some troubleshooting steps? I'm happy to test.
> > > >
> > > > Thanks,
> > > > Joe
> > > >
> > >
> > >
> > > --
> > > Conal Tuohy
> > > eResearch Business Analyst
> > > Victorian eResearch Strategic Initiative
> > > +61-466324297
> > >
> >
> >
>
>
>
>
>
> Attachments:
> - select1-chrome.png
>
|
|
From: Joe W. <jo...@gm...> - 2012-03-15 21:49:21
|
Hi Alain,
Yes, I'm on Windows XP SP3 on this machine.
Thanks,
Joe
Sent from my iPhone
On Thursday, March 15, 2012 at 4:47 PM, Alain Couthures wrote:
> Hi Joe,
>
> I tested again with Chrome (17.0.963.79) and your code but didn't
> succeed in reproducing this issue (Please have a look at the attached
> browser capture on Windows).
>
> The stack dump provided in your capture is pointing to a function used
> to locate the Javascript object for the select1 control from an item.
>
> Are you using Windows??
>
> Thank you for your feedbacks!
>
> -Alain
>
> Le 15/03/2012 18:52, Joe Wicentowski a écrit :
> > Hi Alain and Conal,
> >
> > Thanks for your replies. I've just now had the chance to check out
> > XSLTForms from SVN trunk (rev. 534) and try my code again in Chrome.
> > Alain - unfortunately, I am still seeing the same error, even using
> > rev. 534. I've attached an updated image showing the error I see in
> > Chrome (17.0.963.46 m). The code that is responsible for the error in
> > Chrome is:
> >
> > <xf:select1 ref="instance('volume')/is-orphan" appearance="full">
> > <xf:label>Orphan</xf:label>
> > <xf:item>
> > <xf:label>Yes</xf:label>
> > <xf:value>true</xf:value>
> > </xf:item>
> > <xf:item>
> > <xf:label>No</xf:label>
> > <xf:value>false</xf:value>
> > </xf:item>
> > </xf:select1>
> >
> > The same code works fine in Firefox (4.0). Removing
> > @appearance="full" eliminates the error in Chrome, but I would prefer
> > to see the radio buttons.
> >
> > Thanks in advance for any suggestions!
> > Joe
> >
> > p.s. Conal - you were correct in thinking that my @full="appearance"
> > was just a typo in my email, not in my code - but apologies for the
> > error.
> >
> > On Thu, Feb 16, 2012 at 7:37 PM, Conal Tuohy<con...@ve...> wrote:
> > > Maybe this is just a typo in your email, Joe, but shouldn't you have
> > > @appearance="full"?
> > >
> > >
> > > On 16/02/12 08:40, Joe Wicentowski wrote:
> > > > Hello,
> > > >
> > > > I have a form that fails in Chrome (17.0) when I add the
> > > > @full="appearance" attribute on a select1 element. Without the
> > > > attribute, the form displays without error, but with the attribute, I
> > > > get an error - please see my attached image.
> > > >
> > > > When I use Firefox (4.0), the form works whether I have this attribute or
> > > > not.
> > > >
> > > > Could you please let me know if this is a known issue with XSLTForms
> > > > Beta 3, or suggest some troubleshooting steps? I'm happy to test.
> > > >
> > > > Thanks,
> > > > Joe
> > > >
> > >
> > >
> > > --
> > > Conal Tuohy
> > > eResearch Business Analyst
> > > Victorian eResearch Strategic Initiative
> > > +61-466324297
> > >
> >
> >
>
>
>
>
>
> Attachments:
> - select1-chrome.png
>
|
|
From: Alain C. <ala...@ag...> - 2012-03-15 20:47:15
|
Hi Joe,
I tested again with Chrome (17.0.963.79) and your code but didn't
succeed in reproducing this issue (Please have a look at the attached
browser capture on Windows).
The stack dump provided in your capture is pointing to a function used
to locate the Javascript object for the select1 control from an item.
Are you using Windows??
Thank you for your feedbacks!
-Alain
Le 15/03/2012 18:52, Joe Wicentowski a écrit :
> Hi Alain and Conal,
>
> Thanks for your replies. I've just now had the chance to check out
> XSLTForms from SVN trunk (rev. 534) and try my code again in Chrome.
> Alain - unfortunately, I am still seeing the same error, even using
> rev. 534. I've attached an updated image showing the error I see in
> Chrome (17.0.963.46 m). The code that is responsible for the error in
> Chrome is:
>
> <xf:select1 ref="instance('volume')/is-orphan" appearance="full">
> <xf:label>Orphan</xf:label>
> <xf:item>
> <xf:label>Yes</xf:label>
> <xf:value>true</xf:value>
> </xf:item>
> <xf:item>
> <xf:label>No</xf:label>
> <xf:value>false</xf:value>
> </xf:item>
> </xf:select1>
>
> The same code works fine in Firefox (4.0). Removing
> @appearance="full" eliminates the error in Chrome, but I would prefer
> to see the radio buttons.
>
> Thanks in advance for any suggestions!
> Joe
>
> p.s. Conal - you were correct in thinking that my @full="appearance"
> was just a typo in my email, not in my code - but apologies for the
> error.
>
> On Thu, Feb 16, 2012 at 7:37 PM, Conal Tuohy<con...@ve...> wrote:
>> Maybe this is just a typo in your email, Joe, but shouldn't you have
>> @appearance="full"?
>>
>>
>> On 16/02/12 08:40, Joe Wicentowski wrote:
>>> Hello,
>>>
>>> I have a form that fails in Chrome (17.0) when I add the
>>> @full="appearance" attribute on a select1 element. Without the
>>> attribute, the form displays without error, but with the attribute, I
>>> get an error - please see my attached image.
>>>
>>> When I use Firefox (4.0), the form works whether I have this attribute or
>>> not.
>>>
>>> Could you please let me know if this is a known issue with XSLTForms
>>> Beta 3, or suggest some troubleshooting steps? I'm happy to test.
>>>
>>> Thanks,
>>> Joe
>>
>> --
>> Conal Tuohy
>> eResearch Business Analyst
>> Victorian eResearch Strategic Initiative
>> +61-466324297
>>
>>
|
|
From: Joe W. <jo...@gm...> - 2012-03-15 17:53:10
|
Hi Alain and Conal,
Thanks for your replies. I've just now had the chance to check out
XSLTForms from SVN trunk (rev. 534) and try my code again in Chrome.
Alain - unfortunately, I am still seeing the same error, even using
rev. 534. I've attached an updated image showing the error I see in
Chrome (17.0.963.46 m). The code that is responsible for the error in
Chrome is:
<xf:select1 ref="instance('volume')/is-orphan" appearance="full">
<xf:label>Orphan</xf:label>
<xf:item>
<xf:label>Yes</xf:label>
<xf:value>true</xf:value>
</xf:item>
<xf:item>
<xf:label>No</xf:label>
<xf:value>false</xf:value>
</xf:item>
</xf:select1>
The same code works fine in Firefox (4.0). Removing
@appearance="full" eliminates the error in Chrome, but I would prefer
to see the radio buttons.
Thanks in advance for any suggestions!
Joe
p.s. Conal - you were correct in thinking that my @full="appearance"
was just a typo in my email, not in my code - but apologies for the
error.
On Thu, Feb 16, 2012 at 7:37 PM, Conal Tuohy <con...@ve...> wrote:
> Maybe this is just a typo in your email, Joe, but shouldn't you have
> @appearance="full"?
>
>
> On 16/02/12 08:40, Joe Wicentowski wrote:
>>
>> Hello,
>>
>> I have a form that fails in Chrome (17.0) when I add the
>> @full="appearance" attribute on a select1 element. Without the
>> attribute, the form displays without error, but with the attribute, I
>> get an error - please see my attached image.
>>
>> When I use Firefox (4.0), the form works whether I have this attribute or
>> not.
>>
>> Could you please let me know if this is a known issue with XSLTForms
>> Beta 3, or suggest some troubleshooting steps? I'm happy to test.
>>
>> Thanks,
>> Joe
>
>
> --
> Conal Tuohy
> eResearch Business Analyst
> Victorian eResearch Strategic Initiative
> +61-466324297
>
|
|
From: Alain C. <ala...@ag...> - 2012-03-14 21:00:16
|
Hello, A new W3C Community Group has just been created today for XForms Users: http://www.w3.org/community/xformsusers/ Thank you for joining it! -Alain |
|
From: Alain C. <ala...@ag...> - 2012-03-14 20:36:12
|
Hi Benoit, Oops! I forgot to escape characters such as &, < and > in the text value of the corresponding XML element. It wouldn't append if only a native Javascript API allowed to create an XML document in a simpler way than strings concatenation... Thanks! -Alain Le 09/03/2012 10:20, bvi...@la... a écrit : > Hi Alain, > > My problem is quite simple : when I call the profiler from a page which have more than one parameter in it's URL, the profiler doesn't work. > > What I understood is : > 1) The URL looks like "http://localhost/test.xforms?p1=a&p2=b > 2) So in the profiling_data, the element contains a "&" > 3) The deserialization used by "opener://" fail on the "&" because it tries to resolve an Entity ref"&...;" > > I think we can have this problem each time an instance contains specials chars in it and is shared between a form and a subform. > > Regards > Benoit > > |
|
From: Alain C. <ala...@ag...> - 2012-03-14 19:48:11
|
Hello Javier, Patterns might contain curly brackets and, in host languages such as HTML or SVG, curly brackets are now used for AVT: I will filter this (XML Schema definitions cannot contain AVT anyway). Looking at your form, I saw that you defined repeats within tables without having tr elements. This is not well treated in browsers. Thanks! -Alain Le 13/03/2012 01:15, Javier Díaz a écrit : > Hello, > > I have recently updated to last version of xsltforms and it fails with > the attached xform. With r528 it works. I think it is related with > schemas of the form. > > The error that appears is: > > XSLTForms Exception > -------------------------- > > Error initializing : > > ([object > Object],"xsltforms-mainform-pattern-0")@http://localhost/xsltforms/xsltforms.js:4621 > XsltForms_avt([object > Object],"xsltforms-mainform-pattern-0","value",[object > Object])@http://localhost/xsltforms/xsltforms.js:4953 > xsltforms_initImpl()@http://localhost/xsltforms.data/schema_error.xml:140 > xsltforms_init()@http://localhost/xsltforms.data/schema_error.xml:2 > onload([object Event])@http://localhost/xsltforms.data/schema_error.xml:1 > > > TypeError > > this.element is null > > Best Regards, > Javier > |
|
From: Alain C. <ala...@ag...> - 2012-03-14 19:24:03
|
Hello Javier, Until recently, an empty required input control was displayed with two icons: the required icon (the star character in red) and the invalid icon (a white cross in the middle of a red circle). As in Orbeon, it was then changed to not display the invalid icon when the input control is empty considering that this should be enough for the user to locate this. As an immediate consequence, the alert message associated to the control is currently not displayed on the required icon. This will be considered after the 1.0RC release. BTW, I'm not sure that an alert message for a required control is very interesting when it just says that the control has to be non-empty... Thank you for your feedbacks! -Alain Le 14/03/2012 16:31, Javier Díaz a écrit : > It happens it in firefox. I didn't tested it in any other browser. > > In my previous mail I sent attached a test case. The binding is correct: > > <xf:bind constraint="true()" nodeset="/SELECCION/FILTRO/TIPO" readonly="false()" relevant="true()" required="true()"/> > > Saludos, > Javier > > El 14/03/12 13:19, William Velasquez escribió: >> Which browser did you use to test? >> >> I have this problem with Opera and Safari. >> >> Maybe be you are using required="true" instead of required="true()" in >> bindings. >> >> >> >> >> On 13.03.2012 04:04, Javier Díaz wrote: >>> Hello again, >>> >>> I am updating xsltforms from a very old version (r362) and I have >>> detected that in the last versions I have tested (r534 y r528) alert >>> icon doesn't appear when required. I send attached an example, alert >>> icon should appear when nothing is selected. >>> >>> It works in revision r489 (last version without data island). >>> >>> Best Regards, >>> Javier >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> ************************************************************************************************************************************************ >>> *La información contenida en este mensaje de correo electrónico es >>> confidencial y puede revestir el carácter de reservada. * >>> *Está dirigida exclusivamente a la persona destinataria. >>> >>> * >>> *El acceso o cualquier uso por parte de cualquier otra persona de >>> este mensaje no están autorizados y pueden ser ilegales.* >>> *Si no es Ud. la persona destinataria, le rogamos que proceda a >>> borrarlo. >>> * >>> *The information in this e-mail is confidential and may be legally >>> privileged. >>> * >>> *It is intended solely for the addressee. >>> >>> * >>> *Access or any use by any other person to this Internet e-mail is not >>> authorised and may be unlawful. * >>> *If you are not the intended recipient, please delete this e-mail. >>> >>> * >>> >>> ************************************************************************************************************************************************ > > > > > > > > > > > > > > > ************************************************************************************************************************************************ > *La informaci?n contenida en este mensaje de correo electr?nico es confidencial y puede revestir el car?cter de reservada. * > *Est? dirigida exclusivamente a la persona destinataria. * > *El acceso o cualquier uso por parte de cualquier otra persona de este mensaje no est?n autorizados y pueden ser ilegales.* > *Si no es Ud. la persona destinataria, le rogamos que proceda a borrarlo. * > *The information in this e-mail is confidential and may be legally privileged. * > *It is intended solely for the addressee. * > *Access or any use by any other person to this Internet e-mail is not authorised and may be unlawful. * > *If you are not the intended recipient, please delete this e-mail. * > ************************************************************************************************************************************************ > > > > ------------------------------------------------------------------------------ > Virtualization& Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing > also focuses on allowing computing to be delivered as a service. > http://www.accelacomm.com/jaw/sfnl/114/51521223/ > > > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support |
|
From: Javier D. <jd...@tc...> - 2012-03-14 15:31:31
|
It happens it in firefox. I didn't tested it in any other browser. In my previous mail I sent attached a test case. The binding is correct: <xf:bind constraint="true()" nodeset="/SELECCION/FILTRO/TIPO" readonly="false()" relevant="true()" required="true()"/> Saludos, Javier El 14/03/12 13:19, William Velasquez escribió: > Which browser did you use to test? > > I have this problem with Opera and Safari. > > Maybe be you are using required="true" instead of required="true()" in > bindings. > > > > > On 13.03.2012 04:04, Javier Díaz wrote: >> Hello again, >> >> I am updating xsltforms from a very old version (r362) and I have >> detected that in the last versions I have tested (r534 y r528) alert >> icon doesn't appear when required. I send attached an example, alert >> icon should appear when nothing is selected. >> >> It works in revision r489 (last version without data island). >> >> Best Regards, >> Javier >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> ************************************************************************************************************************************************ >> *La información contenida en este mensaje de correo electrónico es >> confidencial y puede revestir el carácter de reservada. * >> *Está dirigida exclusivamente a la persona destinataria. >> >> * >> *El acceso o cualquier uso por parte de cualquier otra persona de >> este mensaje no están autorizados y pueden ser ilegales.* >> *Si no es Ud. la persona destinataria, le rogamos que proceda a >> borrarlo. >> * >> *The information in this e-mail is confidential and may be legally >> privileged. >> * >> *It is intended solely for the addressee. >> >> * >> *Access or any use by any other person to this Internet e-mail is not >> authorised and may be unlawful. * >> *If you are not the intended recipient, please delete this e-mail. >> >> * >> >> ************************************************************************************************************************************************ ************************************************************************************************************************************************ *La informaciontenida en este mensaje de correo electro es confidencial y puede revestir el carer de reservada. * *Estirigida exclusivamente a la persona destinataria. * *El acceso o cualquier uso por parte de cualquier otra persona de este mensaje no estautorizados y pueden ser ilegales.* *Si no es Ud. la persona destinataria, le rogamos que proceda a borrarlo. * *The information in this e-mail is confidential and may be legally privileged. * *It is intended solely for the addressee. * *Access or any use by any other person to this Internet e-mail is not authorised and may be unlawful. * *If you are not the intended recipient, please delete this e-mail. * ************************************************************************************************************************************************ |
|
From: William V. <wi...@bi...> - 2012-03-14 12:19:55
|
Which browser did you use to test? I have this problem with Opera and Safari. Maybe be you are using required="true" instead of required="true()" in bindings. On 13.03.2012 04:04, Javier Díaz wrote: > Hello again, > > I am updating xsltforms from a very old version (r362) and I have > detected that in the last versions I have tested (r534 y r528) alert > icon doesn't appear when required. I send attached an example, alert > icon should appear when nothing is selected. > > It works in revision r489 (last version without data island). > > Best Regards, > Javier > > > > > > > > > > > > > > > > > ************************************************************************************************************************************************ > *La información contenida en este mensaje de correo electrónico es > confidencial y puede revestir el carácter de reservada. * > *Está dirigida exclusivamente a la persona destinataria. > > * > *El acceso o cualquier uso por parte de cualquier otra persona de > este mensaje no están autorizados y pueden ser ilegales.* > *Si no es Ud. la persona destinataria, le rogamos que proceda a > borrarlo. > * > *The information in this e-mail is confidential and may be legally > privileged. > * > *It is intended solely for the addressee. > > * > *Access or any use by any other person to this Internet e-mail is not > authorised and may be unlawful. * > *If you are not the intended recipient, please delete this e-mail. > > * > > ************************************************************************************************************************************************ -- William David Velasquez Laboratorio de Software Bitlab http://bitlab.com.co Movil 310 412 0218 |
|
From: Ioan F. <mi...@gm...> - 2012-03-13 15:11:35
|
It may be possible in XSLTForms?Now, the focus can be set only on the input fields.(Or, just as I have obtained.) Greetings, Ioan |
|
From: Javier D. <jd...@tc...> - 2012-03-13 08:04:38
|
Hello again, I am updating xsltforms from a very old version (r362) and I have detected that in the last versions I have tested (r534 y r528) alert icon doesn't appear when required. I send attached an example, alert icon should appear when nothing is selected. It works in revision r489 (last version without data island). Best Regards, Javier ************************************************************************************************************************************************ *La información contenida en este mensaje de correo electrónico es confidencial y puede revestir el carácter de reservada. * *Está dirigida exclusivamente a la persona destinataria. * *El acceso o cualquier uso por parte de cualquier otra persona de este mensaje no están autorizados y pueden ser ilegales.* *Si no es Ud. la persona destinataria, le rogamos que proceda a borrarlo. * *The information in this e-mail is confidential and may be legally privileged. * *It is intended solely for the addressee. * *Access or any use by any other person to this Internet e-mail is not authorised and may be unlawful. * *If you are not the intended recipient, please delete this e-mail. * ************************************************************************************************************************************************ |
|
From: Javier D. <jd...@tc...> - 2012-03-13 00:29:18
|
Hello, I have recently updated to last version of xsltforms and it fails with the attached xform. With r528 it works. I think it is related with schemas of the form. The error that appears is: XSLTForms Exception -------------------------- Error initializing : ([object Object],"xsltforms-mainform-pattern-0")@http://localhost/xsltforms/xsltforms.js:4621 XsltForms_avt([object Object],"xsltforms-mainform-pattern-0","value",[object Object])@http://localhost/xsltforms/xsltforms.js:4953 xsltforms_initImpl()@http://localhost/xsltforms.data/schema_error.xml:140 xsltforms_init()@http://localhost/xsltforms.data/schema_error.xml:2 onload([object Event])@http://localhost/xsltforms.data/schema_error.xml:1 TypeError this.element is null Best Regards, Javier ************************************************************************************************************************************************ *La información contenida en este mensaje de correo electrónico es confidencial y puede revestir el carácter de reservada. * *Está dirigida exclusivamente a la persona destinataria. * *El acceso o cualquier uso por parte de cualquier otra persona de este mensaje no están autorizados y pueden ser ilegales.* *Si no es Ud. la persona destinataria, le rogamos que proceda a borrarlo. * *The information in this e-mail is confidential and may be legally privileged. * *It is intended solely for the addressee. * *Access or any use by any other person to this Internet e-mail is not authorised and may be unlawful. * *If you are not the intended recipient, please delete this e-mail. * ************************************************************************************************************************************************ |
|
From: Leigh L K. Jr <lei...@xe...> - 2012-03-12 21:27:34
|
Th forms WG recently resolved to make hint/@appearance='minimal' put the
hint inside the input in a desktop or mobile browser.
I propose that XSLTForms use @appearance='compact' for its current
behavior (an icon with mouseover).
Many graphic designers want more control over hint appearance, so I
propose @appearance='full' place the hint text inline after the form
control.
<span class="xforms-hint*xforms-appearance-full*">
/ ... no span/@class='xforms-hint-icon"
... rest is the same ...
/</span>
In the @appearance='compact' case I propose
<span class="xforms-hint *xforms-appearance-compact*">
/ ...rest is the same ...
/ </span>
XSLTForms does not yet implement appearance='minimal' but when it does I
suspect it will use the HTML5 @placeholder when that is available, so
the form author should not rely on a span whose class is
xforms-appearance-minimal.
The changes below to xsltforms.css are the minimal to demonstrate the
functionality. It might be better to output class="xforms-hint
xforms-appearance-compact" even when there is no @appearance; then the
default CSS would style only that the case
.xforms-hint.xforms-appearance-compact, and the form author CSS could
style .xforms-hint.xforms-appearance-full and not have to override any
CSS behavior.
1. Add hint/@appearance='full'. Make current behavior (and default with
no @apperance) hint/@appearance='compact'
Index: xsltforms.css
===================================================================
--- xsltforms.css (revision 66884)
+++ xsltforms.css (working copy)
@@ -225,6 +225,17 @@
box-sizing : border-box;
}
+span.xforms-hint.xforms-appearance-full > span.xforms-hint-value {
+ display : inline;
+ border : none;
+ white-space: normal;
+ background-color : transparent;
+ white-space: normal;
+ margin-top : 0px;
+ margin-left : 20em;
+ width : 200px;
+}
+
span.xforms-alert {
display : none;
}
Index: xsltforms.xsl
===================================================================
--- xsltforms.xsl (revision 66884)
+++ xsltforms.xsl (working copy)
@@ -1215,8 +1215,17 @@
</xsl:if>
</span>
<xsl:if test="xforms:hint">
- <span class="xforms-hint">
- <span class="xforms-hint-icon"
onmouseover="XsltForms_browser.show(this, 'hint', true)"
onmouseout="XsltForms_browser.show(this, 'hint',
false)"> <xsl:text/></span>
+ <xsl:variable name="ha" select="xforms:hint/@appearance" />
+ <span>
+ <xsl:attribute name="class">
+ <xsl:choose>
+ <xsl:when test="$ha">xforms-hint xforms-appearance-<xsl:value-of
select='$ha' /></xsl:when>
+ <xsl:otherwise>xforms-hint</xsl:otherwise>
+ </xsl:choose>
+ </xsl:attribute>
+ <xsl:if test="$ha='compact' or not($ha)">
+ <span class="xforms-hint-icon"
onmouseover="XsltForms_browser.show(this, 'hint', true)"
onmouseout="XsltForms_browser.show(this, 'hint',
false)"> <xsl:text/></span>
+ </xsl:if>
<xsl:variable name="hid">
<xsl:choose>
<xsl:when test="xforms:hint/@id"><xsl:value-of
select="xforms:hint/@id"/></xsl:when>
@@ -1231,10 +1240,10 @@
</xsl:otherwise>
</xsl:choose>
</xsl:variable>
- <span class="xforms-hint-value" id="{$hid}">
- <xsl:apply-templates select="xforms:hint/node()"/>
- </span>
- </span>
+ <span class="xforms-hint-value" id="{$hid}">
+ <xsl:apply-templates select="xforms:hint/node()"/>
+ </span>
+ </span>
</xsl:if>
<xsl:if test="xforms:help[not(@appearance='minimal')]">
<span class="xforms-help">
|
|
From: C. M. Sperberg-M. <cm...@bl...> - 2012-03-09 13:25:56
|
On Mar 8, 2012, at 7:57 PM, C. M. Sperberg-McQueen wrote: > > On Mar 8, 2012, at 12:05 PM, Alain Couthures wrote: > >> The default behavior when a cross-domain request is detected is to generate a GET method with a callback function name. >> >> Are you sure that the PUT submission is sent to the same domain and port?? > > Ah. It could be a port difference -- I am trying to figure out when to > use http and when to use https. I will look more carefully with particular > reference to that. > > Thank you! More systematic tests show (a) that the GET requests with callback function names are indeed logged when there is a mismatch of some kind between the form and the PUT request (in this case, when one is http and the other is https), and (b) that the original cause of my problem (the one that led me to start mucking about with things in the first place) was that the portion of the site where the form resides, and the portion of the site where the PUT must go (into the Subversion-backed WebDAV server) both use HTTP Basic authentication, but used different AuthName parameters. So my browser was failing to use the appropriate credentials to (re-)issue the request, and the PUT was failing with a 401. Thank you, Alain, for your help. MIchael -- **************************************************************** * C. M. Sperberg-McQueen, Black Mesa Technologies LLC * http://www.blackmesatech.com * http://cmsmcq.com/mib * http://balisage.net **************************************************************** |
|
From: <bvi...@la...> - 2012-03-09 09:20:51
|
Hi Alain, My problem is quite simple : when I call the profiler from a page which have more than one parameter in it's URL, the profiler doesn't work. What I understood is : 1) The URL looks like "http://localhost/test.xforms?p1=a&p2=b 2) So in the profiling_data, the element contains a "&" 3) The deserialization used by "opener://" fail on the "&" because it tries to resolve an Entity ref "&...;" I think we can have this problem each time an instance contains specials chars in it and is shared between a form and a subform. Regards Benoit > Une messagerie gratuite, garantie à vie et des services en plus, ça vous tente ? > Je crée ma boîte mail www.laposte.net > Une messagerie gratuite, garantie à vie et des services en plus, ça vous tente ? Je crée ma boîte mail www.laposte.net |
|
From: bvincent.com <bvi...@la...> - 2012-03-09 09:16:47
|
Hi Alain, My problem is quite simple : when I call the profiler from a page which have more than one parameter in it's URL, the profiler doesn't work. What I understood is : 1) The URL looks like "http://localhost/test.xforms?p1=a&p2=b 2) So in the profiling_data, the element contains a "&" 3) The deserialization used by "opener://" fail on the "&" because it tries to resolve an Entity ref "&...;" I think we can have this problem each time an instance contains specials chars in it and is shared between a form and a subform. Regards Benoit Une messagerie gratuite, garantie à vie et des services en plus, ça vous tente ? Je crée ma boîte mail www.laposte.net |
|
From: C. M. Sperberg-M. <cm...@ac...> - 2012-03-09 01:57:23
|
On Mar 8, 2012, at 12:05 PM, Alain Couthures wrote: > The default behavior when a cross-domain request is detected is to generate a GET method with a callback function name. > > Are you sure that the PUT submission is sent to the same domain and port?? Ah. It could be a port difference -- I am trying to figure out when to use http and when to use https. I will look more carefully with particular reference to that. Thank you! >> |
|
From: C. M. Sperberg-M. <cm...@bl...> - 2012-03-08 18:28:01
|
I'm experiencing slightly unexpected behavior with an attempt to save a document on a server. The Subversion repository does not show the new document, and the Apache logs don't show a PUT -- they show a GET, and the URI of the GET is the URI I was trying to PUT the document to, with the string "?callback=jsoninst" appended. The behavior described can be observed both with Beta 3 and with /trunk/build in the current Subversion copy. I'll try to make a stripped down version of the form to make things very very simple for testing. But in the meantime, any advice would be helpful. MIchael Sperberg-McQueen -- **************************************************************** * C. M. Sperberg-McQueen, Black Mesa Technologies LLC * http://www.blackmesatech.com * http://cmsmcq.com/mib * http://balisage.net **************************************************************** |
|
From: Alain C. <ala...@ag...> - 2012-03-08 18:06:09
|
The default behavior when a cross-domain request is detected is to generate a GET method with a callback function name. Are you sure that the PUT submission is sent to the same domain and port?? Thank you for your feedbacks! -Alain Le 08/03/2012 18:54, C. M. Sperberg-McQueen a écrit : > I'm experiencing slightly unexpected behavior with an attempt to > save a document on a server. > > The Subversion repository does not show the new document, and > the Apache logs don't show a PUT -- they show a GET, and the > URI of the GET is the URI I was trying to PUT the document to, with > the string "?callback=jsoninst" appended. > > When I saw unexpected behavior I checked out the Subversion > copy; the unexpected behavior persists when I use /trunk/build > as the XSLTforms directory. > > I'll try to make a stripped down version of the form to make things > very very simple for testing. But in the meantime, any advice would > be helpful. > > MIchael Sperberg-McQueen > > > |
|
From: Andre C. <ac...@01...> - 2012-03-06 16:17:12
|
Hi Alain,
Thank you fro the very useful info.
I upgraded to the latest (Beta3) xsltForms version, but still had the
same error.
Then, I replaced the two instances of 
 for and it now
works ok.
I will remove the duplicate ids in the forms, although the issue did not
seem to be related.
Thank you for great support
Regards,
Andre
> Hi André,
>
> This form contains the Unicode character for a line separator
> (
) instead of
>
> This character is not supported in rev. 490. You could test with the
> latest revision but, recently, the Javascript classes have been
> renamed ("Core" became "XsltForms_browser", for example) and I noticed
> that you are using some of them directly.
>
> If this is not possible for you to replace 
 with and if
> you don't want to upgrade your XSLTForms version now, I can send you a
> patched version of rev. 490.
>
> I also detected duplicate ids in your forms for "stratedit": the main
> instance and a table. This can cause issues difficult to locate.
>
> Thank you for your feedbacks!
>
> -Alain
>
> Le 29/02/2012 18:11, Andre Cusson a écrit :
>> oops, sorry for hijacking and not replacing the message subject, wich
>> this instance tries to fix ...
>>
>> Hi Alain,
>>
>> Sorry for taking your time for this, and I hope that you are fine.
>>
>> On the StratML portal (http://stratml.hyperbase.com/), we have 842
>> preloaded XSLTForms, each loaded with a specific StratML document
>> (see http://stratml.hyperbase.com/documents.html "Edit" links for the
>> forms). They all seem to work fine, even as they get pretty large,
>> but the last one added ( http://stratml.hyperbase.com/documents.html
>> entry #485-LDTC, "Edit" link), which also seems to work fine when I
>> run it locally, returns an error when accessed from the deployed
>> version. The error message is as follows (also attached):
>>
>> Do you have any idea what could cause this?
>>
>> Thank you,
>>
>> Andre
>>
>
|
|
From: Kurt C. <kur...@gm...> - 2012-03-01 23:14:23
|
Alain, Found another bug. For the following page, I'm getting an error "Object #<Text> has no method "getAttribute", apparently triggered off the <text> element below: The web page is: <html xmlns="http://www.w3.org/1999/xhtml" xmlns:xf="http://www.w3.org/2002/xforms"> <head> <title>Trig Functions</title> <xf:model> <xf:instance id="state"> <state xmlns=""> <angle>0</angle> </state> </xf:instance> </xf:model> <script type="text/javascript"><.toFixed(4); }; ]]></script> </head> <body> <div> <table> <tr> <th>Angle</th> <th>sin()</th> <th>cos()</th> <th>tan()</th> </tr> <tr> <td><xf:input ref="angle" incremental="true"/></td> <td><xf:output value="trig('sin',angle)"/></td> <td><xf:output value="trig('cos',angle)"/></td> <td><xf:output value="trig('tan',angle)"/></td> </tr> </table> </div> <svg width="200" height="200" xmlns="http://www.w3.org/2000/svg"> <circle r="100" cx="100" cy="100" fill="white" stroke="black" stroke-width="2"/> <g transform="translate(100,100)"> <path d="M0,0 L0,-80z M0,0 L{80*trig('sin',angle)},{-80*trig('cos',angle)}z" stroke="black" stroke-width="4"/> <g> <text>Test</text> </g> </g> </svg> </body> </html> Kurt Cagle Invited Expert, XForms Working Group, W3C Managing Editor, XMLToday.org kur...@gm... 443-837-8725 On Thu, Mar 1, 2012 at 4:39 PM, Kurt Cagle <kur...@gm...> wrote: > Alain, > > Much thanks! > > Kurt Cagle > Invited Expert, XForms Working Group, W3C > Managing Editor, XMLToday.org > kur...@gm... > 443-837-8725 > > > > > On Thu, Mar 1, 2012 at 4:17 PM, Alain Couthures < > ala...@ag...> wrote: > >> Kurt, >> >> I didn't test before AVT for SVG and I discovered that the DOM API is not >> exactly the same for SVG as for HTML. >> >> I fixed issues about classes and about children vs childNodes. >> >> So now it works for rev.533 with your example in which I added >> style="overflow:hidden" for IE9. >> >> Thank you for your feedbacks! >> >> -Alain >> >> Le 29/02/2012 18:44, Kurt Cagle a écrit : >> >> Alain, >> >> Just wanted to say that I've downloaded and been testing the new AVT >> and JS changes to xsltforms and have only two words: *This ROCKS!!!!* >> >> I think this will have a *profound* impact upon how applications are >> built with XForms and XSLTForms. >> >> The only downside I've seen thus far is that trying to work with >> embedded SVG is generating significant errors. The following illustrates >> this: >> >> ( >> xdmp:set-response-content-type("text/xml"), >> processing-instruction {"xml-stylesheet"} {'type="text/xsl" >> href="/lib/xsltforms/xsltforms.xsl"'}, >> <html xmlns="http://www.w3.org/1999/xhtml" >> xmlns:xf="http://www.w3.org/2002/xforms"> >> <head> >> <title>Background Colors</title> >> <xf:model> >> <xf:instance id="colors"> >> <colors xmlns=""> >> <color name="Blue" code="#0000FF" size="100"/> >> <color name="Green" code="#00FF00" size="120"/> >> <color name="Olive" code="#808000" size="150"/> >> <color name="Orange" code="#F87A17" size="90"/> >> <color name="Pink" code="#FFC0CB" size="200"/> >> <color name="Purple" code="#800080" size="80"/> >> <color name="Red" code="#FF0000" size="150"/> >> <color name="Yellow" code="#FFFF00" size="200"/> >> </colors> >> </xf:instance> >> <xf:instance id="state"> >> <state xmlns=""> >> <color>#0000FF</color> >> </state> >> </xf:instance> >> </xf:model> >> </head> >> <body> >> >> <xf:select1 ref="instance('state')/color"> >> <xf:itemset nodeset="instance('colors')//color"> >> <xf:label ref="@name"/> >> <xf:value ref="@code"/> >> </xf:itemset> >> </xf:select1> >> <input type="text" value="{{instance('state')/*:color}}" >> style="color:{{instance('state')/*:color}}"></input> >> <div >> style="background-color:{{instance('state')/color}};width:{{instance('colors')/color[@code=instance('state')/color]/@size}}px;height:50px;"> >> This is a test.</div> >> <svg width="300" height="300" xmlns="http://www.w3.org/2000/svg"> >> <circle >> r="{{instance('colors')/color[@code=instance('state')/color]/@size}}" >> cx="50" cy="50" fill="red"/> >> </svg> >> </body> >> </html>) >> >> Given that AVT just landed, this is not surprising, just wanted to let >> you know. However, other than that issue, I'm having a blast playing with >> this. >> >> >> On Wed, Feb 29, 2012 at 12:06 PM, Leigh L. Klotz, Jr. < >> Lei...@xe...> wrote: >> >>> Please respond with corrections. >>> Please start new threads for discussion. >>> >>> >> >> > |
|
From: Kurt C. <kur...@gm...> - 2012-03-01 21:39:43
|
Alain, Much thanks! Kurt Cagle Invited Expert, XForms Working Group, W3C Managing Editor, XMLToday.org kur...@gm... 443-837-8725 On Thu, Mar 1, 2012 at 4:17 PM, Alain Couthures < ala...@ag...> wrote: > Kurt, > > I didn't test before AVT for SVG and I discovered that the DOM API is not > exactly the same for SVG as for HTML. > > I fixed issues about classes and about children vs childNodes. > > So now it works for rev.533 with your example in which I added > style="overflow:hidden" for IE9. > > Thank you for your feedbacks! > > -Alain > > Le 29/02/2012 18:44, Kurt Cagle a écrit : > > Alain, > > Just wanted to say that I've downloaded and been testing the new AVT and > JS changes to xsltforms and have only two words: *This ROCKS!!!!* > > I think this will have a *profound* impact upon how applications are > built with XForms and XSLTForms. > > The only downside I've seen thus far is that trying to work with > embedded SVG is generating significant errors. The following illustrates > this: > > ( > xdmp:set-response-content-type("text/xml"), > processing-instruction {"xml-stylesheet"} {'type="text/xsl" > href="/lib/xsltforms/xsltforms.xsl"'}, > <html xmlns="http://www.w3.org/1999/xhtml" > xmlns:xf="http://www.w3.org/2002/xforms"> > <head> > <title>Background Colors</title> > <xf:model> > <xf:instance id="colors"> > <colors xmlns=""> > <color name="Blue" code="#0000FF" size="100"/> > <color name="Green" code="#00FF00" size="120"/> > <color name="Olive" code="#808000" size="150"/> > <color name="Orange" code="#F87A17" size="90"/> > <color name="Pink" code="#FFC0CB" size="200"/> > <color name="Purple" code="#800080" size="80"/> > <color name="Red" code="#FF0000" size="150"/> > <color name="Yellow" code="#FFFF00" size="200"/> > </colors> > </xf:instance> > <xf:instance id="state"> > <state xmlns=""> > <color>#0000FF</color> > </state> > </xf:instance> > </xf:model> > </head> > <body> > > <xf:select1 ref="instance('state')/color"> > <xf:itemset nodeset="instance('colors')//color"> > <xf:label ref="@name"/> > <xf:value ref="@code"/> > </xf:itemset> > </xf:select1> > <input type="text" value="{{instance('state')/*:color}}" > style="color:{{instance('state')/*:color}}"></input> > <div > style="background-color:{{instance('state')/color}};width:{{instance('colors')/color[@code=instance('state')/color]/@size}}px;height:50px;"> > This is a test.</div> > <svg width="300" height="300" xmlns="http://www.w3.org/2000/svg"> > <circle > r="{{instance('colors')/color[@code=instance('state')/color]/@size}}" > cx="50" cy="50" fill="red"/> > </svg> > </body> > </html>) > > Given that AVT just landed, this is not surprising, just wanted to let > you know. However, other than that issue, I'm having a blast playing with > this. > > > On Wed, Feb 29, 2012 at 12:06 PM, Leigh L. Klotz, Jr. < > Lei...@xe...> wrote: > >> Please respond with corrections. >> Please start new threads for discussion. >> >> > > |
97 messages has been excluded from this view by a project administrator.
