First of all, I have to congratulate you on the XXE 2.3 release, and the
vastly improved support for editing xml data. It inspired me to do some
css hacking to customize and clean up the display for some of our DTDs.
I have run into a few points where XXE doesn't quite do what I want -
perhaps you can suggest alternatives, or extend it in the next version.
I would like to have a convert button which has a text that is the
element name; this way, users clicking on the name are offered a list of
alternative names, e.g.
*:before {
content: division(
content(
paragraph(
content(collapser(collapsed-icon, icon(pop-right),
expanded-icon, icon(pop-down)), " ",
convert-button(text, element-name()), " ",
replace-button(), " ",
insert-before-button(), " ",
insert-button(), " ",
insert-after-button(), " ",
delete-button(), " ",
add-attribute-button(check-has-attributes, yes,
color, navy)),
background-color, silver,
padding-left, 4),
attributes(margin-top, 2,
margin-bottom, 2,
margin-left, 2,
margin-right, 2)));
}
Unfortunately, element-name() appears to have no value in this context.
I can set up specific rules for each element, with the name as a fixed
string, but this requires a lot of duplication.
Another glitch is that a command-button which inserts an element with a
required enumerated attribute creates the element with the attribute
value as "???" but the combobox item simply displays the first menu
choice (in red). This can be a bit confusing, because you can't see the
"???" that the validation error refers to. Is there any way to specify
the attribute value for a newly inserted element in the css? Or at
least have the generated combobox special-case the value "???" and
display it? (It would be useful if the combobox displayed any current
value of the attribute, but even just "???" would help a lot).
Finally, is there any way to specify the initial state of a collapser?
Or to collapse/expand all elements?
Thanks for any help you can provide.
@alex
