/[fenfire]/journals/mudyc
ViewVC logotype

Diff of /journals/mudyc

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.104 by tjl, Mon Aug 25 07:35:51 2003 UTC revision 1.105 by mudyc, Tue Aug 26 01:05:01 2003 UTC
# Line 57  Soon: Line 57  Soon:
57              - rename methods: flush() -> flushAll() tms              - rename methods: flush() -> flushAll() tms
58          3) DOCUMENT!!!          3) DOCUMENT!!!
59    
 2003-07-XX:  
     - [jvk] start experiment framework.  
   
 2003-07-XX:  
     - write a test case for rm_1AA bug.  
60    
61  2003-07-XX:  2003-07-XX:
62      - move fenfire test code to libvob, move libvob tests to their correct places      - move fenfire test code to libvob, move libvob tests to their correct places
# Line 76  Soon: Line 71  Soon:
71  - [tjl] Go through tests in libvob that are marked to fail in awt or gl  - [tjl] Go through tests in libvob that are marked to fail in awt or gl
72    and see which are bugs. Fix them.    and see which are bugs. Fix them.
73    
74    - [tjl] fix libvob test failure
75    
76  - [tjl] ps/pdf import  - [tjl] ps/pdf import
77      - test error scenarios very carefully with differently      - test error scenarios very carefully with differently
78        broken ps/pdf files        broken ps/pdf files
# Line 108  Soon: Line 105  Soon:
105         Support for calling the vob to create the coordsys with the grayed-out data.         Support for calling the vob to create the coordsys with the grayed-out data.
106      4. document all data members carefully      4. document all data members carefully
107    
108  - [tjl] Think about what happens in the libvob & fenpdf event logic when the user  - get rid of ToDo part in my journal
   presses one button down, then another -- it's pretty fragile. How can we  
   make it work right in all cases?  
   
 - [tjl] Clean up buoymanager.findTopmostMainNode: it's really sloppy code.  
     1) why are you an array of java arrays? Use one and write that to hits  
     2) Why do you first collect all hits, then find the topmost (note: not  
        "the most up", it's *topmost*)? Use a single loop that finds the  
        hit.  
     3) ((I did this already, but take note)) When inserting such a long piece  
        of code, use a method.  
     4) Don't use the min constant -99999... - rather use the None value provided  
        by python for the initial value  
   
 - [tjl] fix libvob test failure  
109    
110  =============  =============
111  Past:  Past:
112  =============  =============
113    
114    2003-08-24:
115        - [tjl] Clean up buoymanager.findTopmostMainNode: it's really
116          sloppy code. [0.4h]
117        - [tjl] Think about what happens in the libvob & fenpdf event logic
118          when the user presses one button down, then another -- it's
119          pretty fragile. How can we make it work right in all cases?
120            - made someone to stole the events [2h]
121        - commits [1h]
122    
123    2003-08-25:
124        - SelectListVob and SelectItemVob [2h]
125        - lot's of commits [2h]
126        - cleaning [1h]
127        - demo.py quiting.
128    
129    2003-08-23/24:
130        - lines, cursor etc..
131    
132  2003-08-22:  2003-08-22:
133      - jni conversion of float to float vector.      - jni conversion of float to float vector.
134      - liblines      - liblines

Legend:
Removed from v.1.104  
changed lines
  Added in v.1.105

savannah-hackers-public@gnu.org
ViewVC Help
Powered by ViewVC 1.1.26