xsltforms-support — XSLTForms support list

Re: [Xsltforms-support] Problem with exsltforms

[Claudius T. <cla...@ya...>]

You are totally right about referencing the first instance even without @id.


The problem is that eXSLTforms needs a own model and instance; due to the structure of xsltforms.xsl file, they are integrated by XSLTForms before any user data instance, which is not convenient.

The solution is in Alain Couthures' hand, and consists of refining reference to $config/extensions/*.


Claudius Teodorescu
http://kuberam.ro



      

Re: [Xsltforms-support] No response on the CKEditor forums to question on encoding

[Rob K. <ro...@ko...>]

Are you talking about character encoding or escaping XML/XHTML so it can go
into a textarea?

If encoding, put a content type meta in your head.

If escaping, you can GET from the server and use javascript to escape the
XML, and then place in a textarea. Then on save, get the value of the
textarea and unescape it to PUT or POST.

best,
-Rob



On Fri, Mar 5, 2010 at 6:51 AM, Dan McCreary <dan...@gm...> wrote:

> I posted the question about how to NOT encode XML on post on the CKEditor
> forum yesterday:
>
> http://cksource.com/forums/viewtopic.php?f=11&t=17900
>
> But I have not got any feedback.
>
> Since we can always just do a server-side parse using util:parse() this is
> not a problem for eXist.  But I wanted to see who was watching the forums.
>
> I have tried to classify all the major configuration options of a CKEditor
> into around a dozen classes:
>
> Category Description   Coding These options control how editor encodes
> various items.  Configuration These options control how editor is
> configured and the locations that this configuration information is loaded.
> Initialization These options control how editor is first presented to the
> user.  Import Text These options control initial text is imported.
> Keyboard These options control how characters typed on the keyboard are
> managed.  Language These options control the language used or
> language-related options.  Output These options control how data is output
> when the text is saved.  Dialog These options control the behavior within
> specific dialog panels.  Runtime These options control the non-style
> related user experience while the editor is running.  Style These options
> control the presentation aspects of this extension. Options are
> traditionally done through a CSS file.  Text Coding These options control
> how internal elements in the text are represented or coded as the user
> interacts with the editor.
> It might be nice to create a multi-tab XForms application to edit the most
> common configuration options.
>
> Note that most of the configuration options are style-related.  My next
> step is to find out what options are the most important for our users.
>
> - Dan
>
> --
> Dan McCreary
> Semantic Solutions Architect
> syntactica.com
> 952-460-1674
>
>
>
> ------------------------------------------------------------------------------
> Download Intel&#174; 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
>
>

[Xsltforms-support] No response on the CKEditor forums to question on encoding

[Dan M. <dan...@gm...>]

I posted the question about how to NOT encode XML on post on the CKEditor
forum yesterday:

http://cksource.com/forums/viewtopic.php?f=11&t=17900

But I have not got any feedback.

Since we can always just do a server-side parse using util:parse() this is
not a problem for eXist.  But I wanted to see who was watching the forums.

I have tried to classify all the major configuration options of a CKEditor
into around a dozen classes:

Category Description   Coding These options control how editor encodes
various items.  Configuration These options control how editor is configured
and the locations that this configuration information is loaded.
Initialization These options control how editor is first presented to the
user.  Import Text These options control initial text is imported.
Keyboard These
options control how characters typed on the keyboard are managed.
Language These
options control the language used or language-related options.  Output These
options control how data is output when the text is saved.  Dialog These
options control the behavior within specific dialog panels.  Runtime These
options control the non-style related user experience while the editor is
running.  Style These options control the presentation aspects of this
extension. Options are traditionally done through a CSS file.  Text
Coding These
options control how internal elements in the text are represented or coded
as the user interacts with the editor.
It might be nice to create a multi-tab XForms application to edit the most
common configuration options.

Note that most of the configuration options are style-related.  My next step
is to find out what options are the most important for our users.

- Dan

-- 
Dan McCreary
Semantic Solutions Architect
syntactica.com
952-460-1674

Re: [Xsltforms-support] Problem with exsltforms

[COUTHURES A. <ala...@ag...>]

Javier Díaz a écrit :
> Claudius Teodorescu escribió:
>> As far as I can see, there is one group with 
>> ref="/ACT_INTERCONEXION_IP/TRAZADO/PPAI_IP".
>>
>> But this XPath is valid both for first instance (which is missing 
>> @id) and the second one. Which one are you referring to?
> I thought that when instance is missing always is referring to the 
> first one... Is this wrong? I haven't any problem with this until now...
I confirm there shouldn't be a problem with that. Does it happen also 
without exsltforms ??
>>  
>> If first instance would be implied and it would have @id='i0', the 
>> group should be
>> xf:group ref="instance('i0')/TRAZADO/PPAI_IP"
> I have assigned to the fist instance the id "i0" and changed in the 
> whole document /ACT_INTERCONEXION_IP/ to instance('i0')/ and it works 
> ok, but I find strange that it fails only in this case....
It's a simple workaround but I have to know if there is a bug in XSLTForms.

Thanks!

-Alain

Re: [Xsltforms-support] Problem with exsltforms

[Claudius T. <cla...@ya...>]

As far as I can see, there is one group with ref="/ACT_INTERCONEXION_IP/TRAZADO/PPAI_IP".

But this XPath is valid both for first instance (which is missing @id) and the second one. Which one are you referring to?

 
If first instance would be implied and it would have @id='i0', the group should be
xf:group ref="instance('i0')/TRAZADO/PPAI_IP"


Claudius Teodorescu
http://kuberam.ro


      

Re: [Xsltforms-support] Problem with exsltforms

[Claudius T. <cla...@ya...>]

I have tested the Data Instance Viewer with larger instances and worked fine.

Which elements are not shown?


Claudius Teodorescu
http://kuberam.ro



      

Re: [Xsltforms-support] Is there any way to put markup in atextarea in XSLTForms

[Claudius T. <cla...@ya...>]

 Claudius Teodorescu
http://kuberam.ro



----- Forwarded Message ----
From: Claudius Teodorescu <cla...@ya...>
To: "Klotz, Leigh" <Lei...@xe...>
Sent: Fri, March 5, 2010 3:24:11 AM
Subject: Re: [Xsltforms-support] Is there any way to put markup in atextarea in XSLTForms


This syntax I like:


  <xf:textarea ref="description" appearance="ext:ckedit">
    <xf:label>Description 
:</xf:label>
    <xf:extension><ext:ckeditOptions 
toolbar="full" spellcheck="true" /></xf:extension>
  </xf:textarea>


It is very intuitive and leave space for other editors. Thanks for these samples!


 Claudius Teodorescu
http://kuberam.ro




________________________________
From: "Klotz, Leigh" <Lei...@xe...>
To: Claudius Teodorescu <cla...@ya...>
Sent: Fri, March 5, 2010 2:57:29 AM
Subject: RE: [Xsltforms-support] Is there any way to put markup in atextarea in XSLTForms


Most xforms implementations already do this; xsltforms is 
new.
 
I think Dan is on the right track.
 
As Alain said, and I noted as well, xsltforms doesn't play 
well with other JavaScript packages.  If that isn't fixed, nothing will 
work.
 
Once that's fixed, there are many ways to include ckeditor or 
tinymce or some other package: xsltforms plug ins, separate javascript script 
src file, etc.
 
But a single syntax for declaring the textarea as rich text 
should work with all of the cases.
 
Leigh.


________________________________
 From: Claudius Teodorescu 
[mailto:cla...@ya...] 
Sent: Thursday, March 04, 2010 4:43 
PM
To: Klotz, Leigh
Subject: Re: [Xsltforms-support] Is 
there any way to put markup in atextarea in XSLTForms


Very 
nice approaches, this is the way. I didn't know about them.

The problem 
is, now: what shall we do, as there is a need for such editor?

 Claudius Teodorescu
http://kuberam.ro


      

Re: [Xsltforms-support] Is there any way to put markup in atextarea in XSLTForms

[Dan M. <dan...@gm...>]

I have stated to put together a database of the current options for an
XForms Rich Text Editor extension to XSLTForms based on based on the
CKEditor.

You can see a report of this here:

http://demo.syntactica.com/exist/rest/db/syntactica/apps/rich-text-editor/views/list-items.xq

There are about about 114 options not including the edit controls.

We will be working with our customers to prioritize these but I think to get
started just the basics will be OK.

- Dan

On Thu, Mar 4, 2010 at 6:33 PM, Claudius Teodorescu <cla...@ya...>wrote:

> Yes, you are right that is no need for a new form control, if one consider
> just editing some XML/HTML as text.
>
> But, like I said, for certain web applications, there is a need for a full
> and complex rich text editor. I can only think that such extension element
> could have an attribute or child element specifying a certain configuration
> option, for instance: "full" or "basic" toolbar, UI language for
> editor/spell checking,etc.
>
> The only drawback here could be that such new form control would rely on
> CKEditor, leaving aside other editors
>
>
> Claudius Teodorescu
> http://kuberam.ro
>
>
> ------------------------------
> *From:* "Klotz, Leigh" <Lei...@xe...>
> *To:* Claudius Teodorescu <cla...@ya...>;
> xsl...@li...
> *Sent:* Fri, March 5, 2010 2:04:15 AM
> *Subject:* RE: [Xsltforms-support] Is there any way to put markup in
> atextarea in XSLTForms
>
> I don't think you need a new form control.  mediatype or appearance
> attributes on textarea is good enough, and interoperable.  Chiba uses
> mediatype, for example, and even processors without rich text support will
> allow editing of escaped html as text.
>
> Leigh.
>
>  ------------------------------
> *From:* Claudius Teodorescu [mailto:cla...@ya...]
> *Sent:* Thursday, March 04, 2010 1:31 PM
> *To:* xsl...@li...
> *Subject:* Re: [Xsltforms-support] Is there any way to put markup in
> atextarea in XSLTForms
>
>  Hi,
>
> I also thought about an extension element for XSLTForms, called
> "richTextarea" (maybe), which would allow all sort of rich text editing (I
> thought about editing the files stored within eXist, and for translations (a
> web app to manage translations)).
>
> I looked over web editors, found CKEditor and liked it very much, as being
> enough complex and flexible to be a professional extension element for
> XForms.
>
> Such extension element called richTextarea should be bound to a node, just
> like textarea element.
>
> My two cents.
>
> Claudius Teodorescu
> http://kuberam.ro
>
>
>
>
> ------------------------------------------------------------------------------
> 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
>
>


-- 
Dan McCreary
Semantic Solutions Architect
syntactica.com
952-460-1674
VOIP: 111@69.199.167.229

Re: [Xsltforms-support] Is there any way to put markup in atextarea in XSLTForms

[Kurt C. <kur...@gm...>]

It may also be worth setting up a community effort to encode an XSLTForms
rich text editor around the textarea and input component. I've done RTEs
before - they're not that hard to pull off in general, but they also require
giving up on jQuery and related libs, and you have to test them EXTENSIVELY
against different platforms.

This brings up a broader issue - one that I think Alain is probably in the
best position to answer. Itt might be very useful if we were to set up an
XSLTForms community group (possibly on GoogleCode or GIT) that would let us
post community components and extensions to XSLTForms (and quite possibly to
Ubiquity and Orbeon). I know this has been floated before, but the major
challenge is freeing up Alain to concentrate on core improvements while
others can post both extensions and cool XForms widgets (and techniques). My
model is the Drupal community, but I'm not wedded to it.

Kurt Cagle
Managing Editor
http://xmlToday.org


On Thu, Mar 4, 2010 at 4:37 PM, Klotz, Leigh <Lei...@xe...> wrote:

>  Here's what I've succesfully used to express rich text edit in XForms in
> the past:
>
>   <xf:textarea ref="description" mediatype="text/html">
>
> You can also use this
>   <xf:textarea ref="description" appearance="ext:ckedit" />
>
> You can also use this:
>   <xf:textarea ref="description" appearance="ext:ckedit"
> class="ckedit-full-toolbar" />
>
> All of these are interoperable.
>
> If you need even more, you can use the xf:extension element and put any
> content you want:
>
>   <xf:textarea ref="description" mediatype="text/html">
>     <xf:label>Description :</xf:label>
>     <xf:extension><ext:ckeditOptions toolbar="full" spellcheck="true"
> /></xf:extension>
>   </xf:textarea>
>
>
> XForms offers abstract form controls which are then specialized by
> bindings, datatypes, appearance, and styling.
>
> Leigh.
>
>  ------------------------------
> *From:* Claudius Teodorescu [mailto:cla...@ya...]
> *Sent:* Thursday, March 04, 2010 4:34 PM
> *To:* Klotz, Leigh; support xsltforms
>
> *Subject:* Re: [Xsltforms-support] Is there any way to put markup in
> atextarea in XSLTForms
>
>  Yes, you are right that is no need for a new form control, if one
> consider just editing some XML/HTML as text.
>
> But, like I said, for certain web applications, there is a need for a full
> and complex rich text editor. I can only think that such extension element
> could have an attribute or child element specifying a certain configuration
> option, for instance: "full" or "basic" toolbar, UI language for
> editor/spell checking,etc.
>
> The only drawback here could be that such new form control would rely on
> CKEditor, leaving aside other editors
>
> Claudius Teodorescu
> http://kuberam.ro
>
>
>  ------------------------------
> *From:* "Klotz, Leigh" <Lei...@xe...>
> *To:* Claudius Teodorescu <cla...@ya...>;
> xsl...@li...
> *Sent:* Fri, March 5, 2010 2:04:15 AM
> *Subject:* RE: [Xsltforms-support] Is there any way to put markup in
> atextarea in XSLTForms
>
> I don't think you need a new form control.  mediatype or appearance
> attributes on textarea is good enough, and interoperable.  Chiba uses
> mediatype, for example, and even processors without rich text support will
> allow editing of escaped html as text.
>
> Leigh.
>
>  ------------------------------
> *From:* Claudius Teodorescu [mailto:cla...@ya...]
> *Sent:* Thursday, March 04, 2010 1:31 PM
> *To:* xsl...@li...
> *Subject:* Re: [Xsltforms-support] Is there any way to put markup in
> atextarea in XSLTForms
>
>  Hi,
>
> I also thought about an extension element for XSLTForms, called
> "richTextarea" (maybe), which would allow all sort of rich text editing (I
> thought about editing the files stored within eXist, and for translations (a
> web app to manage translations)).
>
> I looked over web editors, found CKEditor and liked it very much, as being
> enough complex and flexible to be a professional extension element for
> XForms.
>
> Such extension element called richTextarea should be bound to a node, just
> like textarea element.
>
> My two cents.
>
> Claudius Teodorescu
> http://kuberam.ro
>
>
>
>
> ------------------------------------------------------------------------------
> Download Intel&#174; 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
>
>

Re: [Xsltforms-support] Is there any way to put markup in atextarea in XSLTForms

[Klotz, L. <Lei...@xe...>]

Here's what I've succesfully used to express rich text edit in XForms in the past:
 
  <xf:textarea ref="description" mediatype="text/html">
 
You can also use this
  <xf:textarea ref="description" appearance="ext:ckedit" />
 
You can also use this:
  <xf:textarea ref="description" appearance="ext:ckedit" class="ckedit-full-toolbar" />
 
All of these are interoperable.
 
If you need even more, you can use the xf:extension element and put any content you want:
 
  <xf:textarea ref="description" mediatype="text/html">
    <xf:label>Description :</xf:label>
    <xf:extension><ext:ckeditOptions toolbar="full" spellcheck="true" /></xf:extension>
  </xf:textarea>
 
 
XForms offers abstract form controls which are then specialized by bindings, datatypes, appearance, and styling.
 
Leigh.

________________________________

From: Claudius Teodorescu [mailto:cla...@ya...] 
Sent: Thursday, March 04, 2010 4:34 PM
To: Klotz, Leigh; support xsltforms
Subject: Re: [Xsltforms-support] Is there any way to put markup in atextarea in XSLTForms


Yes, you are right that is no need for a new form control, if one consider just editing some XML/HTML as text.

But, like I said, for certain web applications, there is a need for a full and complex rich text editor. I can only think that such extension element could have an attribute or child element specifying a certain configuration option, for instance: "full" or "basic" toolbar, UI language for editor/spell checking,etc.

The only drawback here could be that such new form control would rely on CKEditor, leaving aside other editors

 
Claudius Teodorescu
http://kuberam.ro 


________________________________

From: "Klotz, Leigh" <Lei...@xe...>
To: Claudius Teodorescu <cla...@ya...>; xsl...@li...
Sent: Fri, March 5, 2010 2:04:15 AM
Subject: RE: [Xsltforms-support] Is there any way to put markup in atextarea in XSLTForms


I don't think you need a new form control.  mediatype or appearance attributes on textarea is good enough, and interoperable.  Chiba uses mediatype, for example, and even processors without rich text support will allow editing of escaped html as text.
 
Leigh.

________________________________

From: Claudius Teodorescu [mailto:cla...@ya...] 
Sent: Thursday, March 04, 2010 1:31 PM
To: xsl...@li...
Subject: Re: [Xsltforms-support] Is there any way to put markup in atextarea in XSLTForms


Hi,

I also thought about an extension element for XSLTForms, called "richTextarea" (maybe), which would allow all sort of rich text editing (I thought about editing the files stored within eXist, and for translations (a web app to manage translations)).

I looked over web editors, found CKEditor and liked it very much, as being enough complex and flexible to be a professional extension element for XForms.

Such extension element called richTextarea should be bound to a node, just like textarea element.

My two cents.

 
Claudius Teodorescu
http://kuberam.ro

Re: [Xsltforms-support] Is there any way to put markup in atextarea in XSLTForms

[Claudius T. <cla...@ya...>]

Yes, you are right that is no need for a new form control, if one consider just editing some XML/HTML as text.

But, like I said, for certain web applications, there is a need for a full and complex rich text editor. I can only think that such extension element could have an attribute or child element specifying a certain configuration option, for instance: "full" or "basic" toolbar, UI language for editor/spell checking,etc.

The only drawback here could be that such new form control would rely on CKEditor, leaving aside other editors

 Claudius Teodorescu
http://kuberam.ro




________________________________
From: "Klotz, Leigh" <Lei...@xe...>
To: Claudius Teodorescu <cla...@ya...>; xsl...@li...
Sent: Fri, March 5, 2010 2:04:15 AM
Subject: RE: [Xsltforms-support] Is there any way to put markup in atextarea in XSLTForms


I don't think you need a new form control.  mediatype or 
appearance attributes on textarea is good enough, and interoperable.  Chiba 
uses mediatype, for example, and even processors without rich text support will 
allow editing of escaped html as text.
 
Leigh.


________________________________
 From: Claudius Teodorescu 
[mailto:cla...@ya...] 
Sent: Thursday, March 04, 2010 1:31 
PM
To: xsl...@li...
Subject: Re: 
[Xsltforms-support] Is there any way to put markup in atextarea in 
XSLTForms


Hi,

I 
also thought about an extension element for XSLTForms, called "richTextarea" 
(maybe), which would allow all sort of rich text editing (I thought about 
editing the files stored within eXist, and for translations (a web app to manage 
translations)).

I looked over web editors, found CKEditor and liked it 
very much, as being enough complex and flexible to be a professional extension 
element for XForms.

Such extension element called richTextarea should be 
bound to a node, just like textarea element.

My two cents.

 Claudius Teodorescu
http://kuberam.ro



      

Re: [Xsltforms-support] Is there any way to put markup in atextarea in XSLTForms

[Dan M. <dan...@gm...>]

I just found out that there are several other people that are already using
the CKEditor to manage TEI content.

We would like to demonstrate a simple FAQ editor that combines XSLTForms and
CKEditor to several potential customers.

Here is what the CKEdit tool will look like running on eXist:

http://demo.syntactica.com/exist/rest/db/test/ckeditor/_samples/faq-edit.html

On Thu, Mar 4, 2010 at 6:04 PM, Klotz, Leigh <Lei...@xe...> wrote:

>  I don't think you need a new form control.  mediatype or appearance
> attributes on textarea is good enough, and interoperable.  Chiba uses
> mediatype, for example, and even processors without rich text support will
> allow editing of escaped html as text.
>
> Leigh.
>
>  ------------------------------
> *From:* Claudius Teodorescu [mailto:cla...@ya...]
> *Sent:* Thursday, March 04, 2010 1:31 PM
> *To:* xsl...@li...
>
> *Subject:* Re: [Xsltforms-support] Is there any way to put markup in
> atextarea in XSLTForms
>
>  Hi,
>
> I also thought about an extension element for XSLTForms, called
> "richTextarea" (maybe), which would allow all sort of rich text editing (I
> thought about editing the files stored within eXist, and for translations (a
> web app to manage translations)).
>
> I looked over web editors, found CKEditor and liked it very much, as being
> enough complex and flexible to be a professional extension element for
> XForms.
>
> Such extension element called richTextarea should be bound to a node, just
> like textarea element.
>
> My two cents.
>
> Claudius Teodorescu
> http://kuberam.ro
>
>
>
> ------------------------------------------------------------------------------
> Download Intel&#174; 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
>
>


-- 
Dan McCreary
Semantic Solutions Architect
syntactica.com
952-460-1674
VOIP: 111@69.199.167.229

Re: [Xsltforms-support] Is there any way to put markup in atextarea in XSLTForms

[Klotz, L. <Lei...@xe...>]

I don't think you need a new form control.  mediatype or appearance attributes on textarea is good enough, and interoperable.  Chiba uses mediatype, for example, and even processors without rich text support will allow editing of escaped html as text.
 
Leigh.

________________________________

From: Claudius Teodorescu [mailto:cla...@ya...] 
Sent: Thursday, March 04, 2010 1:31 PM
To: xsl...@li...
Subject: Re: [Xsltforms-support] Is there any way to put markup in atextarea in XSLTForms


Hi,

I also thought about an extension element for XSLTForms, called "richTextarea" (maybe), which would allow all sort of rich text editing (I thought about editing the files stored within eXist, and for translations (a web app to manage translations)).

I looked over web editors, found CKEditor and liked it very much, as being enough complex and flexible to be a professional extension element for XForms.

Such extension element called richTextarea should be bound to a node, just like textarea element.

My two cents.

 
Claudius Teodorescu
http://kuberam.ro

Re: [Xsltforms-support] Is there any way to put markup in a textarea in XSLTForms

[Rob K. <ro...@ko...>]

The XHTML is being escaped so that CKEditor can edit it, I think. In other
words, it won't work unless the XHTML is escaped. But, have you tried
wrapping it in CDATA?

-Rob



On Thu, Mar 4, 2010 at 2:27 PM, Dan McCreary <dan...@gm...> wrote:

> Hello Claudius,
>
> I installed CKEditor on eXist and wrote up the following notes here:
>
> http://en.wikibooks.org/wiki/XForms/CKEditor
>
> I can now see the XHTML in the HTTP Post but I can not seem to get it to
> stop encoding the XML tags.
>
> I put a copy of this form on our demo server here:
>
>
> http://demo.syntactica.com/exist/rest/db/test/ckeditor/_samples/replacebyclass.html
>
> If you can figure out how to get the config.js file to stop encodeing let
> me know!  CKEditor does not have very good documentation yet :-(
>
> - Dan
>
> On Thu, Mar 4, 2010 at 3:31 PM, Claudius Teodorescu <cla...@ya...>wrote:
>
>> Hi,
>>
>> I also thought about an extension element for XSLTForms, called
>> "richTextarea" (maybe), which would allow all sort of rich text editing (I
>> thought about editing the files stored within eXist, and for translations (a
>> web app to manage translations)).
>>
>> I looked over web editors, found CKEditor and liked it very much, as being
>> enough complex and flexible to be a professional extension element for
>> XForms.
>>
>> Such extension element called richTextarea should be bound to a node, just
>> like textarea element.
>>
>> My two cents.
>>
>> Claudius Teodorescu
>> http://kuberam.ro
>>
>>
>>
>> ------------------------------------------------------------------------------
>> 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
>>
>>
>
>
> --
> Dan McCreary
> Semantic Solutions Architect
> syntactica.com
> 952-460-1674
> VOIP: 111@69.199.167.229
>
>
> ------------------------------------------------------------------------------
> Download Intel&#174; 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
>
>

Re: [Xsltforms-support] xalan infinite loop

[COUTHURES A. <ala...@ag...>]

Christian,
> I also was thinking that this recursion could maybe be replaced by a 
> regular expression, if I am not dependent on transforming it in the 
> browser. Only I would like to know what it _should_ do before I try to 
> make up some code.
There is no regular expression support in XSLT 1.0 but I have committed 
what should be an improvement for this situation.

It seems to work correctly but I can't see if it's faster or slower! I 
have limited name length to 100, just in case...

Can you please tell me if you see a significant difference ?

Thanks!

-Alain

Re: [Xsltforms-support] Is there any way to put markup in a textarea in XSLTForms

[Dan M. <dan...@gm...>]

Hello Claudius,

I installed CKEditor on eXist and wrote up the following notes here:

http://en.wikibooks.org/wiki/XForms/CKEditor

I can now see the XHTML in the HTTP Post but I can not seem to get it to
stop encoding the XML tags.

I put a copy of this form on our demo server here:

http://demo.syntactica.com/exist/rest/db/test/ckeditor/_samples/replacebyclass.html

If you can figure out how to get the config.js file to stop encodeing let me
know!  CKEditor does not have very good documentation yet :-(

- Dan

On Thu, Mar 4, 2010 at 3:31 PM, Claudius Teodorescu <cla...@ya...>wrote:

> Hi,
>
> I also thought about an extension element for XSLTForms, called
> "richTextarea" (maybe), which would allow all sort of rich text editing (I
> thought about editing the files stored within eXist, and for translations (a
> web app to manage translations)).
>
> I looked over web editors, found CKEditor and liked it very much, as being
> enough complex and flexible to be a professional extension element for
> XForms.
>
> Such extension element called richTextarea should be bound to a node, just
> like textarea element.
>
> My two cents.
>
> Claudius Teodorescu
> http://kuberam.ro
>
>
>
> ------------------------------------------------------------------------------
> 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
>
>


-- 
Dan McCreary
Semantic Solutions Architect
syntactica.com
952-460-1674
VOIP: 111@69.199.167.229

Re: [Xsltforms-support] xalan infinite loop

[Christian M. <chr...@mu...>]

Hi
The good message: The resulting javascript is very responsive and great to
use. I also was thinking that this recursion could maybe be replaced by a
regular expression, if I am not dependent on transforming it in the browser.
Only I would like to know what it _should_ do before I try to make up some
code.

Maybe it would even be a valuable strategy to fork the xsltforms to a more
performance optimized version which allows to use exsl. I think that the use
of xslt forms with something like existdb, as in my case, is a very nice use
of xsltforms. Maybe even more useful than the application in the browser.
Also I could store the generated code in some cache  be cause the only thing
that needs to change often is the instance  data.



> Do you have very very long names in instances??
>
> no, not really, but a lot of instance data because I have an instance with
all attribute default values and one with all elements and their minimal
data model.

How I found out was to compare the template hit counts in the debugger. With
xalan getname has a count of over 10 000
before it crashes.   With saxon 6.5.5 no template has a count larger than
9000 and getname has much less.
saxon takes also more than a minute to do my form. I don't think that this
must be so slow it could probably get orders of magnitudes faster.

Thanks!
>
> -Alain
>

Thanks!

Re: [Xsltforms-support] Is there any way to put markup in a textarea in XSLTForms

[Claudius T. <cla...@ya...>]

Hi,

I also thought about an extension element for XSLTForms, called "richTextarea" (maybe), which would allow all sort of rich text editing (I thought about editing the files stored within eXist, and for translations (a web app to manage translations)).

I looked over web editors,  found CKEditor and liked it very much, as being enough complex and flexible to be a professional extension element for XForms.

Such extension element called richTextarea should be bound to a node, just like textarea element.

My two cents.

 Claudius Teodorescu
http://kuberam.ro


      

Re: [Xsltforms-support] Is there any way to put markup in atextarea in XSLTForms

[Klotz, L. <Lei...@xe...>]

It might be possible to decompose this so that different people can attack the different parts of the problem:
 
1. xsltforms global variable/name usage so it plays nice with other js libs
2. a plugin or second stylesheet to enable xf:textarea/@mediatype='text/html'
 
Leigh.

________________________________

From: Dan McCreary [mailto:dan...@gm...] 
Sent: Thursday, March 04, 2010 1:08 PM
To: COUTHURES Alain
Cc: xsl...@li...
Subject: Re: [Xsltforms-support] Is there any way to put markup in atextarea in XSLTForms


Hello Alain,

Thanks for your quick reply!

I think we may have to add this to your TODO list.

I am sorry we were not able to get everyone together this week for some training.  It will have to wait till we get back from Prague I believe.

But it looks like we have a few items that should fill up at least one day of consulting.

I will continue to work with CKEditor to see if I can get at least that part working.

- Dan


On Thu, Mar 4, 2010 at 2:50 PM, COUTHURES Alain <ala...@ag...> wrote:


	Hi Dan, 


		Can anyone tell me if there is a way to put HTML markup in a XSLTForms
		textarea?  I need to do basic HTML like list items, bold, italic.
		 
		

	As in other XForms implementations, xf:output mediatype="application/xhtml+xml" will render text containing serialized XML (&lt; and &gt; instead of < and >) as XHTML. Effective XHTML, instead of text, is not yet supported.
	
	xf:textarea is now consistent with that: enter < (or >) and &lt; (or &gt;) will be written in the corresponding node as ordinary text.
	
	A new type might be added so the control is valid only if the corresponding text can be parsed. Then, for submission, it would be serialized as XML and not as text. I already can see one restriction: would it be acceptable for your project not to be able to parse at client-side the entered markup? 


		In the long run it would be nice to have CKEditor to working within eXist.
		
		Here is the link to CKEditor: http://cksource.com
		 
		

	Yes, I'm convinced that "real" applications will require this kind of controls.
	
	XSLTForms Javascript code is not yet well protected against conflicts with other Javascript code...
	
	A workload of some days is to consider.
	
	Thanks!
	
	-Alain
	
	




-- 
Dan McCreary
Semantic Solutions Architect
syntactica.com
952-460-1674
VOIP: 111@69.199.167.229

Re: [Xsltforms-support] Is there any way to put markup in a textarea in XSLTForms

[Dan M. <dan...@gm...>]

Hello Alain,

Thanks for your quick reply!

I think we may have to add this to your TODO list.

I am sorry we were not able to get everyone together this week for some
training.  It will have to wait till we get back from Prague I believe.

But it looks like we have a few items that should fill up at least one day
of consulting.

I will continue to work with CKEditor to see if I can get at least that part
working.

- Dan

On Thu, Mar 4, 2010 at 2:50 PM, COUTHURES Alain <
ala...@ag...> wrote:

> Hi Dan,
>
>  Can anyone tell me if there is a way to put HTML markup in a XSLTForms
>> textarea?  I need to do basic HTML like list items, bold, italic.
>>
>>
> As in other XForms implementations, xf:output
> mediatype="application/xhtml+xml" will render text containing serialized XML
> (&lt; and &gt; instead of < and >) as XHTML. Effective XHTML, instead of
> text, is not yet supported.
>
> xf:textarea is now consistent with that: enter < (or >) and &lt; (or &gt;)
> will be written in the corresponding node as ordinary text.
>
> A new type might be added so the control is valid only if the corresponding
> text can be parsed. Then, for submission, it would be serialized as XML and
> not as text. I already can see one restriction: would it be acceptable for
> your project not to be able to parse at client-side the entered markup?
>
>  In the long run it would be nice to have CKEditor to working within eXist.
>>
>> Here is the link to CKEditor: http://cksource.com
>>
>>
> Yes, I'm convinced that "real" applications will require this kind of
> controls.
>
> XSLTForms Javascript code is not yet well protected against conflicts with
> other Javascript code...
>
> A workload of some days is to consider.
>
> Thanks!
>
> -Alain
>
>


-- 
Dan McCreary
Semantic Solutions Architect
syntactica.com
952-460-1674
VOIP: 111@69.199.167.229

Re: [Xsltforms-support] Is there any way to put markup in a textarea in XSLTForms

[COUTHURES A. <ala...@ag...>]

Hi Dan,
> Can anyone tell me if there is a way to put HTML markup in a XSLTForms
> textarea?  I need to do basic HTML like list items, bold, italic.
>   
As in other XForms implementations, xf:output 
mediatype="application/xhtml+xml" will render text containing serialized 
XML (&lt; and &gt; instead of < and >) as XHTML. Effective XHTML, 
instead of text, is not yet supported.

xf:textarea is now consistent with that: enter < (or >) and &lt; (or 
&gt;) will be written in the corresponding node as ordinary text.

A new type might be added so the control is valid only if the 
corresponding text can be parsed. Then, for submission, it would be 
serialized as XML and not as text. I already can see one restriction: 
would it be acceptable for your project not to be able to parse at 
client-side the entered markup?
> In the long run it would be nice to have CKEditor to working within eXist.
>
> Here is the link to CKEditor: http://cksource.com
>   
Yes, I'm convinced that "real" applications will require this kind of 
controls.

XSLTForms Javascript code is not yet well protected against conflicts 
with other Javascript code...

A workload of some days is to consider.

Thanks!

-Alain

[Xsltforms-support] Is there any way to put markup in a textarea in XSLTForms

[Dan M. <dan...@gm...>]

Hello XSLTForms fans!

Can anyone tell me if there is a way to put HTML markup in a XSLTForms
textarea?  I need to do basic HTML like list items, bold, italic.

In the long run it would be nice to have CKEditor to working within eXist.

Here is the link to CKEditor: http://cksource.com

I got the old version of this tool (FCKEditor) to work with the
FireFox but that was several years ago.  The documentation for that is
here:

http://en.wikibooks.org/wiki/XForms/Rich_Text_Editor

Thanks! - Dan

-- 
Dan McCreary
Semantic Solutions Architect
syntactica.com
952-460-1674

[Xsltforms-support] xalan infinite loop

[Christian M. <chr...@mu...>]

Hi,
 I have a very large xform I want to render with xsltforms in exist db. I
can render it in the browser allthought it takes a minute also xsltproc and
saxon 6.5.5 does the job xalan however fails because the recursion in
<xsl:template xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
name="getName">
<xsl:param name="s"/>
<xsl:param name="r"/>
<xsl:choose>
<xsl:when test="$s = ''"><xsl:value-of select="$r"/></xsl:when>
<xsl:otherwise>
<xsl:variable name="c" select="substring($s,1,1)"/>
<xsl:choose>
<xsl:when
test="contains('_.-0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz',$c)
or ($c=':' and not(contains($r,$c)))">
<xsl:call-template name="getName">
<xsl:with-param name="s" select="substring($s,2)"/>
<xsl:with-param name="r" select="concat($r,$c)"/>
</xsl:call-template>
</xsl:when>
<xsl:otherwise><xsl:value-of select="$r"/></xsl:otherwise>
</xsl:choose>
</xsl:otherwise>
</xsl:choose>
</xsl:template>

never exits.  This at least shows in the oxigen xslt debugger.

maybe it is a problem of xalan but I thought you might want to know.
cheers

[Xsltforms-support] Submission/@replace='all'

[Klotz, L. <Lei...@xe...>]

This is a follow-on to the discussion before on xsltforms-support [1].

We discussed the issue of replace='all' and user agent behavior at the W3C Forms Working Group.

Particular issues were the user agent behavior expectations for "new page" with regards to the location displayed and the behavior of the back button.

Here is the resolution: [2]

    Resolution 2010-02-24.1: Dispatching xforms-submit-done
    and xforms-submit-error after submission/@replace='all'
    is optional and is not as important as other
    considerations, such as conforming to non-XForms user
    agent requirements of showing the page's URI and back
    button. While some non-native (JavaScript and
    server-side) XForms+XHTML implementations have been able
    to use techniques to retain most of these advantages in
    the complex cases of POST with application/xml
    serialization, we still see it as more important to
    conform to greater user-agent expectations in easier
    cases, such as <submission method='get' replace='all'>.

My belief is that if the back button and location bar issues can be solved (and Erik Bruchez seems to think at least back button can be solved) that the current XSLTForms approach is good; however, if they can't, the replace='all' ought to do actual browser page loads in cases where it can.  Another option is offering an XSLTForms extension value for replace or submission method for keeping the page but breaking location and back.

[1] http://tinyurl.com/yenkenu
[2] http://lists.w3.org/Archives/Public/public-forms/2010Feb/att-0046/2010-02-24.html#resolution1

Leigh.

Re: [Xsltforms-support] add element to empty element

[Christian M. <chr...@mu...>]

changing
line 2493: if (index >= nodes.length ) {
to
line 2493: if (index >= nodes.length && nodes.length != 0) {
in xsltforms.js
fixes the issue for me

On Mon, Mar 1, 2010 at 11:34 AM, Christian Meisenbichler <
chr...@mu...> wrote:

> Hi all
> I do have a strange problem that might be a bug. I can now insert
> attributes and I can also insert elements into elements that contain already
> one sibling of the same name. If i try however to insert an element into an
> empty element I do get
>
> "Uncaught TypeError: Cannot read property 'nextSibling' of undefined
> xsltforms.js:2494<http://localhost:8080/exist/rest/www/xforms/xsltforms/xsltforms.js>
> "
>
> When I add an element to the instance and try again a second element is
> added just fine.
>
> my insert element looks as following:
>
>  <xf:trigger>
>  <xf:label>Add: spin</xf:label>
> <xf:action ev:event="DOMActivate">
> <xf:insert context="/input/groundstate"
> origin="instance('elemprototype')/spin" nodeset="spin"/>
> </xf:action>
> </xf:trigger>
>
> I am using xsltforms svn 357
>
> Yours grateful
> Christian
>