Philippe Nobili - GPM Team wrote:
> 
> Please find hereafter a couple of suggestions for improvements related
> to XMLmind (we currently use version 3.6.1). Thank you as usual for your
> suggestions if some of these can already be achieved with the current
> release and thank you for your very good reactivity in any case.
> 
> Best regards,
> 
> *1) Upgrades*
> 
> Upgrading XMLmind is not straightforward, especially because of the
> potential incompatibilities of installed add-ons with the new release of
> XMLmind; a way to also upgrade all installed add-ons would certainly
> help (something similar to what exists for Firefox).

We agree with you. Implementing this enhancement has been added to our
TODO list.



> *2) Multiple Selection of Elements*
> 
> Once a selection is done, is it possible to extend it to the next or
> preceding sibling from the Select menu. A way to do this directly with
> the mouse using a key modifier -- Ctrl- or Shifft- as for multiple
> selection for example - would make this extended selection more
> efficient. Another way would be to extend automatically the selection
> while the mouse button is pressed (something like the browse selection
> in Xm lists).

Keyboard: "Esc Left-Arrow" and "Esc Right-Arrow". You don't need to
select anything beforehand: just press "Esc Right-Arrow" several
times in a row. (Personnally, I use this shortcut all the time.)

Mouse: First select a node then Ctrl-Shift-Click anywhere before or
after this node to select all its siblings.

See http://www.xmlmind.com/xmleditor/_distrib/doc/user/being_productive.html

See Quick reference cards in PDF format
http://www.xmlmind.com/xmleditor/_distrib/doc/quickrefcard/quickrefcard-A4.pdf



> *3) Finding available ID for linkend (link, xref)*
> 
> The dialog box which allows to select one of the available IDs for
> /linkend/ attribute is limited to the current XML document. When the
> final document is composed of the aggregation of several XML documents
> inserted by reference (one for each chapter for instance in the case of
> books), the IDs you can refer to for /linkend/ attributes have to be
> found from all referenced documents, not only from current one.
> 
> The only solution you have in this case is to enter the /linkend/
> attribute by end.

XXE is just a ``topic editor''. It has no concept of ``project''. It is
not designed to work on several ``topics'' as a whole. Such feature
(even if it seems natural and easy to implement) is outside the scope of
XXE but we are currently working on a new, high-end, product (leveraging
XXE) which should make it easy to solve such problems (among many other
things).


> (Note that your document is also flagged as invalid in this case).

This should not disturb you: Unlike the red icon, a yellow icon just
indicates cross-reference errors and not severe, structural, errors.



> *4) Customization of XSLT Stylesheets
> *
> (Already mentioned in a previous e-mail, just here as a reminder)
>
> We need to use of couple of customizations, valid for all our XMLmind
> users; each customization deals with PDF, HTML (+ chunked) and Java Help
> outputs and serves a specific purpose, because some conventions may
> changed depending on the product we write the documentation for.
> 
> It would be convenient to be able to load a named customization from
> disk file (from a .xxe file for example); this customization would
> override whatever default have been loaded automatically during startup
> and would allow us to maintain our different sets of customization layers.

I'm sorry but we do not intend to improve the customization of XSLT
stylesheets in the near future.

Meanwhile, I would suggest that you create *by* *hand* different
customizations of the DocBook configuration. See
http://www.xmlmind.com/xmleditor/_distrib/doc/configure/customizing.html

Note that a feature added to the very last version makes it easy to
automatically apply different customized configurations to different
DocBook documents. See "rootElementAttribute" in
http://www.xmlmind.com/xmleditor/_distrib/doc/configure/detect.html

Yes, this is a trick but it should serve you well.

(If you intend to use the "rootElementAttribute" facility, do not forget
to give the customized configurations names different from "DocBook".)


Reply via email to