[Xsltforms-support] No response on the CKEditor forums to question on encoding
Brought to you by:
alain-couthures
|
From: Dan M. <dan...@gm...> - 2010-03-05 14:51:11
|
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 |