2 |
|
|
3 |
Subject: One more split of VobScene |
Subject: One more split of VobScene |
4 |
|
|
5 |
Currently, a VobScene consists of |
Currently, a VobScene consists of |
6 |
1) VobMap: the binding between coordinate systems indices and vobs, |
1) VobMap: the binding between coordinate systems indices and vobs, |
7 |
2) VobCoorder: the coordinate systems and their keys |
2) VobCoorder: the coordinate systems and their keys |
8 |
|
|
9 |
I'm suggesting splitting this one more time: |
I'm suggesting splitting this one more time: |
10 |
1) VobMap: the binding between coordinate systems indices and vobs, |
1) VobMap: the binding between coordinate systems indices and vobs, |
11 |
2) VobCoorder: the coordinate systems |
2) VobCoorder: the coordinate systems |
12 |
3) VobMatcher: the binding between coordinate system indices and keys. |
3) VobMatcher: the binding between coordinate system indices and keys. |
13 |
|
|
14 |
GraphicsAPI calls creating vobscenes would accept a parameter for VobMatcher for now, |
GraphicsAPI calls creating vobscenes would accept a parameter for VobMatcher for now, |
15 |
or alternatively it would not yet be a final member. |
or alternatively it would not yet be a final member. |
16 |
|
|
17 |
|
(Benja:) |
18 |
|
Sounds ok. |
19 |
|
|
20 |
The point is to free the vob matching functionality for extending and experiments; |
The point is to free the vob matching functionality for extending and experiments; |
21 |
we want hierarchical things, things depending not only on identity but clicks etc. |
we want hierarchical things, things depending not only on identity but clicks etc. |
22 |
|
|
23 |
|
(Benja:) |
24 |
|
Not sure we can make it general enough to encompass all the experiments |
25 |
|
we'd like to do... |
26 |
|
|
27 |
The VobMatcher API would be |
The VobMatcher API would be |
28 |
|
|
29 |
public interface VobMatcher { |
public interface VobMatcher { |
41 |
Now, the important point is that particular vobmatchers can add other add methods, e.g. |
Now, the important point is that particular vobmatchers can add other add methods, e.g. |
42 |
|
|
43 |
void add(int cs, Object key, String subkey) |
void add(int cs, Object key, String subkey) |
44 |
|
|
45 |
|
(Benja:) |
46 |
|
One thing I would like to do is span interpolation similar to the old text |
47 |
|
interpolation stuff from 0.6. So, |
48 |
|
|
49 |
|
void add(int cs, Object key, int start, int n) |
50 |
|
|
51 |
|
But that needs help from the coorder or somewhere to work right, |
52 |
|
because it may need to split the spans while interpolating... |
53 |
|
|
54 |
|
Can that work with this scheme?` |
55 |
|
|
56 |
|
|
57 |
At the same time, add to VobMap a new method |
At the same time, add to VobMap a new method |
60 |
|
|
61 |
without a coordinate system, for non-coorded vobs. |
without a coordinate system, for non-coorded vobs. |
62 |
|
|
63 |
|
(Benja:) |
64 |
|
I'd prefer a longer (more descriptive) method name as this won't be used |
65 |
|
as often. |
66 |
|
|
67 |
Tuomas |
Tuomas |