Changes between Version 26 and Version 27 of path:pathView

Timestamp:

02/21/2014 11:47:10 AM (10 years ago)

Author:

michael.perscheid

Comment:

--

path:pathView

@@ -84 +84 @@
 
 
- Menus:: XXX
-don't forget right click menu --- different depending on selected item
+ Menus:: By right-clicking on specific entities of a class widget, a menu will open and offer several possibilities to edit and refactor program entities. All operations are done with the help of Squeak's refactoring engine. ''Please note, these changes will also be reflected in source code, immediately.'''
+ * ''Class name:'' Rename or delete class. Furthermore, add variables, method, and category as well as create accessors.
+ * ''Variables:'' Add, rename, and delete variable. Also, create accessors. 
+ * ''Method categories:'' Rename category and add method.
+ * ''Methods:'' Rename and delete method. Add, remove, and inline parameter. 
 
- Line:: There are two kinds of lines between class widgets (based on UML). First, associations represent instance variables and their applied types. For example, in the figure above the spellChecker variable of !CodeSpellChecker includes a Hunspell object. The arrow heads represent the navigation/access directions. Here, Hunspell objects are not able to access !CodeSpellChecker objects through this variable. Second, inheritance relationships between classes are represented by a line with an unfilled triangle at the end. 
+In order to change source code, drag'n'drop the method name and edit the corresponding source code in the opened method widget.
+
+ Line:: There are two kinds of lines between class widgets (based on UML). First, associations represent instance variables and their applied types. For example, in the figure above the spellChecker variable of !CodeSpellChecker includes a Hunspell object. The arrow heads represent the navigation/access directions and the labels show the name and cardinality. Here, Hunspell objects are not able to access !CodeSpellChecker objects through this variable. Second, inheritance relationships between classes are represented by a line with an unfilled triangle at the end. 
 
 '''Please note:''' These lines can also be used for refactoring purposes. For example, click on the arrow head of an inheritance relationship and drop it over another class. 
@@ -106 +111 @@
 [[Image(pathViewMethods.png)]]
 
- Widget:: Includes the method source code of an opened method from class widget. 
+ Widget:: Includes the method source code of an opened method from class widget. It can be edited as known from standard source code browsers.
 
  Line:: A dashed line presents the connection to the corresponding class widget.