Mark Fletcher wrote: > > How hard is it to implement a command that would combine the > functionality of, say, Select Parent and Insert After? What I'd like is > to be able to select the parent of the current element AND update the > contents of the Insert After list in one step, and while the focus is > still on the Edit tab. > > Here's my usage scenario: > > 1. User is typing text into a <para> tag. > 2. User presses Ctrl+J to insert an element after <para>, but because > #text is the current element, he gets a list of inline elements instead. > The Edit text box is in focus. > 3. User presses Ctrl+J again and the parent <para> is selected. The Edit > list is updated with elements valid for inserting after the <para>.
Many things can be done with XXE (for example: "select ancestor para if any + insert after" is trivial) but the *exact* behavior you describe cannot be implemented. I'm sorry but XXE is not good enough to adapt to your way of doing things. Unfortunately, you, as a user, have to adapt to its way doing things. If you want to insert something after a para, the easiest way to do it is to use the *implicit* *element* *selection*: [1] Click anywhere inside the para, but not inside any of its child elements. Thus anywhere precisely means inside any child #text node. [2] Use Edit|Insert After. Now, if your users are keyboard diehards, being inside the para, most of the time, they simply have to press Ctrl-J[*]. No explicit selection at all! Could it be simpler? Implicit element selection is, in our opinion, one of the features which makes XXE efficient to use. The only problem is that your users have to *learn* about this feature. > A related question: Is it possible to display the name of the current > element as a label somewhere on the Edit tab? For example "Insert > element after <curr_element_name>" or even just "Current element: > <curr_element_name>". The element which is explicitly or implicitly selected is already displayed in the node path bar. All editing commands act on this element. > Finally, where does a CSS stylesheet have to exist in order to be > considered "available" to be assigned to a new View? The CSS style sheet must have been ``declared'' in the configuration associated to the type of document you are editing. > Are you considering adding Browse functionality to that dialog? We are considering allowing the end user to customize XXE (to a certain extent) without having to edit configuration files. This would mean, among other things, adding a CSS style sheet, making a CSS style sheet the default one, etc. --- [*] Have you tried Ctrl-Enter? Very handy too.
