3 |
=================================== |
=================================== |
4 |
|
|
5 |
The Vob templates were not an easy design: |
The Vob templates were not an easy design: |
6 |
the previous approach in ``gfx/librenderables/renderables.py`` was |
the previous approach in Gzz's ``gfx/librenderables/renderables.py`` was |
7 |
not at all optimal, due to the syntactic complexities. |
not at all optimal, due to the syntactic complexities and the single point |
8 |
|
of generation. |
9 |
|
|
10 |
The ideal requirements for the template design were: |
The ideal requirements for the template design were: |
11 |
|
|
12 |
- Pure C++ templates and possibly some preprocessor macros |
- Pure C++ templates (possibly some preprocessor macros) |
13 |
|
|
14 |
- Author of Vob type should not have to type a list of assignments |
- Author of Vob type should not have to type a list of assignments |
15 |
to the members - at most a single list of parameter names. |
to the members - at most a single list of parameter names. |
16 |
|
|
17 |
- Should be able to avoid the extra assignments and initialize |
- Should be able to avoid the extra assignments and initialize |
18 |
vob members directly. |
vob members directly from the parameters passed from Java. |
19 |
|
|
20 |
To my surprise, there was a solution. The basic Vob definition |
To my surprise, there was a solution. The basic Vob definition |
21 |
would be :: |
would be :: |