[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[ff-cvs] libvob/doc/pegboard/animation_api--mudyc peg.rst

From: Matti Katila
Subject: [ff-cvs] libvob/doc/pegboard/animation_api--mudyc peg.rst
Date: Fri, 24 Oct 2003 03:17:10 -0400

CVSROOT:        /cvsroot/libvob
Module name:    libvob
Changes by:     Matti Katila <address@hidden>   03/10/24 03:17:10

Modified files:
        doc/pegboard/animation_api--mudyc: peg.rst 

Log message:


Index: libvob/doc/pegboard/animation_api--mudyc/peg.rst
diff -u libvob/doc/pegboard/animation_api--mudyc/peg.rst:1.10 
--- libvob/doc/pegboard/animation_api--mudyc/peg.rst:1.10       Fri Oct 24 
03:09:25 2003
+++ libvob/doc/pegboard/animation_api--mudyc/peg.rst    Fri Oct 24 03:17:10 2003
@@ -5,8 +5,8 @@
 :Authors:  mudyc
 :Date-Created: 2003-09-27
-:Last-Modified: $Date: 2003/10/24 07:09:25 $
-:Revision: $Revision: 1.10 $
+:Last-Modified: $Date: 2003/10/24 07:17:10 $
+:Revision: $Revision: 1.11 $
 :Status:   Current
 :Stakeholders: mudyc, tjl, benja
 :Scope:    Minor
@@ -83,7 +83,7 @@
 We heavily use the ``demo framework`` in our applications, see
 vob.putil.demo. ``Demo framework`` basicly is libvob using one window.
-One window is obivious to get more testing of irregular edge.
+One window is obivious to get more testing with irregular edge.
 Animation seen in window is made with one or two VobScenes.
 Although, VobScene is very sticky with *one* window we have no interfaces
@@ -91,7 +91,7 @@
 This PEG tries to be a solution to provide an interface
 for handling VobScenes per *one* window instead of
-current UpdateManager which handles multiple windows.
+current UpdateManager which handles multiple windows and timing.
 Currently we use AbstactUpdateManager directly from programs.
 This is bad thing 'cause of it can prevent proper animation, e.g., 

reply via email to

[Prev in Thread] Current Thread [Next in Thread]