Hello,
First of all, thanks for creating a great open source tool. It looks very nice.
I am attempting to port CKEditor to work with the XSLTForms product under the eXist-db.org native XML database.
I did get the files loaded into exist. I just had to escape the ampersands with & and to remove the nbsp and copy entities to be well-formed XHTML files.
I am now trying to figure out how to configure CKForms to NOT encode the XHTML in the POSTDATA. I can not seem to find this information in the 3.2 documentation.
I will be creating a user guild for porting CKEditor to XForms and eXist.
Thanks! - Dan
First of all, thanks for creating a great open source tool. It looks very nice.
I am attempting to port CKEditor to work with the XSLTForms product under the eXist-db.org native XML database.
I did get the files loaded into exist. I just had to escape the ampersands with & and to remove the nbsp and copy entities to be well-formed XHTML files.
I am now trying to figure out how to configure CKForms to NOT encode the XHTML in the POSTDATA. I can not seem to find this information in the 3.2 documentation.
I will be creating a user guild for porting CKEditor to XForms and eXist.
Thanks! - Dan
Re: Getting CKEditor to work with XSLTForms and eXist-db.org
Hello CKEditor fans,
First my apologize. I am very new to CKEditor and I am not an experienced JavaScript developer. I only know XML, XPath, XQuery, and XForms.
For those of you that might be interested in our port to eXist-db.org and the XSLTForms project I have created a page with my notes here:
http://en.wikibooks.org/wiki/XForms/CKEditor
We have many people that seem to think that a good rich-text editor is critical to a strong native XML based CMS. So we are looking for partners (i.e. funding) for this project.
I have started to create a database of all of the configuration options for our port and how they might work in an XRX CMS. In this case all the configuration is usually done with indexed XML files and the configuration files are edited directly with XForms tools. Our goal is to allow non-JavaScript users to customize the editor configuration options.
Our first step will be to classify each configuration option to create a multi-tab editing form to edit the configuration options. I suspect that most of the CSS/presentation related options will be put into a single CSS file to begin.
I have an early version of the option classifiers here:
http://demo.syntactica.com/exist/rest/d ... t-items.xq
And I would love any feedback on how people feel the options should be logically classified on a form.
Thanks! - Dan
BTW, is it a little ironic that the form used on on the forum does not use CKEditor? :-O