xsltforms-support Mailing List for XSLTForms (Page 92)
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: Kostis A. <ank...@gm...> - 2010-03-29 14:26:33
|
On FF, when an external schema is defined, xf:bind elements with 'type' attributes having xsd-types, i.e. "xsd:string, xsd:integer" fail to work, and the form on initialization complains about these types with a «Schema for namespace '' not defined for type string» msg. (or "Schema not defined" on older revisions) - On Chrome and (i think?) IE external schemas work OK. - I didn't manage to determine exactly the revision this behavior was introduced. The beta-2(rev260) release, on FF, although it did not work always quite-well with external schemas, it did *not* produce the err msg, and the attached-here test-case xform works indeed correctly. On rev262, the msg emerges on init, and the xsd-types ceases to work. I include below a test-case reproducing the error, also attached as separate files. Regards, Kostis Anagnostopoulos XForms file: -------------------- <?xml version="1.0" encoding="UTF-8"?> <?xml-stylesheet href="xsltforms/xsltforms.xsl" encoding="UTF-8" type="text/xsl"?> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:xf="http://www.w3.org/2002/xforms" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:data="http://some-uri.org/data" > <head> <title>external-schema</title> <xf:model id="model-main" schema="xsd.xml"> <xf:instance id="inst-main" > <data:root> <data:item /> <data:otherItem /> </data:root> </xf:instance> <xf:bind id="bind-item" nodeset="/data:root/data:item" type="data:Route" /> <xf:bind id="bind-otherItem" nodeset="/data:root/data:otherItem" type="xsd:string" /> </xf:model> </head> <body> Item: <xf:input bind="bind-item" incremental="true" /> OtherItem: <xf:input bind="bind-otherItem" incremental="true" /> </body> </html> XSD file: -------------------- <?xml version="1.0" encoding="UTF-8"?> <xsd:schema elementFormDefault="unqualified" attributeFormDefault="unqualified" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:data="http://some-uri.org/data" targetNamespace="http://some-uri.org/data" > <xsd:simpleType name="someInt"> <xsd:restriction base="xsd:integer"> </xsd:restriction> </xsd:simpleType> </xsd:schema> exa |
|
From: Kostis A. <ank...@gm...> - 2010-03-29 12:21:29
|
The generation of XPATH for <f:bind> elements with no @nodeset attribute
(for instance, when <xf:bind> is used only for its @calculate or MIP
attributes)
fails with a cryptic message, saying: "4.*[1]".
The problem appeared on rev361 ("XPath parsing loop with node-set()")
which i tihnk is caused by an erroneous xsl generated-template at
trunk/buid/xsltforms.xsl:189:
<xsl:if test="//xforms:bind[not(@nodeset)]"><xexpr>4.*[1]</xexpr></xsl:if>
- Reproduced on all browsers (ie, FF, chrome)
Regards,
Kostis Anagnostopoulos
|
|
From: COUTHURES A. <ala...@ag...> - 2010-03-27 22:55:37
|
Hello,
> With rev 364, in template with name="field" (near line 885), we have :
>
> <xsl:if test="local-name() != 'trigger' and local-name() != 'submit'
> and (local-name() != 'output' or (xforms:label/node() and
> string($appearance) != 'none'))">
> <span class="focus"> <xsl:text/></span>
> </xsl:if>
>
> The presence of the invisible character   is annoying
This is due to Internet Explorer misunderstanding autoclose tags.
> in the case of a <select> or <select1> without a label element :
>
> <xf:select1 ref="type_annonce" appearance="full" incremental="true">
> <xf:itemset
> nodeset="instance('instance-types-d-annonce')/resource[@xml:lang=/requete/@xml:lang]/item">
> <xf:label ref="label"/>
> <xf:value ref="value"/>
> </xf:itemset>
> </xf:select1>
>
> It adds an empty line above the input boxes, where the label would be
> written, even though there's no label at all.
Because focus mark is now hidden by default in XSLTForms, I now wonder
if anyone is using it actually! It could be depreciated but I still
consider that it's a good practice for accessibility, isn't it ??
>
> A fix would be to use a "and" instead of the "or" in the <xsl:if>,
> like this:
>
> <xsl:if test="local-name() != 'trigger' and local-name() != 'submit'
> and (local-name() != 'output' and (xforms:label/node() and
> string($appearance) != 'none'))">
It doesn't sound as a fix for me (and I don't see why there shouldn't be
a focus mark when there is no label anyway) because it's changing the
behavior.
>
> If this seems correct, I suggest to add it to the svn.
Even so, I don't think that such a change will disturb anybody so I will
commit it!
Thanks!
-Alain
|
|
From: COUTHURES A. <ala...@ag...> - 2010-03-27 22:53:57
|
Hi, > In "xsltforms.xsl" (rev 364), there's a encoding="iso-8859-1" in the > <xsl:output> element. This was already like this before rev 364... but the xml prolog is missing! > For some reason, IE7 considers that the content is encoded in UTF-8 > and so all non-ISO characters, and some invisible UTF-8 characters, > are displayed as little squares (see attached file). Without the xml prolog, the content has to be considered à UTF-8 by the parser! Anyway, I didn't notice such funny characters myself... > > Setting the encoding attribute to "UTF-8" solves the problem. I prefer add the correct missing xml prolog. Somehow, the .xsl generation from source components is now broken and I have to save the resulting file manually. I have to be more careful before fixing this... Thanks! -Alain |
|
From: COUTHURES A. <ala...@ag...> - 2010-03-27 22:53:54
|
Hello, > I have a problem that is created due to my need to avoid a server side > error. This relates to the server declaring invalid any xml that > contains the same gml:id attribute twice. > > As a quick workaround to avoid this problem I can just globally delete > the gml:id attribute before submission, however this has the effect of > creating a namespace declaration in the submitted xml as follows: > > xmlns:pre3="" > Attribute removing has been fixed! Thanks! -Alain |
|
From: COUTHURES A. <ala...@ag...> - 2010-03-27 22:53:38
|
Chris, > I have two nested repeats and I need to get the current index of the inner repeat using the index() function. Here is an example: > > <xf:repeat id="outerRepeat" nodeset="outer"> > <xf:repeat id="innerRepeat" nodeset="inner"> > ... > </xf:repeat> > </xf:repeat> > > The index() function works well so long as there is only element in the "outer" nodeset. However, if there is more than one element in the outer nodeset, the index() function gives incorrect results. > This bug appears only with IE because of its different event management... I have fixed this but an extra HTML is still required: you have to embed the nested xf:repeat within a TBODY element. Thank you for your feedbacks! -Alain |
|
From: COUTHURES A. <ala...@ag...> - 2010-03-27 22:53:19
|
Kostis, > In a nutshell, i think it would be preferrable *not* to link schema-length > with xf:input.size or width in any way. > I agree with you, it's better to let designers manage input size with CSS. This old AJAXForms feature is removed from the SVN release. Thanks! -Alain |
|
From: COUTHURES A. <ala...@ag...> - 2010-03-27 13:19:43
|
Hi, > If i'm correct, at your last commit r367, Alain, you are fixing the > "itemset's-1st-node-not-deleted" problem i reported yesterday. > Yes, the SVN version includes an important optimization for IE about .length calculations in loop. Unfortunately, this cannot be done in every statement and some regressions, such as this one, have already been fixed. > I hope it won't be difficult to backport it to beta-2. > I haven't tested it with beta-2 since it works now with SVN... > Have you also noticed the tracker item about the use of the 'size' > attribute on 'input' elements[1] i submited 20 days ago? > Yes, it isn't already fixed because size value is expressed as a number of characters while width is expressed as a number of pixels: I have to find how to convert this in every CSS situation. It shouldn't be difficult indeed but, because it doesn't sound as a priority, help is welcome! Thanks! -Alain |
|
From: Kostis A. <ank...@gm...> - 2010-03-27 12:48:36
|
Hi,
When for some reason the generated-from-XSL javascript-initialization
code of the page fails,
(such as when the definition of the init() function fails)
no message gets displayed to the user.
I really had trouble realising why my users reported "all ok" but
"nothing worked!" on IE.
A more adequate response would be to issue an error mesage.
I would suggest the generated page-code to become something along the
lines drawn above:
<!-- the old script element -->
<script type="text/javascript">
function initImpl() { // The old init() renamed.
try {
.../* XFDefinition genrated by XSL HERE. */
} catch (e) {
...
}
<!-- A new script element -->
</script>
<script type="text/javascript">
// The new init() to be invoked by body.onLoad.
function init() {
try {
initImpl();
} catch(e) {
alert("Generated XForms-Init script crashed due to: \n"+e);
}
</script>
Regards,
Kostis Anagnostopoulos.
|
|
From: Kostis A. <ank...@gm...> - 2010-03-27 12:46:50
|
Hi, If i'm correct, at your last commit r367, Alain, you are fixing the "itemset's-1st-node-not-deleted" problem i reported yesterday. Thank you for your really responsive attitude towards bug submissions. I hope it won't be difficult to backport it to beta-2. Regards, Kostis Anagnostopoulos PS: Have you also noticed the tracker item about the use of the 'size' attribute on 'input' elements[1] i submited 20 days ago? I apologize for sending it directly to the tracker, if i had discovered this mailling list back then, i would have tried to ask about it here first, and not add "noise" on your development tools. [1] https://sourceforge.net/tracker/?func=detail&aid=2964204&group_id=242651&atid=1119926 On Thu, Mar 25, 2010 at 1:35 PM, Kostis Anagnostopoulos <ank...@gm...> wrote: > I think there is a problem with using the <xf:delete> to delete > instance-nodes bound to <xf:itemsets> of <xf:select> or <xf:select1> > controls. > (lets say to clean-up the selection-lists) > > Although the <xf;delete> properly erases the instance-document contents, > the seletion-lists are not updated corretly, > and the first item is always visible in the select controls. > > Is this indeed the expected behavior? > > - Reported against XSLTForms release: > beta-2 > - I tested and got the same behavior on browsers: > * firefox 3.5, > * chrome 4 > * ie8 > > - Also checked on Chrome revision-364 from svn and found the situation > slightly worse: > The <xf:select1> control preserves the old buggy behavior but the > <xf:select> does not remove *any* item of it selection-list items, > keeping it intact! > > > An xform that demonstrate the problems is attached, > and also included below for reference. > > Regards, > Kostis Anagnostopouos > > > <?xml version="1.0" encoding="UTF-8"?> > <?xml-stylesheet href="xsltforms/xsltforms.xsl" encoding="UTF-8" > type="text/xsl"?> > <html lang="en" xml:lang="en" 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:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation=" > http://www.w3.org/2002/xforms > http://www.w3.org/MarkUp/Forms/2007/XForms-11-Schema.xsd > http://www.w3.org/2001/xml-events > http://www.w3.org/MarkUp/SCHEMA/xml-events-attribs-1.xsd > "> > <head> > <title>Deleting selection-list Itemset contents</title> > <xf:model> > <xf:instance id="main"> > <main> > <data /> > </main> > </xf:instance> > <xf:instance id="items"> > <items> > <item>1</item> > <item>2</item> > <item>3</item> > </items> > </xf:instance> > </xf:model> > </head> > > <body> > <p>xf:itemset's bound-document conents: > <xf:repeat nodeset="instance('items')/item"> > <xf:output ref="."/> > </xf:repeat> > </p> > <xf:select1 ref="/main"> > <xf:itemset nodeset="instance('items')/item"> > <xf:label ref="." /> > <xf:value ref="." /> > </xf:itemset> > </xf:select1> > <xf:select ref="/main"> > <xf:itemset nodeset="instance('items')/item"> > <xf:label ref="." /> > <xf:value ref="." /> > </xf:itemset> > </xf:select> > <p> > When trigger clicked, should it had deleted all nodes from > select-list? > <br /> > Or it is ok for the selection-list to still contain the first-one > node?? > </p> > <xf:trigger> > <xf:label>xf:delete the contents of the xf:itemset's > bound-document</xf:label> > <xf:delete ev:event="DOMActivate" nodeset="instance('items')/*" /> > </xf:trigger> > > </body> > </html> > |
|
From: Kostis A. <ank...@gm...> - 2010-03-26 19:25:19
|
Hello, i first experimented with this promissing project when it was still named AjaxForms, and now i find it to be in a much better state. So i have started using XSLTForms's last released version, 'beta-2', to build simple applications but a i tried more compex scenarios i came across various issues: differences between browsers (ie won't even run), peculiar control behavior, minor gotcha, silent JS crashes, etc. It seems there is a development effort directed into the latest version in svn, but this is far from complete. In general, the latest revision is in a much worse state than beta-2. I searched through the support archives but did not find any answer to the following general questions: * Is it possible to get a feeling of the development roadmap? (when is the next release comming, and on what version would this next release be based upon?) * Are there any architectural changes that delay the release? * Are there any open tasks (docs, samples, test-cases, reports) to facilitate the participation of more developers in the process? I hope i'm not interveening too harsh with these questions. With appreciation to your Efforts, Kostis Anagnostopoulos |
|
From: Claudius T. <cla...@ya...> - 2010-03-26 15:44:58
|
HI, For CKEditor and TinyMCE we have now their content refreshed when the boundednode is changed. Claudius Teodorescu http://kuberam.ro |
|
From: Kostis A. <ank...@gm...> - 2010-03-25 13:36:05
|
I think there is a problem with using the <xf:delete> to delete instance-nodes bound to <xf:itemsets> of <xf:select> or <xf:select1> controls. (lets say to clean-up the selection-lists) Although the <xf;delete> properly erases the instance-document contents, the seletion-lists are not updated corretly, and the first item is always visible in the select controls. Is this indeed the expected behavior? - Reported against XSLTForms release: beta-2 - I tested and got the same behavior on browsers: * firefox 3.5, * chrome 4 * ie8 - Also checked on Chrome revision-364 from svn and found the situation slightly worse: The <xf:select1> control preserves the old buggy behavior but the <xf:select> does not remove *any* item of it selection-list items, keeping it intact! An xform that demonstrate the problems is attached, and also included below for reference. Regards, Kostis Anagnostopouos <?xml version="1.0" encoding="UTF-8"?> <?xml-stylesheet href="xsltforms/xsltforms.xsl" encoding="UTF-8" type="text/xsl"?> <html lang="en" xml:lang="en" 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:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation=" http://www.w3.org/2002/xforms http://www.w3.org/MarkUp/Forms/2007/XForms-11-Schema.xsd http://www.w3.org/2001/xml-events http://www.w3.org/MarkUp/SCHEMA/xml-events-attribs-1.xsd "> <head> <title>Deleting selection-list Itemset contents</title> <xf:model> <xf:instance id="main"> <main> <data /> </main> </xf:instance> <xf:instance id="items"> <items> <item>1</item> <item>2</item> <item>3</item> </items> </xf:instance> </xf:model> </head> <body> <p>xf:itemset's bound-document conents: <xf:repeat nodeset="instance('items')/item"> <xf:output ref="."/> </xf:repeat> </p> <xf:select1 ref="/main"> <xf:itemset nodeset="instance('items')/item"> <xf:label ref="." /> <xf:value ref="." /> </xf:itemset> </xf:select1> <xf:select ref="/main"> <xf:itemset nodeset="instance('items')/item"> <xf:label ref="." /> <xf:value ref="." /> </xf:itemset> </xf:select> <p> When trigger clicked, should it had deleted all nodes from select-list? <br /> Or it is ok for the selection-list to still contain the first-one node?? </p> <xf:trigger> <xf:label>xf:delete the contents of the xf:itemset's bound-document</xf:label> <xf:delete ev:event="DOMActivate" nodeset="instance('items')/*" /> </xf:trigger> </body> </html> |
|
From: Grégoire C. <gco...@gm...> - 2010-03-24 12:14:32
|
Hello,
With rev 364, in template with name="field" (near line 885), we have :
<xsl:if test="local-name() != 'trigger' and local-name() != 'submit' and
(local-name() != 'output' or (xforms:label/node() and string($appearance) !=
'none'))">
<span class="focus"> <xsl:text/></span>
</xsl:if>
The presence of the invisible character   is annoying in the case of a
<select> or <select1> without a label element :
<xf:select1 ref="type_annonce" appearance="full" incremental="true">
<xf:itemset
nodeset="instance('instance-types-d-annonce')/resource[@xml:lang=/requete/@xml:lang]/item">
<xf:label ref="label"/>
<xf:value ref="value"/>
</xf:itemset>
</xf:select1>
It adds an empty line above the input boxes, where the label would be
written, even though there's no label at all.
A fix would be to use a "and" instead of the "or" in the <xsl:if>, like
this:
<xsl:if test="local-name() != 'trigger' and local-name() != 'submit' and
(local-name() != 'output' and (xforms:label/node() and string($appearance)
!= 'none'))">
If this seems correct, I suggest to add it to the svn.
Grégoire
|
|
From: Peter O. <pol...@gm...> - 2010-03-24 01:54:54
|
I am trying to create an editor for an xml file that has a very specific format that has a series of <video>s, all with the same format. To do this I am using <select1> to choose which <video> to change, and then several <input>s that represent the fields within that <video>. I can't figure out how to get the <input>s to match the selected <video>. Here is the source: <?xml version="1.0" encoding="utf-8" ?> <?xml-stylesheet href="scripts/xsltforms/xsltforms.xsl" type="text/xsl" ?> <?xsltforms-options debug="yes"?> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:xf="http://www.w3.org/2002/xforms" xmlns:xs="http://www.w3.org/2001/XMLSchema"> <head> <title>Search</title> <xf:model id="control"> <xf:instance> <control xmlns=""> <current /> </control> </xf:instance> </xf:model> <xf:model id="document"> <xf:instance> <videos xmlns="http://www.example.org/videos" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.example.org/videos videos.xsd" id="videos"> <video name="Magnifica"> <description> <![CDATA[Don't be an arrogant jerk. Try Magnifica today!]]> </description> <furl>http://www.facebook.com/video/video.php?v=610610255477 </furl> <yurl>http://www.youtube.com/watch?v=X6--U2p7fnE </yurl> </video> <!-- more <video>s follow --> </videos> </xf:instance> </xf:model> </head> <body> <xf:input ref="video[2]@name" model="document"> <xf:label>name</xf:label> </xf:input> <!--other <input>s follow--> <xf:select1 model="control" ref="current"> <xf:label>Current Video:</xf:label> <xf:itemset model="document" nodeset="video"> <xf:label ref="@name" /> <xf:value ref="@name" /> </xf:itemset> </xf:select1> </body> </html> The xml that is being edited is the document <model>. According to the W3C specification, using <copy> instead of <value> inside the <itemset> and then referencing control/current should work, but I get an error (shown below). I am open to slight modifications in the formats if it will get the job done. XSLTForms Exception -------------------------- Error initializing : TypeError this.valueBinding is undefined |
|
From: Stephen C. <Ste...@ut...> - 2010-03-24 01:19:56
|
Hello, I have a problem that is created due to my need to avoid a server side error. This relates to the server declaring invalid any xml that contains the same gml:id attribute twice. As a quick workaround to avoid this problem I can just globally delete the gml:id attribute before submission, however this has the effect of creating a namespace declaration in the submitted xml as follows: xmlns:pre3="" This is also rejected by the server with the message "Prefixed namespace bindings may not be empty". The following xform is a simplified example of what I am doing. <?xml version="1.0" encoding="UTF-8"?> <?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:aatams="http://www.imos.org.au/aatams" xmlns:wfs="http://www.opengis.net/wfs" xmlns:ogc="http://www.opengis.net/ogc" xmlns:ows="http://www.opengis.net/ows" xmlns:gml="http://www.opengis.net/gml"> <head> <xf:model id="m1"> <xf:instance id="data"> <wfs:Insert> <wfs:FeatureCollection> <gml:featureMember> <aatams:device> <aatams:name>device-1</aatams:name> <aatams:device_model> <aatams:device_type gml:id="aatams.device_type.1"> <aatams:name>RECEIVER</aatams:name> </aatams:device_type> </aatams:device_model> </aatams:device> </gml:featureMember> <gml:featureMember> <aatams:device> <aatams:name>device-2</aatams:name> <aatams:device_model> <aatams:device_type gml:id="aatams.device_type.1"> <aatams:name>RECEIVER</aatams:name> </aatams:device_type> </aatams:device_model> </aatams:device> </gml:featureMember> </wfs:FeatureCollection> </wfs:Insert> </xf:instance> <xf:instance id="response"> <dummy xmlns=""/> </xf:instance> <xf:submission id="s01" ref="instance('data')" method="post" action="../../deegree-wfs/services" replace="instance" instance="response"> <xf:action ev:event="xforms-submit"> <xf:delete nodeset="instance('data')//@gml:id" /> </xf:action> <xf:message level="modeless" ev:event="xforms-submit-error">Submit error.</xf:message> </xf:submission> </xf:model> </head> <body> <xf:submit submission="s01"> <xf:label>Submit</xf:label> </xf:submit> </body> </html> The xml arriving at the server is as follows: <Transaction xmlns="http://www.opengis.net/wfs" xmlns:pre1="http://www.opengis.net/gml" xmlns:pre2="http://www.imos.org.au/aatams" xmlns:pre3="" version="1.1.0" service="WFS"> <Insert> <FeatureCollection> <pre1:featureMember> <pre2:device> <pre2:name>device-1</pre2:name> <pre2:device_model> <pre2:device_type> <pre2:name>RECEIVER</pre2:name> </pre2:device_type> </pre2:device_model> </pre2:device> </pre1:featureMember> <pre1:featureMember> <pre2:device> <pre2:name>device-2</pre2:name> <pre2:device_model> <pre2:device_type> <pre2:name>RECEIVER</pre2:name> </pre2:device_type> </pre2:device_model> </pre2:device> </pre1:featureMember> </FeatureCollection> </Insert> </Transaction> I am hoping that this is a quickly fixed, if not please advise. Thanks -- Regards Stephen Cameron Data Programmer Integrated Marine Observing System (IMOS) eMarine Information Infrastructure Project University of Tasmania, Private Bag 21, Hobart, TAS 7001, Australia Tel: +61 3 6226 8507 Fax: +61 3 6226 2997 Email: ste...@ut... URL: http://www.imos.org.au/eMII.html |
|
From: Claudius T. <cla...@ya...> - 2010-03-22 12:06:45
|
Hi, The next version of eXSLTForms is done (see eXSLTForms'>http://sourceforge.net/projects/extxsltforms/files/">eXSLTForms). It integrates EditArea (single file mode, for now), CKEditor, and TinyMCE. Enjoy! Claudius Teodorescu http://kuberam.ro |
|
From: Christopher D. <cd...@vi...> - 2010-03-20 09:56:44
|
Alain, Here is a simple example which demonstrates the behavior. Chris <?xml version="1.0" ?> <?xml-stylesheet href="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:xsd="http://www.w3.org/2001/XMLSchema"> <head> <xf:model> <!-- DATA FROM EXTERNAL SOURCES --> <xf:instance id="library"> <library> <books> <book> <title>The Way We Work</title> <authors> <author>David Macaulay</author> <author>Richard Walker</author> </authors> </book> <book> <title>The Astonishing Life of Octavian Nothing, Traitor to the Nation, Volume II: The Kingdom on the Waves</title> <authors> <author>M. T. Anderson</author> </authors> </book> <book> <title>Old Bear</title> <authors> <author>Kevin Henkes</author> </authors> </book> </books> </library> </xf:instance> </xf:model> <title>index() Test</title> <style> td { border: 1px solid #000000; } </style> </head> <body> <xf:group ref="instance('library')"> Click a book or author for its index <table> <thead> <tr> <td> <b>Title</b> </td> <td> <b>Authors</b> </td> </tr> </thead> <tbody> <xf:repeat id="books" nodeset="books/book"> <td> <xf:trigger appearance="minimal"> <xf:label> <xf:output ref="title"/> </xf:label> <xf:message ev:event="DOMActivate"> <xf:output value="concat('The current book is: ', instance('library')/books/book[index('books')]/title)"/> </xf:message> </xf:trigger> </td> <td> <table> <xf:repeat id="authors" nodeset="authors/author"> <td> <xf:trigger appearance="minimal"> <xf:label> <xf:output ref="."/> </xf:label> <xf:message ev:event="DOMActivate"> <xf:output value="concat('The current author is: ', instance('library')/books/book[index('books')]/authors/author[index('authors')])"/> </xf:message> </xf:trigger> </td> </xf:repeat> </table> </td> </xf:repeat> </tbody> </table> </xf:group> </body> </html> |
|
From: COUTHURES A. <ala...@fr...> - 2010-03-20 09:24:36
|
Christopher, Can you please post a testcase about this bug? Thanks! -Alain > I have two nested repeats and I need to get the current index of the inner repeat using the index() function. Here is an example: > > <xf:repeat id="outerRepeat" nodeset="outer"> > <xf:repeat id="innerRepeat" nodeset="inner"> > ... > </xf:repeat> > </xf:repeat> > > The index() function works well so long as there is only element in the "outer" nodeset. However, if there is more than one element in the outer nodeset, the index() function gives incorrect results. > > Chris > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > > > |
|
From: COUTHURES A. <ala...@ag...> - 2010-03-20 09:21:55
|
Christopher, Can you please post a testcase about this bug? Thanks! -Alain > I have two nested repeats and I need to get the current index of the > inner repeat using the index() function. Here is an example: > > <xf:repeat id="outerRepeat" nodeset="outer"> > <xf:repeat id="innerRepeat" nodeset="inner"> > ... > </xf:repeat> > </xf:repeat> > > The index() function works well so long as there is only element in > the "outer" nodeset. However, if there is more than one element in > the outer nodeset, the index() function gives incorrect results. > > Chris > > ------------------------------------------------------------------------------ > > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > > > |
|
From: Christopher D. <cd...@vi...> - 2010-03-20 09:08:31
|
I have two nested repeats and I need to get the current index of the inner repeat using the index() function. Here is an example:
<xf:repeat id="outerRepeat" nodeset="outer">
<xf:repeat id="innerRepeat" nodeset="inner">
...
</xf:repeat>
</xf:repeat>
The index() function works well so long as there is only element in the "outer" nodeset. However, if there is more than one element in the outer nodeset, the index() function gives incorrect results.
Chris
|
|
From: Claudius T. <cla...@ya...> - 2010-03-17 08:54:06
|
Unfortunately, AnyTime's license is "Noncommercial — You may not use this work for commercial purposes.". So, XForms developers don't have at their disposal open source software for theri commercial web apps. Claudius Teodorescu http://kuberam.ro |
|
From: Claudius T. <cla...@ya...> - 2010-03-17 08:12:28
|
Hi, I am managing eXSLTForms. I have looked over AnyTime and looks very nice. If other users of XSLTForms found AnyTime of interest, I can try to help with its integration into XSLTForms. P.S. On page http://www.ama3.com/anytime/#AnyTime.widget.placement I copied the content of "English" input control in section 4. Add JavaScript Code, modified the year to 1968, and pasted back to the input control. The result was that the date on calendar was modified accordingly. Claudius Teodorescu http://kuberam.ro |
|
From: Stephen C. <Ste...@ut...> - 2010-03-16 22:55:23
|
Hi Andrew, Thanks for this, much appreciated. I should be able to have a go with it in the next few days. Looking at what you have suggested it might be worth taking a look at the exsltforms (http://sourceforge.net/projects/extxsltforms) project on source-forge to see how their 'extensions' to XSLTForms are included (I allows you to include CKEditor for example), but jquery might be the difference. In terms of useability I think that AnyTime is an improvement over the current Calendar pop-up in XSLTforms but there is one problem in that it does not allow you to interact with the date-time input control, particularly to paste a value. For general use how you have it setup is fine but in my case where people may be copying data from another electronic document into a web-form this will not work. No doubt I can change this arrangement fairly easily in the AnyTime javascript. The way date validation is done currently in XSLTForms has problems for me, so if a short term solution is available using *AnyTime.Converter that would be good as well. * Andrew M. Andrews III wrote: > Hi Stephen, > > I saw your post about trying to use Any+Time(TM) with XSLTForms: > http://tinyurl.com/yl7oakx > > I want to let you know that I got jQuery and AnyTime.widget to work > with the XSLTForms spreadsheet.xml demo, but it required a bit of a > hack. First, I changed my library to be compatible with jQuery's > noConflict() method. You can get the new version 3.1012 here: > > http://www.ama3.com/anytime/ > > Next, I determined that you have to add the necessary JavaScript code > to the page in a very round-about way, I think because there is a > delay in how the browsers execute scripts after an XML/XSLT > transformation. Basically, the solution I found was to use a timeout > to delay and synchronize the load and execution of jquery.js, > anytime.js and a short script containing jQuery.noConflict() and > AnyTime.widget() calls. For example, if you create an <input> that > you want to manage using my library such as this: > > <input type="text" id="AnyTimeDemo" /> > > Then place the following script just before the closing </body> tag in > your XML document: > > <script type="text/javascript"> > setTimeout( > function() > { > var atwx = document.createElement("script"); > atwx.type = "text/javascript"; > atwx.src = "jquery.js"; > document.getElementsByTagName("head")[0].appendChild(atwx); > setTimeout( > function() > { > atwx = document.createElement("script"); > atwx.type = "text/javascript"; > atwx.src = "anytime.js"; > document.getElementsByTagName("head")[0].appendChild(atwx); > setTimeout( > function() > { > atwx = document.createElement("script"); > atwx.type = "text/javascript"; > var code = > 'jQuery.noConflict();AnyTime.widget("AnyTimeDemo");'; > if ( atwx.canHaveChildren ) > atwx.appendChild(document.createTextNode(code)); > else > atwx.text = code; > > document.getElementsByTagName("head")[0].appendChild(atwx); > }, 100 ); > }, 100 ); > }, 100 ); > </script> > > A few changes you'll have to make to your version: > > (1) If jquery.js and anytime.js do not reside in the current > directory, be sure to use the appropriate path in the lines that > assign atwx.src! > > (2) If your date/time field does not have the ID "AnyTimeDemo", be > sure to change it in the line that calls AnyTime.widget(). You can > also modify the code string to create additional widgets and pass > parameters to them. > > (3) You might have to increase the delays on the timeouts from 100 > miliseconds to something longer, but try not to make them longer than > necessary or it will delay how long it takes the widgets to appear. > > (4) If you want, you can of course put the calls to > jQuery.noConflict() and AnyTime.widget() into a separate script file, > and load it the same way as jquery.js and anytime.js. In fact, doing > so would probably be a Good Idea (TM). ;-) > > Please give it a try, and let me know if it does or doesn't work for > you. If you have any problems, feel free to send me the URL of your > dev/test/demo server where I can see what's going wrong, or send me > the appropriate files and I will take a look at them on my own machine. > > I look forward to hearing from you. > > Peace, > Andrew > > -- Regards Stephen Cameron Data Programmer Integrated Marine Observing System (IMOS) eMarine Information Infrastructure Project University of Tasmania, Private Bag 21, Hobart, TAS 7001, Australia Tel: +61 3 6226 8507 Fax: +61 3 6226 2997 Email: ste...@ut... URL: http://www.imos.org.au/eMII.html |
|
From: COUTHURES A. <ala...@ag...> - 2010-03-12 22:02:43
|
Brian,
>
> I encountered cross-browser problem when using XForms dialog inside a
> table with XForms repeat. This XForms dialog has another table with
> XForms repeat.
>
> In Firefox, it renders correctly -- the dialog is hidden initially and
> I can click on the "show" button to show the dialog. However, in IE,
> the supposed-to-be-hidden dialog appears and the "show" button shows
> an empty dialog.
>
>
>
> Attached please find a simplified version of my code and two
> screenshots for IE and FF.
>
>
>
> Is this a bug or something I did incorrectly?
>
It appears that Internet Explorer doesn't accept "div" at "td" level !
For this test case, I suggest this:
<table border="1">
<thead>
<tr>
<th>A</th>
<th>B</th>
</tr>
</thead>
<tbody>
<xf:repeat nodeset="test" appearance="full">
<tr>
<td>
<xf:output ref="a" />
</td>
<td>
<xf:output ref="b" />
</td>
<td style="border-style: none; padding:0">
<xf:dialog id="dialog">
<div>
<table border="1">
<thead>
<tr>
<th>A</th>
</tr>
</thead>
<tbody>
<xf:repeat nodeset="test"
appearance="full">
<tr>
<td>inner</td>
</tr>
</xf:repeat>
</tbody>
</table>
</div>
<xf:trigger>
<xf:label>hide</xf:label>
<xf:hide ev:event="DOMActivate"
dialog="dialog"/>
</xf:trigger>
</xf:dialog>
</td>
</tr>
</xf:repeat>
</tbody>
</table>
(I have explicitely added "thead" elements).
Rendering is not absolutely perfect but this is just a testcase...
Thanks!
-Alain
|
97 messages has been excluded from this view by a project administrator.
