453 |
allowing the reader to see which alternate spatial views are available for the |
allowing the reader to see which alternate spatial views are available for the |
454 |
current node. |
current node. |
455 |
|
|
456 |
.. figure:: diagramlinks.gen.eps |
.. figure:: umldoc-linking.gen.eps |
457 |
:width: 16.9cm |
:width: 16.9cm |
458 |
:alternative: * |
:alternative: * |
459 |
:label: diagramlinks |
:label: diagramlinks |
630 |
can no longer talk about objects that are not immidiately |
can no longer talk about objects that are not immidiately |
631 |
visible." [gentner-nielsen96anti-mac-onpage-74]_ |
visible." [gentner-nielsen96anti-mac-onpage-74]_ |
632 |
|
|
633 |
The direct manipulation user interface do not necessarily improve |
Direct manipulation user interface do not necessarily improve |
634 |
performance: users must learn the meaning of the graphical components, |
performance: users must learn the meaning of the graphical components, |
635 |
graphic presentation could be misleading, graphical presentation could |
graphic presentation could be misleading and graphical presentation could |
636 |
take excessive screen display space |
take excessive screen display space |
637 |
[shneiderman83direct-manipulation-onpage-64]_. The direct manipulation |
[shneiderman83direct-manipulation-onpage-64]_. Direct manipulation |
638 |
interfaces could be also rather slow to use, since in a such interface |
interfaces could be also rather slow to use, since in a such interface |
639 |
user have to directly manipulate everything. Instead of an executive |
user may have to directly manipulate everything. Instead of an |
640 |
who gives high-level instructions, the user is reduced to an assembly |
executive who gives high-level instructions, the user is reduced to an |
641 |
line worker who must carry out the same task over and over |
assembly line worker who must carry out the same task over and over |
642 |
[gentner-nielsen96anti-mac-onpage-74]_. The UML langage has XXX different |
[gentner-nielsen96anti-mac-onpage-74]_. The UML langage has a large |
643 |
symbols and XXX different connections between them. It is a quite |
amount of different symbols and different connection types between |
644 |
challanging for a direct manipulation interface to make all these |
them [booch-jacobson-rumbaugh98uml-reference-manual]_. It could be |
645 |
alternatives as easily available as they could be typed within lexical |
quite challanging for a direct manipulation interface to make all |
646 |
description. |
these alternatives as easily available as they could be just typed |
647 |
|
when using lexical description. |
|
Describing existing objects for diagram is easy done as lexical |
|
|
description, but the graphical placing of objects is a bit more |
|
|
complicated, although, not impossible. |
|
648 |
|
|
649 |
.. figure:: umltool-example-uml.gen.eps |
.. figure:: umltool-example-uml.gen.eps |
650 |
:label: umltoolumlsource |
:label: umltoolumlsource |
651 |
:width: 6cm |
:width: 4.5cm |
652 |
|
|
653 |
Example of UML tool object description. |
Example of UML tool object description. |
654 |
|
|
655 |
|
In our UML tool the describtion of UML diagram is divided in two: into |
656 |
|
a description of all the elements in diagram [ref-umltoolumlsource]_ |
657 |
|
and description their graphical layout [ref-umltoolmpsource]_. We |
658 |
|
argue that for a programmer used to Describing existing objects for |
659 |
|
diagram is easily done using our UML tools's lexical description |
660 |
|
language, but the graphical placing of objects is a bit more |
661 |
|
complicated, although, not impossible. We admit that after objects for |
662 |
|
the diagram are selected, the graphical placing for them could be done |
663 |
|
easiest by using direct manipulation. |
664 |
|
|
665 |
|
|
666 |
.. figure:: umltool-example-mp.gen.eps |
.. figure:: umltool-example-mp.gen.eps |
667 |
:alternative: * |
:alternative: * |
668 |
:label: umltoolmpsource |
:label: umltoolmpsource |