43 |
explain why or/and fix. Can be seen when running buoyoing. |
explain why or/and fix. Can be seen when running buoyoing. |
44 |
|
|
45 |
Soon: |
Soon: |
46 |
|
|
47 |
- [tjl] fix .cvsignores: ignoring *.cxx, *.hxx is *NOT* the right thing. |
- [tjl] fix .cvsignores: ignoring *.cxx, *.hxx is *NOT* the right thing. |
48 |
Talk to Tjl. |
Talk to Tjl. |
49 |
- [tjl] Discuss buoy geometry with Tjl; we can't have what it currently is - |
- [tjl] Discuss buoy geometry with Tjl; we can't have what it currently is - |
69 |
- 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 |
70 |
in the tree (as in fenfire) |
in the tree (as in fenfire) |
71 |
|
|
72 |
|
ASAP: |
73 |
|
- [tjl] PEG the controller stuff - it sounds like a really good idea, but |
74 |
|
it needs a real spec and documentation. |
75 |
|
several small issues: |
76 |
|
- it's mouse code, not controller code, thus name should contain "Mouse" |
77 |
|
- it should be in libvob, not fenfire |
78 |
|
- you should start by documenting what it needs to do, then deriving |
79 |
|
the interfaces from that |
80 |
|
- needs documentation |
81 |
|
- can it allow, e.g. several different drags based on what |
82 |
|
object was clicked, i.e. who can route drags to the object |
83 |
|
that was clicked and how? |
84 |
|
|
85 |
============= |
============= |
86 |
Past: |
Past: |
87 |
============= |
============= |