xsltforms-support Mailing List for XSLTForms (Page 109)
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: Arnaud F. <arn...@gm...> - 2009-07-07 14:33:00
|
Hi,
I'm using your processor for 2 days and I had a headhache to change the
input field style. I don't want modify all input only some.
I put, just after <body> tag my css.
And somewhere I've something like
.testClass input.xforms-value {width: 50px !important}
It doesn't work because when page is generated all escape characters are not
present. My instruction became
.testClassinput.xforms-value {width: 50px !important}
no space between .testClass and input.xforms-values
So what can I do?
Regards
|
|
From: COUTHURES A. <ala...@ag...> - 2009-06-25 13:11:08
|
Hi Benoit,
Thank you for testing XSLTForms.
> 1) When I insert a stylesheet link <link href="http://sisal.dvp/corpus/stylesheets/sisal/sisal.css" media="screen" rel="stylesheet" type="text/css" /> in my page. I obtain, after transform by my Firefox, an empty inline style <style>{}</style>.
>
Because XSLT 1.0 is used by XSLTForms to parse CSS external file, its
content has to be an XML document. Adding a document element, such as
<css> at the beginning and </css> at the end, is enough. Hopefully
browsers are not disturbed by this if your intend is to also use the CSS
file in non-XForms situations.
This can also be done dynamically at server side, for example with URL
rewriting and a generic script for that. The test environment for
XSLTForms is based on such a mechanism and you can have a look at
http://xsltforms.svn.sourceforge.net/viewvc/xsltforms/txs/css.txs?revision=85&view=markup
> 2) So I tried to directly inline my CSS in the page with <style> markup. It's better but some CSS rules are corrupted. Ie:
> div#banner div#applications ul.tabs li { margin-left: 0px; margin-right: -6px; list-style-type: none; display: inline; }
> become
> div#bannerdiv#applicationsul.tabsli { margin-left: 0px; margin-right: -6px; list-style-type: none; display: inline; }
> I suspect a pb around the "cssconv" template. I tried to modify the line #2188 from:
> <xsl:with-param name="sels" select="translate(substring-before($input,'{'),' ','')"/>
> To
> <xsl:with-param name="sels" select="translate(substring-before($input,'{'),' ',' ')"/>
>
> And now it works better (rendering is OK, javascript not...), but since I don't really know what the "cssconv" template does I'afraid I'm breaking some thing else.
>
Yes, this is an already known bug in the beta release. You better test
with the latest work version in the SVN repository at
http://xsltforms.svn.sourceforge.net/viewvc/xsltforms/trunk/build/
> 3) And a general question : what do you think about XForms generation directly from XSD definition of documents ?
>
Some years ago, I was very disappointed by a similar approach for
relational databases based on DDL to automatically generate forms.
Today, from XML schemas, possibilities are more interesting and some
people, such as Dan McCreary, are definitely working on this. I haven't
seen yet what can be produced. The main difficulty is that usually users
need condensed interfaces. Data and presentation don't necessarily have
the same goals.
> PS: For information, I try to embbed "eXist" and "xsltForms" in an existing Ruby on Rail app (tired by SQL and ORM...)
The beta release of XSLTForms has recently been added in eXist
distribution !
Thanks!
Alain Couthures
<agenceXML>
Bordeaux, France
Twitter account: AlainCouthures
|
|
From: COUTHURES A. <ala...@ag...> - 2009-06-25 13:02:33
|
Hi Benoit,
Thank you for testing XSLTForms.
> 1) When I insert a stylesheet link <link
> href="http://sisal.dvp/corpus/stylesheets/sisal/sisal.css"
> media="screen" rel="stylesheet" type="text/css" /> in my page. I
> obtain, after transform by my Firefox, an empty inline style
> <style>{}</style>.
>
Because XSLT 1.0 is used by XSLTForms to parse CSS external file, its
content has to be an XML document. Adding a document element, such as
<css> at the beginning and </css> at the end, is enough. Hopefully
browsers are not disturbed by this if your intend is to also use the CSS
file in non-XForms situations.
This can also be done dynamically at server side, for example with URL
rewriting and a generic script for that. The test environment for
XSLTForms is based on such a mechanism and you can have a look at
http://xsltforms.svn.sourceforge.net/viewvc/xsltforms/txs/css.txs?revision=85&view=markup
> 2) So I tried to directly inline my CSS in the page with <style>
> markup. It's better but some CSS rules are corrupted. Ie:
> div#banner div#applications ul.tabs li { margin-left: 0px;
> margin-right: -6px; list-style-type: none; display: inline; }
> become
> div#bannerdiv#applicationsul.tabsli { margin-left: 0px;
> margin-right: -6px; list-style-type: none; display: inline; }
> I suspect a pb around the "cssconv" template. I tried to modify the
> line #2188 from:
> <xsl:with-param name="sels"
> select="translate(substring-before($input,'{'),' ','')"/>
> To
> <xsl:with-param name="sels"
> select="translate(substring-before($input,'{'),' ',' ')"/>
>
> And now it works better (rendering is OK, javascript not...), but
> since I don't really know what the "cssconv" template does I'afraid
> I'm breaking some thing else.
>
Yes, this is an already known bug in the beta release. You better test
with the latest work version in the SVN repository at
http://xsltforms.svn.sourceforge.net/viewvc/xsltforms/trunk/build/
> 3) And a general question : what do you think about XForms generation
> directly from XSD definition of documents ?
>
Some years ago, I was very disappointed by a similar approach for
relational databases based on DDL to automatically generate forms.
Today, from XML schemas, possibilities are more interesting and some
people, such as Dan McCreary, are definitely working on this. I haven't
seen yet what can be produced. The main difficulty is that usually users
need condensed interfaces. Data and presentation don't necessarily have
the same goals.
> PS: For information, I try to embbed "eXist" and "xsltForms" in an
> existing Ruby on Rail app (tired by SQL and ORM...)
The beta release of XSLTForms has recently been added in eXist
distribution !
Thanks!
Alain Couthures
<agenceXML>
Bordeaux, France
Twitter account: AlainCouthures
|
|
From: <ben...@en...> - 2009-06-25 08:59:32
|
Hi,
I've tried xsltForms and I had some problems with my own CSS :
My CSS is generated by haml/sass (from the ruby world) and looks like this:
/* balises générales */
html, body { height: 100%; overflow: hidden; margin: 0ex; padding: 0ex; background: #ffffff; }
body { max-height: 100%; }
body.dialog { overflow: visible; }
p, ul, input, select, body { font-family: 'Trebuchet MS', Geneva, Verdana, Arial, Helvetica, 'Century Gothic', sans-serif; font-size: 10pt; color: #000000; }
textarea, input { font-family: 'Bitstream Vera Sans Mono','Courier',monospace; font-size: 9.5pt; color: #000000; }
/* banner */
div#banner { display: block; height: 18px; position: absolute; top: 80px; width: 100%; z-index: 9; right: 18px; padding: 2px 0px; background: #ebf0f6; border-top: 1px solid #b0c4de; border-bottom: 1px solid #b0c4de; }
div#banner div#applications ul.tabs { margin: 0px; padding: 0px; border: 0px; }
div#banner div#applications ul.tabs li { margin-left: 0px; margin-right: -6px; list-style-type: none; display: inline; }
...
1) When I insert a stylesheet link <link href="http://sisal.dvp/corpus/stylesheets/sisal/sisal.css" media="screen" rel="stylesheet" type="text/css" /> in my page. I obtain, after transform by my Firefox, an empty inline style <style>{}</style>.
2) So I tried to directly inline my CSS in the page with <style> markup. It's better but some CSS rules are corrupted. Ie:
div#banner div#applications ul.tabs li { margin-left: 0px; margin-right: -6px; list-style-type: none; display: inline; }
become
div#bannerdiv#applicationsul.tabsli { margin-left: 0px; margin-right: -6px; list-style-type: none; display: inline; }
I suspect a pb around the "cssconv" template. I tried to modify the line #2188 from:
<xsl:with-param name="sels" select="translate(substring-before($input,'{'),' ','')"/>
To
<xsl:with-param name="sels" select="translate(substring-before($input,'{'),' ',' ')"/>
And now it works better (rendering is OK, javascript not...), but since I don't really know what the "cssconv" template does I'afraid I'm breaking some thing else.
3) And a general question : what do you think about XForms generation directly from XSD definition of documents ?
Thank's for your job
Benoit VINCENT
PS: For information, I try to embbed "eXist" and "xsltForms" in an existing Ruby on Rail app (tired by SQL and ORM...) .
|
|
From: COUTHURES A. <ala...@ag...> - 2009-06-18 07:25:41
|
Morgan, repeat-* attribute usage is not yet supported in XSLTForms because it wasn't in AJAXForms. I haven't already study how to implement them. It shouldn't be very difficult but it has not been a priority yet because it sounds like just an alternative with elements usage. Do you effectively require them ? Have you already many forms based on this usage ? Are you in a hurry about this support ? Thank you for your interest in XSLTForms, -Alain |
|
From: <mcu...@co...> - 2009-06-18 02:29:31
|
Does XSLTforms support the repeat-nodeset attribute? Thank you, Morgan |
|
From: Dominique R. <dom...@or...> - 2009-06-17 08:29:11
|
I just have read your trick proposal. Unfortunately any other solution leads to same problem : security, overloading, server dependencies Better to detect unecessary intermediate uploading Dominique _____ De : COUTHURES Alain [mailto:ala...@ag...] Envoyé : vendredi 15 mai 2009 11:20 À : xsl...@li... Objet : Re: [Xsltforms-support] XForms Upload with AJAX Hello, What would you think about this bad trick for xforms:upload support in XSLTForms : 1. as soon as it is selected or just before submission, the corresponding file is uploaded to the server, alone, in background 2. the server creates a temporary file for it and returns the corresponding URI (security problems to consider...) 3. this URI is stored in the instance and normal processing can continue For example, the URI could then used to be rendered as an image with an xforms:output. For a base64 storage in the instance, the server should return the contents instead. Yes, the file contents would be sent 3 times instead of just one time. Would this be a big problem ? BTW, inline images are not supported in IE7 but in IE8 (workarounds seem to exist for IE7...). Anyway, a sort of generic echo program would be required on the server... Thank you for your comments, -Alain |
|
From: COUTHURES A. <ala...@ag...> - 2009-06-17 05:55:41
|
Hi Micah, Here is an example of Javascript Trigger Activation : <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" > <head> <title>Javascript Trigger Activation Example</title> <xf:model/> </head> <body onload="$('console').style.display = 'block';"> <xf:trigger> <xf:label>Button 1</xf:label> <xf:message level="modal" ev:event="DOMActivate">Hello from Button 1</xf:message> <xf:load ev:event="DOMActivate" resource="javascript:$('button2').xfElement.click()"/> </xf:trigger> <xf:trigger id="button2"> <xf:label>Button 2</xf:label> <xf:message level="modal" ev:event="DOMActivate">Hello from Button 2</xf:message> </xf:trigger> </body> </html> I have tested it with the committed work version in the SVN repository. I'm not sure it would also work with the beta version for many reasons... Hope it helps. -Alain |
|
From: Micah D. <Mic...@ma...> - 2009-06-17 05:15:28
|
Alain and friends, Within the JavaScript of an app, I need to activate a <trigger> of a certain id, exactly as if someone had clicked a button. Is there an easy way to do this? -m |
|
From: COUTHURES A. <ala...@ag...> - 2009-06-08 06:49:54
|
Hi Robert, > Opera not handling the document function, but really, who cares? Opera is not handling the document() function correctly but it exists. For XSLTForms (http://www.agencexml.com/xsltforms), my client-side XForms implementation, external schemas are parsed using the document() function. Opera succeeds in loading the external file but there is a confusion at the attribute level : when the namespace definition (let's say xmlns:xs) is written before the @targetNamespace, the @targetNamespace is unseen while xmlns:xs is presented as an attribute (when the namespace definition is moved to last position, it works...) ! Best regards, Alain Couthures <agenceXML> Bordeaux, France |
|
From: COUTHURES A. <ala...@ag...> - 2009-05-15 09:21:41
|
Hello,
What would you think about this bad trick for xforms:upload support in
XSLTForms :
1. as soon as it is selected or just before submission, the
corresponding file is uploaded to the server, alone, in background
2. the server creates a temporary file for it and returns the
corresponding URI (security problems to consider...)
3. this URI is stored in the instance and normal processing can continue
For example, the URI could then used to be rendered as an image with an
xforms:output.
For a base64 storage in the instance, the server should return the
contents instead. Yes, the file contents would be sent 3 times instead
of just one time. Would this be a big problem ? BTW, inline images are
not supported in IE7 but in IE8 (workarounds seem to exist for IE7...).
Anyway, a sort of generic echo program would be required on the server...
Thank you for your comments,
-Alain
|
|
From: COUTHURES A. <ala...@ag...> - 2009-05-15 08:54:09
|
Hello All, People blame XForms for not providing a sexy rendering (fading,...). What do you think about a mechanism based on CSS extensions (I know, CSS is not with an XML notation...) to be interpreted by the XSLT stylesheet of XSLTForms to generated corresponding instructions ? Thank you for your answers, -Alain |
|
From: COUTHURES A. <ala...@ag...> - 2009-05-07 16:10:17
|
Hello, XSLTForms considers there is no label when the "xforms:label" element is not a child of the control element. Actually, I have already seen forms written by developers for the Mozilla extension where (X)HTML elements are in between : then, the "xforms:label" element is a descendant but not a child ! Those (X)HTML elements should, in fact, be within the "xforms:label", shouldn't they ? Thank you for your comments, -Alain |
|
From: COUTHURES A. <ala...@ag...> - 2009-05-06 07:50:11
|
Hi Micah, > While the XSLT portion of XSLTForms is executing on the client, it > displays a blank white page for a fraction of a second. This can be > jarring when transitioning between pages. > About this problem, I have tested with different browsers and, for simple forms, it might be due to just a cache problem. IE seems to be the slowest to load the stylesheet when it isn't already in its cache (when the stylesheet is dynamically composed from components no date/time is associated and it is always reloaded). I will soon update the SVN repository so it will be easy for anybody to compare loading behavior from the "src" and the "build" folders. > Does anyone have any advice or experience in eliminating the flash or > at least making it less noticeable? > No, sorry about that. With the frame extension, there wouldn't be any flash because the transformation would be performed from Javascript. Thanks! -Alain |
|
From: Micah D. <mic...@ma...> - 2009-05-05 22:31:38
|
Hi All, While the XSLT portion of XSLTForms is executing on the client, it displays a blank white page for a fraction of a second. This can be jarring when transitioning between pages. Does anyone have any advice or experience in eliminating the flash or at least making it less noticeable? Thanks, -m |
|
From: COUTHURES A. <ala...@ag...> - 2009-05-05 12:02:15
|
Hello, XForms Upload seems impossible to be fully implemented with AJAX... File upload with AJAX is usually performed with a frame or iframe element and the submission appears to be limited to POST method. XForms Upload is able to integrate binary contents within an instance to be sent with any kind of submission. Ubiquity XForms doesn't integrate Upload support yet. EMC Test Suite Report says that the corresponding tests (those tests don't include submission...) are OK for them but it's impossible to verify this ! I'm now thinking of a POST-only submission with a field containing the instance but with links to other fields in the same submission so the server can automatically build the desired instance with the binary part inside before calling processing treatments. Any suggestions ? What do you think about this ? -Alain |
|
From: COUTHURES A. <ala...@ag...> - 2009-04-29 08:57:14
|
The support list for XSLTForms is now created ! Alain Couthures <agenceXML> http://www.agencexml.com Bordeaux, France |
97 messages has been excluded from this view by a project administrator.
