[ff-cvs] fenfire/docs/pegboard/functional_futureproof_ap...

[Tuomas J. Lukka]

CVSROOT:        /cvsroot/fenfire
Module name:    fenfire
Branch:         
Changes by:     Tuomas J. Lukka <address@hidden>        03/09/09 03:20:23

Modified files:
        docs/pegboard/functional_futureproof_api--tjl: peg.rst 

Log message:
        Add ripple effects to PEG

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/fenfire/fenfire/docs/pegboard/functional_futureproof_api--tjl/peg.rst.diff?tr1=1.8&tr2=1.9&r1=text&r2=text

Patches:
Index: fenfire/docs/pegboard/functional_futureproof_api--tjl/peg.rst
diff -u fenfire/docs/pegboard/functional_futureproof_api--tjl/peg.rst:1.8 
fenfire/docs/pegboard/functional_futureproof_api--tjl/peg.rst:1.9
--- fenfire/docs/pegboard/functional_futureproof_api--tjl/peg.rst:1.8   Mon Sep 
 8 05:12:43 2003
+++ fenfire/docs/pegboard/functional_futureproof_api--tjl/peg.rst       Tue Sep 
 9 03:20:23 2003
@@ -3,9 +3,9 @@
 =============================================================
 
 :Author:   Tuomas J. Lukka
-:Last-Modified: $Date: 2003/09/08 09:12:43 $
-:Revision: $Revision: 1.8 $
-:Status:   Incomplete
+:Last-Modified: $Date: 2003/09/09 07:20:23 $
+:Revision: $Revision: 1.9 $
+:Status:   Current
 
 Functions and caching are here to stay with us, as they provide
 us with a way to give faster user response times with minimal
@@ -180,8 +180,8 @@
     Metainformation about a function, for example whether it takes a long time 
to run,
     or whether it needs to be run in the OpenGL thread.
 
-Changes
-=======
+Changes to Functions, new API
+=============================
 
 Creating functions
 ------------------
@@ -383,5 +383,24 @@
 what to cache. 
 
 
+Changes to the rest of Fenfire
+==============================
 
+Node content
+------------
+
+The ``NodeContent`` class is something of a remnant.
+It provides the Node content function, so we need to touch
+it here, let's upgrade it properly at the same time.
+
+Move it to its rightful place, ``org.fenfire.structure.Ff``,
+and add ``getContent`` and ``setContent`` methods, given a Fen.
+There's shall also be a PureNodeFunction nested class
+``org.fenfire.structure.Ff.ContentFunction`` which allows the user
+to create an appropriate node function.
+
+Fen
+---
+
+We will not change Fen at this time, except for to remove the ``txtfunc`` 
member.