Hello Hussein,
thank you for your quick reply...
Hussein Shafie wrote:
> Bernd Kuemmerlen wrote:
>
>>My question is: Would it be possible to have a mode in which the
>>"normal" text selection (and a copy of this) would at least include all
>>totally enclosed markup tags? This would save a lot of hassle when
>>people try to copy complete paragraphs. The normal expectation is to be
>>able to easily copy the markup within the paragraph. Or are there any
>>technical reasons which prohibit this?
>
> No, it just takes a lot of experimentation and a lot of work. (Remember
> that text selection works across elements.)
Yes, I understand the implicit problems, especially when pasting such a
selection somewhere where it would violate the dtd.
>>The issue is even more important
>>because the Shift-Ctrl-Click to select markup nodes in the normal
>>text-view sometimes does not seem register, so it is very difficult to
>>select multiple nodes (it's mostly OK in the tree view).
>
>
> There is no bug here. 99% of the time, Shift-Ctrl-Click will not work
> because user has not selected previously the right first node of the
> range. (Shift-Ctrl-Click can only be used to select nodes having the
> same parent.)
>
> For example, if you want select all nodes in a paragraph, first you have
> to explicitly select first child of the paragraph: if it is an element,
> explicitly select this element; if it is a text node, explicitly select
> this text node.
Ah, this explains it. I have read the userguide, but this was not
completely clear to me. Maybe this behaviour could be expanded a bit to
automatically select the smallest possible parent when trying to select
two nodes with different parents. I think this is what the user would
want most of the time anyway. Let me explain this:
If I have the following structure:
<itemizedlist>
<listitem>
<para>Foo</para>
<para>Bla1 <emphasis>Rhubarb</emphasis></para>
<para>Bla2</para>
</listitem>
</itemizedlist>
If I Ctrl-Click on the "Foo" text, the text node gets selected. At first
it is not possible to Shift-Ctrl-Click the "Bla1" text node (and now it
is clear to me why you can't). It seems to me that Shift-Ctrl-Click
should go up the tree to the enclosing para and then also select the
para containing the "Bla1" text node. Or if you consider the emphasis
"Rhubarb". Here it makes a difference if you first select Rhubarb (and
therefore just the text node), you then are not able to select Bla1
(because they do not have the same parent), but the other way round it
works. For most of the people who are not really aware of the underlying
structure (and as you say for the tree view, it should not be
necessary to know too much about this structure.) this seems if not
buggy at least inconsistent, because in the styled view you can't see
that "Rhubarb" and Bla1 are not on the same hierarchy level (well, in
this special case you could infer it because "Rhubarb" is rendered
differently, but in general you can't see it), you can't even see a
difference between selecting the "Rhubarb" text node or the emphasis
node. If you would extend the behaviour to what I described above, this
would work as expected. Please do not understand me wrong, I am just
trying to give a bit of constructive criticism.
> PS: In XXE, if you have a stylesheet available, you really never, ever,
> need to use the tree view. If it is the case, may be you have missed
> something in the tutorial. No offense intended and of course, I'm not
> pretending that XXE is perfect. But the fact is that here at XMLmind, we
> never, ever, use the tree view, just the styled view.
No offense taken! Thank you for your help again, and keep up the good work.
Cheers
Bernd
--
Bernd Kuemmerlen | fon: +49-421-218-7704
MeVis - Center for Medical Diagnostic Systems | fax: +49-421-218-4236
and Visualization | mailto:bkuemmer at mevis.de
Universitaetsallee 29, 28359 Bremen, Germany | http://www.mevis.de/
