*** empty log message ***

diff --git a/report.txt b/report.txt
index fbab898b73941c3daf902fece6abd14aca378bcd..3711ef97b85a00458102d09706a403c7e0ccb2dd 100644 (file)
--- a/report.txt
+++ b/report.txt
@@ -36,15 +36,13 @@ The schedule that was made initially reflected the time required to implement th
 As we earlier realized, some implementation of the functional classes was required to see what features the graphical representations would need.
 
 As an indication of which classes that were most difficult to implement, the version numbering of the Concurrent Versions System can be compared. In that respect, the most frequently altered classes were MooTrackView, Moosique and MooToolbar.
-
 [...]
 
-Strictly graphical classes [...]
 Implementing the strictly graphical classes has at some points been both tricky, and boring. Probably beacuse of the programmers lack of experience of the Java Swing library. Huge amounts of time has been spended with trial and error. The Java Swing library offers rather inflexible layout managers, which sometimes can cause problems. This feature makes it real difficult to get a feeling of how the window actual will look onscreen, while implementing the classes.
-In retrospect it maybe should have been better if we chose to work only with the Java AWT library.
+In retrospect it maybe would have been better if we chose to work only with the Java AWT library (see section [Problems]).
 ------------------------------
 2.5 Testing
-Är det nån som har testat nåt dårå?!?
+See section [Implemention and Problems]
 ------------------------------
 2.6 Major Decisions