Usability issues of diagrams

by Bogdan SZANTO - GSoC 2008


   Weekly report -- Week 9 & 10




 1. Work achieved since the last report

Now that Luis is back he started reviewing the first 3 features and with the feedback he provided I started modifying the code in order to improve it. I have also returned to Romania for the month of August so now I can spend more time coding.


   1.    F1 - Integration of classes between diagrams

        [http://argouml.tigris.org/issues/show_bug.cgi?id=5138]

Originally, after implementing this, I refactored the code in order to use a drop(Object droppedObject, Point location), declared in UMLDiagram, that each diagram type had to overwrite in order to use drop features (DnD and Add to diagram). Since this was only implemented in UMLSequenceDiagram (the 2nd version), DnD was inhibited for all other diagrams. After having the "thumbs up" from Luis, I implemented this method in every diagram type. Both Add to diagram and DnD rely on this method, so there is no code duplication.


   3.    F3 - Class modifications on the diagram

        [http://argouml.tigris.org/issues/show_bug.cgi?id=5140]

Implementing the first part of this issue (cycle visibility of attributes and operations) was based on a calculation of the word/sign offset (the offset is the distance from the beginning of the Fig until the end of the visibility word/sign) that was done rather rudimentary. A more interesting way is to allow every notation type to set this offset (a value of 0 means turned off). Font size and zoom factor should also be taken into account. I will refactor/rewrite the code to match this.

*4.** *

*4.** *


 2. Impressions

With Luis back again, the work should be OK again. I can't say I lost time because of this, but rather because of me leaving France (for 6 months) and having to move all my stuff to friends and because I had to work a little bit more that usual at the metro. We should have no problem on picking up the pace and going back on schedule again.


 4. Work to complete during this week

      1. Rewrite some part of F3 to improve the code.
      2. Start work on F4.

--
Bogdan SZANTO
-----------------------------------------------
Impossible is nothing ~ Nothing is impossible !
-----------------------------------------------

Reply via email to