Kevin Flynn wrote: > > These two additions (or something similar) would be nice to have, and make > XXE even better than it already is (for me at least)... > > 1 When the set-attribute-button function is used for an IDREF attribute, the > resulting command menu can be very long in some documents. Is there any > chance of: > > - an option enabling the menu functions to be displayed in a scrollable box > instead of as a true menu?
OK but you'll have to use a command-button executing command putAttribute rather set-attribute-button. We'll enhance the putAttribute command to let it display ``a scrollable box'' for enumerated values, ID, IDREF, IDREFS, etc. Currently this command, which has not really been designed to be used interactively, displays a very simple prompt in all cases. > - the ability to filter the ID elements displayed in the menu (using an > XPath expression or even just an element name)? > > I use ID/IDREF for a variety of different purposes in my documents, and it > would be great to be able to display only the IDs that are actually of > interest in a given context. > > 2 An XXE-CSS command that enabled the display of an element to be > constructed from the result of an XPath expression would be great (one could > then, for example, display the actual title of a cross-referenced section). > I know XXE only implements a subset of XPath, but even a subset would > presumably open up quite a few possibilities... I don't think that the subset of XPath currently implemented in XXE is powerful enough. You could just use it to search an element or an attribute in the *subtree* of the element which is the target of the CSS rule. And for what you want to do, this is not enough.
