190 |
+ speed up tests: currently too much execfile().. could |
+ speed up tests: currently too much execfile().. could |
191 |
pre-compile and exec compiled in the same globals(). |
pre-compile and exec compiled in the same globals(). |
192 |
humppake: |
humppake: |
193 |
- If OvalBgVob is used as Bg vob it should not use colored |
- write about representing mind map in ZZ |
194 |
sectors: |
- how different dimensions would be used |
195 |
- OvalBgVob to use colored stripes also with AWT |
- how n:m associations are handled |
196 |
- SectorVob for LollipopCV, 360dgrs is a CircleVob :) |
- rethink View interfaces |
197 |
- SquareVob, square with colored sectors |
- PEG1018 - ViewTool |
198 |
- should these be named ColoredXXXVob? |
- peg about stretching and mounting connections |
199 |
- think about renderables for OpenGL sides, with them |
- rename solids into cellColors or something... |
200 |
dicing and using with distorted coords would be possible :) |
- Vobs |
201 |
|
- ColoredSectorVob for LollipopCV, 360dgrs is a CircleVob :) |
202 |
|
- ColoredSquareVob, square with colored sectors |
203 |
|
- think, how "solids" could be rendered using renderables |
204 |
|
in circular forms, specially stripes in oval could be |
205 |
|
difficult |
206 |
- opengl demo, which uses view (made in python) |
- opengl demo, which uses view (made in python) |
207 |
- rethink interfaces between PlainVanishing and VobScene |
- new umltool and paper about it |
|
eg. correct implementation of LollipopCellView needs |
|
|
to affect connections' coordsys (through box?) |
|
|
- first have to understand current interfaces -> UML |
|
|
- new PEG, new UMLs would be good |
|
|
- also stretching relates this |
|
|
- more about PEG1018 - generalizing VobVanishingClient |
|
208 |
- BallCellView (text inside the ball) |
- BallCellView (text inside the ball) |
209 |
- we don't want more complicated line breaker, uses cell's |
- we don't want more complicated line breaker, uses cell's |
210 |
content will be in square |
content will be in square |
211 |
|
+ create gfx/libirregu from irregu4.py and make effects.py to use |
212 |
|
new libirregu... ask jvk for more. |
213 |
+ fix the way nonlinearity of coordsys is handled. |
+ fix the way nonlinearity of coordsys is handled. |
214 |
Needs a slightly better approach, with also |
Needs a slightly better approach, with also |
215 |
direction of nonlinearity taken into account. |
direction of nonlinearity taken into account. |