|
|
Some Hints for configuring BXEThie following is the edited version of some questions on the mailinglist: http://lists.bitflux.ch/pipermail/bx-editor-users/2004-May/000062.html I have found absolutely no current documentation about A: configuring bitflux in its current version and B: how is bitflux integrated in lenya. In BXE, there are mainly 2 places to configure the Editor. First, the RelaxNG itself, for defining which elements are allowed where. RelaxNG is an alternative to XML Schema and relatively easy to understand. More info about RelaxNG can be found at http://relaxng.org/. Where this RelaxNG file can be found within Lenya was answered in another mail. The second place is the config.xml Besides defining which files to load, from where and some button definition, you can also define, which elements (defined in the RelaxNG) should not appear on the popups. See http://cvs.bitflux.ch/chora/co.php/trunk/examples/uni/config.xml?rt=svneditor&r=687#120 for an example (the <context type="dontShow"> part) the config.xml is also somewhat described in http://wiki.bitfluxeditor.org/index.php/config.xml My problems in detail: 1. It is not possible to make a word bold. Bitflux always claims: "b is not allowed as a child of p" (this is possible in the original examples of bitflux) change the button definition in the config.xhtml from <button name="b" col="1" row="1" action="ToggleTextClass" ns="http://www.w3.org/1999/xhtml"/> to <button name="strong" col="1" row="1" action="ToggleTextClass" ns="http://www.w3.org/1999/xhtml"/> {panel}
2. In the upper left corner you have a bunch of xhtml style elements in the examples (like xhtml:p, xhtml:h1, xhtml:li,...) In the lenya default pub there are just two 4 of that (p, h1-4)
{panel}
remove the ones you want to show from the config.xml. To make it hopefully clear, what those 2 different "files" intend to do: The RelaxNG Schema is for defining which elements and attributes are allowed where. It's the general approach to the problem, using a widely known standard. In the Config.xml, you can adjust, what BXE should show to the user (besides other configuration issues). As the XHTML standard is quite huge, we didn't want to show all possibilities to the enduser, but still allow to validate these X(HT)ML documents. |
Add Comment