On 19 Mar 2018, at 9:29, Hussein Shafie wrote:
On 03/18/2018 09:50 PM, Leif Halvard Silli wrote:
(Relating to XMLmind XML Editor version 8.0)
When clicking a R/O button when the referenced file is already open
for
editing, XXE could benefit from issuing a warning to the user.
Background:
Version 8 has 3 new toolbar buttons which opens files in read only
mode
(namely "Open Topic R/O", "Open Page R/O", and "Open Resource R/O".)
XXE always had these buttons. Simply the new v8 UI makes them more
"visible".
The new interface good! For instance, I like how you it the interface
tries to operate with the same concept regardles of the file format -
Ebook, XHTML, Docbook, DITA. Of course, there was an element of the same
in the earlier versions as well. But in v8 you are taking it a step
further. It is like the toolbar has become a meta language of its own
... ;-)
Because, if the file is already open for editing (in another tab or
window) when the R/O button is clicked, the user is simply brought to
the existing tab/window where the file is already open. As a result,
the
user might end up thinking that the file is indeed in read only when
it,
in reality, is not. (
And by the way, the opposite is also the case: If the file is open
for
read only already, pressing the Open Topic button will not be
converted
to editing mode.
You are right. The problem is that the feature you request is not easy
to implement (e.g. file locks; a R/O file is never locked). We'll see
what we can do, given the fact that switching from R/O to R/W and the
other way around is not expected to be used very often.
Thumbs up.
The Tabs of XXE are easily hidden for the user. Depending on the size
of
the screen, or whether the Window has been split in two, or whether
the
file names are long or short, the room for Tabs can quickly decrease.
My
XXE editing window sometimes only have room for two visible tabs on
my
20inch monitor. And so it is not, in my judgement, a rare thing that
users might loose track of which files are open (in this or that
mode)
already.
Note taken. We'll consider limiting the width of a tab by eliding very
long file names ("A_very_very_very_long_file_name.ditamap" -->
"A_very_very_…_file_name.ditamap").
That could help the above problem, and sounds like an improvement in
general. However you should perhaps consider to truncate from the right
("A_very_very_very_long…") instead of truncating from the middle
("A_very_very_…_file_name.ditamap"). Why: 1) Most people know what
format the work with. 2) The file name becomes more
readable/meaningfull. 3) And, when you hover above a tab, the format
(read:”configuration”) of the file is mentioned anyway (which
includes full file name, including file extension/suffix), so it should
not be very important to include the file extension - when this makes
the Tab too wide.
Slightly off topic: But why do we have to open a file in order to know
the title of the file? When one hovers above a tab, why not list the
title of the file as well?
Leif Halvard Silli
--
XMLmind XML Editor Support List
xmleditor-support@xmlmind.com
http://www.xmlmind.com/mailman/listinfo/xmleditor-support
