[binarycloud-cvs-commit] cvs: r2 / TODO

[alex <bin...@li...>]

alex		Wed Jul 25 14:12:19 2001 EDT

  Modified files:              
    /r2	TODO 
  Log:
  Removed PEAR Integration tasks from the TODO.
  
  
Index: r2/TODO
diff -u r2/TODO:1.14 r2/TODO:1.15
--- r2/TODO:1.14	Tue Jul 17 21:10:59 2001
+++ r2/TODO	Wed Jul 25 14:12:19 2001
@@ -1,5 +1,5 @@
 # cvs:
-# $Id: TODO,v 1.14 2001/07/18 04:10:59 alex Exp $
+# $Id: TODO,v 1.15 2001/07/25 21:12:19 alex Exp $
 
 r2 build:
 -------------------------------
@@ -21,14 +21,8 @@
 should be dumb about the data that is coming in - no global scope. the difference between a
 master template and a layout template should be semantic, not functional.
 
--get a simple process down for pear installation, test imports of PEAR in Init.
-
--test ext/ imports in general
-
 -make default module association work for master templates. this should be a function of Page,
 not the subject template. likely a $Page->defaults['unique_id'].
-
--once PEAR imports are functional, remove PEAR_Error.php from base/core/
 
 -putz with bc_edit a bit more, check it into cvs.