Philippe Nobili wrote:
> 
> May we suggest two small improvements for XMLMind (we currently use 4.2.1):
> 
> + When adding mediaobject to a DocBook document, the file selector used
> for specifying the image file always opens in the location of the XML
> source. It would certainly be better (better for us in any case) if it
> would always open in the last used location (images are usually all kept
> at the same place, notnecessarily with the XML document itself).

Images are often kept in a subdirectory of the directory containing the
document. Different documents are almost always kept in different
directories. Hence, when you work with different documents, images are
usually *not* kept in the same place.


> 
> + The image directory frenquently contains may images; since the file
> selection always comes back to its initial default size, we have to
> resize it again and gain to have a usable file's view. Could it retained
> the last size ? (and, cherry on the cake, could it scrolls by default to
> the last position ?).

There will always be something wrong with Java's standard file chooser.
Please consider using drag and drop from the file explorer of your OS.
(Drop the image from the file explorer to the image placeholder icons
found in the document views displayed by XXE).



> 
> This may seem minor details, but they freally make a difference in
> certain contexts...
> 
> + The last one look more like a bug. In the URL selection box used to
> save the result of XML conversion (e.g. DocBook > Convert ...), it seems
> that the ftp:// locations are systematically lost from one session to
> another. Did we miss something ?

Many other user choices (e.g. searched strings, collapsed sections,
opened files, etc) are not remembered across editing sessions. Why would
it  be a bug in this specific case?

"DocBook > Convert > Convert to PDF" suggests "C:\doc\foo.pdf" when you
convert "C:\doc\foo.xml" to PDF. If you reject "C:\doc\foo.pdf" and
instead choose "ftp://acme.com/doc/foo.pdf";, then XXE will suggest
"ftp://acme.com/doc/XXX"; for all subsequent conversions (to PDF or other
formats). We find this behavior rather sensible.

--> A bug is when something does not work like intended. In *all* the
above cases, it works like intended. In some cases, this is caused by
obscure implementation constraints which force us to be less
user-friendly that we would like to be. In other cases, it is a user
interface design choice having a rationale (which indeed annoys you, but
please keep in mind that changing to what you suggest may annoy other
users, notably users which work with many different documents).

As usual, we'll examine the problems you have reported one by one and
we'll *try* to improve the situation. Note that it's too late for XXE
v4.3 which should be released tomorrow.









Reply via email to