John L. Clark wrote: > According to the documentation[0], I should be able to make a xhtml:div > collapsible by adding a collapser widget :before the div (the > documentation also adds one :after, but that should be superfluous). > However, when I attempt it, it doesn't work. In the xhtml example, the > collapsers appear but do nothing. In a different XML configuration, they > appear and collapse the *parent* collapsible element. I can easily send > more information about the configuration if necessary, but I think I > have the CSS syntax correct. The widget appears correctly; it simply > does not collapse the correct element.
No, the xhtml:div example in the doc http://www.xmlmind.com/xmleditor/_distrib/docs/poweruser/ar01s06s03.html#collapsibleblocks really works fine. The behaviour you describe can be easily reproduced if you forget to mark the div as being collapsible. To do this, you really need to use proprietary CSS property "collapsible: yes;" (which is not inherited). In the doc, please notice "div[class=c3] {collapsible: yes;}": --- div { display: block; } div[class=c3] { collapsible: yes; } div[class=c3]:before, div[class=c3]:after { content: collapser(); display: block; margin: 5 auto; text-align: center; } div[class=c3]:after { content: collapser(collapsed-icon, icon(collapsed-left), expanded-icon, icon(expanded-up)); } --- > P.S. As a complete aside, I would like to renew my request for a feature > to be able to include user configurations by a particular name, so that > I can build on previous configurations. This would look something like: > > <cfg:include location="docbook/docbook.xxe" user="true"/> > > and would locate the configuration using the user's XXE configuration > directory as a base. Well, I don't understand this request (and, sorry, I don't remember it). --- <cfg:include location="docbook/docbook.xxe" system="true"/> --- is useful to extend system configuration without having to know where XXE has been installed. But in the case of a user's custom configuration, the user knows where he/she has created his/her configurations. In such case, a relative location should be sufficient. Example, a DocBook configuration file called ~/.xxe2/config/docbook_plus/0docbook.xxe could contain: --- <cfg:include location="../docbook_base/docbook.xxe"/> --- Notice the "0docbook.xxe" base name to force XXE to use ~/.xxe2/config/docbook_plus/0docbook.xxe rather than ~/.xxe2/config/docbook_base/docbook.xxe when editing DocBook documents (only useful when both configurations are named "DocBook").
