83 |
|
|
84 |
We heavily use the ``demo framework`` in our applications, see |
We heavily use the ``demo framework`` in our applications, see |
85 |
vob.putil.demo. ``Demo framework`` basicly is libvob using one window. |
vob.putil.demo. ``Demo framework`` basicly is libvob using one window. |
86 |
One window is obivious to get more testing of irregular edge. |
One window is obivious to get more testing with irregular edge. |
87 |
|
|
88 |
Animation seen in window is made with one or two VobScenes. |
Animation seen in window is made with one or two VobScenes. |
89 |
Although, VobScene is very sticky with *one* window we have no interfaces |
Although, VobScene is very sticky with *one* window we have no interfaces |
91 |
|
|
92 |
This PEG tries to be a solution to provide an interface |
This PEG tries to be a solution to provide an interface |
93 |
for handling VobScenes per *one* window instead of |
for handling VobScenes per *one* window instead of |
94 |
current UpdateManager which handles multiple windows. |
current UpdateManager which handles multiple windows and timing. |
95 |
|
|
96 |
Currently we use AbstactUpdateManager directly from programs. |
Currently we use AbstactUpdateManager directly from programs. |
97 |
This is bad thing 'cause of it can prevent proper animation, e.g., |
This is bad thing 'cause of it can prevent proper animation, e.g., |