Changes between Version 26 and Version 27 of path:pathView


Ignore:
Timestamp:
02/21/2014 11:47:10 AM (9 years ago)
Author:
michael.perscheid
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • path:pathView

    v26 v27  
    8484
    8585
    86  Menus:: XXX
    87 don't forget right click menu --- different depending on selected item
     86 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.'''
     87 * ''Class name:'' Rename or delete class. Furthermore, add variables, method, and category as well as create accessors.
     88 * ''Variables:'' Add, rename, and delete variable. Also, create accessors.
     89 * ''Method categories:'' Rename category and add method.
     90 * ''Methods:'' Rename and delete method. Add, remove, and inline parameter.
    8891
    89  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.
     92In order to change source code, drag'n'drop the method name and edit the corresponding source code in the opened method widget.
     93
     94 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.
    9095
    9196'''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.
     
    106111[[Image(pathViewMethods.png)]]
    107112
    108  Widget:: Includes the method source code of an opened method from class widget.
     113 Widget:: Includes the method source code of an opened method from class widget. It can be edited as known from standard source code browsers.
    109114
    110115 Line:: A dashed line presents the connection to the corresponding class widget.