24 |
Not sure we can make it general enough to encompass all the experiments |
Not sure we can make it general enough to encompass all the experiments |
25 |
we'd like to do... |
we'd like to do... |
26 |
|
|
27 |
|
(Tjl:) |
28 |
|
Of course not; OTOH, it's better than what we have now. Going to the right |
29 |
|
direction. |
30 |
|
|
31 |
The VobMatcher API would be |
The VobMatcher API would be |
32 |
|
|
33 |
public interface VobMatcher { |
public interface VobMatcher { |
57 |
|
|
58 |
Can that work with this scheme?` |
Can that work with this scheme?` |
59 |
|
|
60 |
|
(Tjl:) |
61 |
|
I don't see why it couldn't. All we basically need is a call to |
62 |
|
quash a renderable (don't show while animating) and replacing it with |
63 |
|
split pieces. |
64 |
|
|
65 |
|
|
66 |
At the same time, add to VobMap a new method |
At the same time, add to VobPlacer a new method |
67 |
|
|
68 |
put(Vob v) |
put(Vob v) |
69 |
|
|
73 |
I'd prefer a longer (more descriptive) method name as this won't be used |
I'd prefer a longer (more descriptive) method name as this won't be used |
74 |
as often. |
as often. |
75 |
|
|
76 |
|
(Tjl:) |
77 |
|
Consistency: we now have |
78 |
|
void put(Vob vob, int coordsys); |
79 |
|
void put(Vob vob, int coordsys1, int coordsys2); |
80 |
|
so I think put(Vob v) would be best. Sorry, I first said |
81 |
|
VobMap, I meant of course VobPlacer. |
82 |
|
|
83 |
Tuomas |
Tuomas |