[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[ff-cvs] journals mudyc
From: |
Matti Katila |
Subject: |
[ff-cvs] journals mudyc |
Date: |
Mon, 25 Aug 2003 21:05:01 -0400 |
CVSROOT: /cvsroot/fenfire
Module name: journals
Branch:
Changes by: Matti Katila <address@hidden> 03/08/25 21:05:01
Modified files:
. : mudyc
Log message:
weekend
CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/fenfire/journals/mudyc.diff?tr1=1.104&tr2=1.105&r1=text&r2=text
Patches:
Index: journals/mudyc
diff -u journals/mudyc:1.104 journals/mudyc:1.105
--- journals/mudyc:1.104 Mon Aug 25 03:35:51 2003
+++ journals/mudyc Mon Aug 25 21:05:01 2003
@@ -57,11 +57,6 @@
- rename methods: flush() -> flushAll() tms
3) DOCUMENT!!!
-2003-07-XX:
- - [jvk] start experiment framework.
-
-2003-07-XX:
- - write a test case for rm_1AA bug.
2003-07-XX:
- move fenfire test code to libvob, move libvob tests to their correct
places
@@ -76,6 +71,8 @@
- [tjl] Go through tests in libvob that are marked to fail in awt or gl
and see which are bugs. Fix them.
+- [tjl] fix libvob test failure
+
- [tjl] ps/pdf import
- test error scenarios very carefully with differently
broken ps/pdf files
@@ -108,25 +105,29 @@
Support for calling the vob to create the coordsys with the grayed-out
data.
4. document all data members carefully
-- [tjl] Think about what happens in the libvob & fenpdf event logic when the
user
- 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
+- get rid of ToDo part in my journal
=============
Past:
=============
+
+2003-08-24:
+ - [tjl] Clean up buoymanager.findTopmostMainNode: it's really
+ sloppy code. [0.4h]
+ - [tjl] Think about what happens in the libvob & fenpdf event logic
+ when the user presses one button down, then another -- it's
+ pretty fragile. How can we make it work right in all cases?
+ - made someone to stole the events [2h]
+ - commits [1h]
+
+2003-08-25:
+ - SelectListVob and SelectItemVob [2h]
+ - lot's of commits [2h]
+ - cleaning [1h]
+ - demo.py quiting.
+
+2003-08-23/24:
+ - lines, cursor etc..
2003-08-22:
- jni conversion of float to float vector.
- [ff-cvs] journals mudyc, Matti Katila, 2003/08/18
- [ff-cvs] journals mudyc, Tuomas J. Lukka, 2003/08/25
- [ff-cvs] journals mudyc, Tuomas J. Lukka, 2003/08/25
- [ff-cvs] journals mudyc,
Matti Katila <=
- [ff-cvs] journals mudyc, Tuomas J. Lukka, 2003/08/26
- [ff-cvs] journals mudyc, Matti Katila, 2003/08/26
- [ff-cvs] journals mudyc, Matti Katila, 2003/08/28
- [ff-cvs] journals mudyc, Matti Katila, 2003/08/29