[ff-cvs] journals mudyc tjl

[Tuomas J. Lukka]

CVSROOT:        /cvsroot/fenfire
Module name:    journals
Branch:         
Changes by:     Tuomas J. Lukka <address@hidden>        03/08/23 06:11:35

Modified files:
        .              : mudyc tjl 

Log message:
        more

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/fenfire/journals/mudyc.diff?tr1=1.100&tr2=1.101&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/fenfire/journals/tjl.diff?tr1=1.141&tr2=1.142&r1=text&r2=text

Patches:
Index: journals/mudyc
diff -u journals/mudyc:1.100 journals/mudyc:1.101
--- journals/mudyc:1.100        Fri Aug 22 10:06:21 2003
+++ journals/mudyc      Sat Aug 23 06:11:35 2003
@@ -79,10 +79,21 @@
       broken ps/pdf files
       in actual .test cases
 
-- [tjl] ASAP: Document *WHAT* the objects in fenpdfcontext actually are
-  supposed to represent. What is each one's task and who does it cooperate 
with.
-  If possible, think of better names for the classes (ContextState seems
-  really bizarre - what *IS* it?)
+- [tjl] 
+    - [mudyc] libvob/include/vob/vobs/Lines.hxx why coords1.transform 
+      doesn't affect when running vob/demo/lines.py?
+      libvob/src/lines/Lines.cxx -> could you check the gl settings (after 
+      coordinates are set correctly..) can 1d texture be made?
+    - I don't understand the second part at all.
+      When adding stuff to journal, PLEASE MAKE IT REALLY EXPLICIT AND CLEAR.
+
+- [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.
 
 =============
 Past:
Index: journals/tjl
diff -u journals/tjl:1.141 journals/tjl:1.142
--- journals/tjl:1.141  Fri Aug 22 10:06:21 2003
+++ journals/tjl        Sat Aug 23 06:11:35 2003
@@ -160,16 +160,42 @@
   * commandline parameters
   * keybindingd (including mouse)
 
-- encapsulation of paper &c appearances to a single set of classes in fenpdf!
 
-- [mudyc] libvob/include/vob/vobs/Lines.hxx why coords1.transform 
-  doesn't affect when running vob/demo/lines.py?
-  libvob/src/lines/Lines.cxx -> could you check the gl settings (after 
-  coordinates are set correctly..) can 1d texture be made?
+- Ctrl-I, Ctrl-B working
+
 
 =============
 Past:
 =============
+
+2003-08-23: 
+    - refactoring buoymanager
+       - req. mudyc to comment code
+
+2003-08-22: 
+    - refactoring
+    - teaching mudyc
+    - [mudyc] libvob/include/vob/vobs/Lines.hxx why coords1.transform 
+      doesn't affect when running vob/demo/lines.py?
+      libvob/src/lines/Lines.cxx -> could you check the gl settings (after 
+      coordinates are set correctly..) can 1d texture be made?
+       - discussed, explained coordsys problem
+       - I don't understand the second part, req'd to be more specific
+
+2003-08-21: 
+    - refactoring
+    - getting to know arch (tla).
+       - seems like a good tool. Using it for local changes before committing 
to cvs.
+
+2003-08-20: 
+    - refactoring
+       - start separating org.fenfire.fenpdf.appearance
+           - encapsulation of paper &c appearances to a single set of classes 
in fenpdf!
+           - try using views immutably
+
+2003-08-19: 
+    - Using FenPDF
+    - Resting, after the excitement on the weekend and monday
 
 2003-08-18: JKL
     - start FenPDF.rst