[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gzz-commits] manuscripts/UMLLink Makefile article.rst umldoc...
From: |
Asko Soukka |
Subject: |
[Gzz-commits] manuscripts/UMLLink Makefile article.rst umldoc... |
Date: |
Fri, 14 Feb 2003 18:08:52 -0500 |
CVSROOT: /cvsroot/gzz
Module name: manuscripts
Changes by: Asko Soukka <address@hidden> 03/02/14 18:08:52
Modified files:
UMLLink : Makefile article.rst umldoc-flow.dia
umldoc-refer-flow.dia umltool-example-mp.dia
umltool-example-uml-linked.dia
umltool-example-uml.dia
Added files:
UMLLink : umldoc-linking.dia umltool-convert-process.dia
Removed files:
UMLLink : diagramlinks.dia
Log message:
umltool process diagram
CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/UMLLink/umldoc-linking.dia?rev=1.1
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/UMLLink/umltool-convert-process.dia?rev=1.1
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/UMLLink/Makefile.diff?tr1=1.8&tr2=1.9&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/UMLLink/article.rst.diff?tr1=1.33&tr2=1.34&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/UMLLink/umldoc-flow.dia.diff?tr1=1.1&tr2=1.2&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/UMLLink/umldoc-refer-flow.dia.diff?tr1=1.1&tr2=1.2&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/UMLLink/umltool-example-mp.dia.diff?tr1=1.1&tr2=1.2&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/UMLLink/umltool-example-uml-linked.dia.diff?tr1=1.1&tr2=1.2&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/UMLLink/umltool-example-uml.dia.diff?tr1=1.1&tr2=1.2&r1=text&r2=text
Patches:
Index: manuscripts/UMLLink/Makefile
diff -u manuscripts/UMLLink/Makefile:1.8 manuscripts/UMLLink/Makefile:1.9
--- manuscripts/UMLLink/Makefile:1.8 Fri Feb 14 09:44:24 2003
+++ manuscripts/UMLLink/Makefile Fri Feb 14 18:08:52 2003
@@ -8,7 +8,7 @@
echo$(DIA_TARGETS) $(RST_TARGETS)
clean:
- rm -f *.gen.* *.~*
+ rm -f *.gen.* *~
.PRECIOUS: %.gen.latex
Index: manuscripts/UMLLink/article.rst
diff -u manuscripts/UMLLink/article.rst:1.33
manuscripts/UMLLink/article.rst:1.34
--- manuscripts/UMLLink/article.rst:1.33 Fri Feb 14 14:39:33 2003
+++ manuscripts/UMLLink/article.rst Fri Feb 14 18:08:52 2003
@@ -9,7 +9,7 @@
.. Alternative title: "Free Software toolchain for bidirectional
linking between UML diagrams and Javadoc"
-.. :Stamp: $Id: article.rst,v 1.33 2003/02/14 19:39:33 humppake Exp $
+.. :Stamp: $Id: article.rst,v 1.34 2003/02/14 23:08:52 humppake Exp $
.. Points for HT people
====================
@@ -453,7 +453,7 @@
allowing the reader to see which alternate spatial views are available for the
current node.
-.. figure:: diagramlinks.gen.eps
+.. figure:: umldoc-linking.gen.eps
:width: 16.9cm
:alternative: *
:label: diagramlinks
@@ -630,30 +630,38 @@
can no longer talk about objects that are not immidiately
visible." [gentner-nielsen96anti-mac-onpage-74]_
-The direct manipulation user interface do not necessarily improve
+Direct manipulation user interface do not necessarily improve
performance: users must learn the meaning of the graphical components,
-graphic presentation could be misleading, graphical presentation could
+graphic presentation could be misleading and graphical presentation could
take excessive screen display space
-[shneiderman83direct-manipulation-onpage-64]_. The direct manipulation
+[shneiderman83direct-manipulation-onpage-64]_. Direct manipulation
interfaces could be also rather slow to use, since in a such interface
-user have to directly manipulate everything. Instead of an executive
-who gives high-level instructions, the user is reduced to an assembly
-line worker who must carry out the same task over and over
-[gentner-nielsen96anti-mac-onpage-74]_. The UML langage has XXX different
-symbols and XXX different connections between them. It is a quite
-challanging for a direct manipulation interface to make all these
-alternatives as easily available as they could be typed within 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.
+user may have to directly manipulate everything. Instead of an
+executive who gives high-level instructions, the user is reduced to an
+assembly line worker who must carry out the same task over and over
+[gentner-nielsen96anti-mac-onpage-74]_. The UML langage has a large
+amount of different symbols and different connection types between
+them [booch-jacobson-rumbaugh98uml-reference-manual]_. It could be
+quite challanging for a direct manipulation interface to make all
+these alternatives as easily available as they could be just typed
+when using lexical description.
.. figure:: umltool-example-uml.gen.eps
:label: umltoolumlsource
- :width: 6cm
+ :width: 4.5cm
Example of UML tool object description.
+
+In our UML tool the describtion of UML diagram is divided in two: into
+a description of all the elements in diagram [ref-umltoolumlsource]_
+and description their graphical layout [ref-umltoolmpsource]_. We
+argue that for a programmer used to Describing existing objects for
+diagram is easily done using our UML tools's lexical description
+language, but the graphical placing of objects is a bit more
+complicated, although, not impossible. We admit that after objects for
+the diagram are selected, the graphical placing for them could be done
+easiest by using direct manipulation.
+
.. figure:: umltool-example-mp.gen.eps
:alternative: *
Index: manuscripts/UMLLink/umldoc-flow.dia
Index: manuscripts/UMLLink/umldoc-refer-flow.dia
Index: manuscripts/UMLLink/umltool-example-mp.dia
Index: manuscripts/UMLLink/umltool-example-uml-linked.dia
Index: manuscripts/UMLLink/umltool-example-uml.dia
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Gzz-commits] manuscripts/UMLLink Makefile article.rst umldoc...,
Asko Soukka <=