--- joko/doc/SampleTasks/joko_2003-02.html	2003/02/05 20:43:54	1.11
+++ joko/doc/SampleTasks/joko_2003-02.html	2003/02/05 23:43:55	1.15
@@ -208,13 +208,73 @@
   o look at http://pear.php.net/package-info.php?pacid=124&release=1.2.3
   o look at http://smarty.php.net
   
+o send patch for PEAR/Log/file.php
+
+o make patch for PEAR/XML/RPC.php
+
+o refactor to PEAR::DB - drivers
+  o glib/Data/Driver/Proxy.php
+  o glib/Data/Driver/RPC/Remote.php
+
+o integrate autogenerated api-documentation for code@netfrag.org
+  use PhpDocumentor: http://phpdocu.sourceforge.net/
+
+o phpLdapBrowser using components from
+  o PEAR (DB_ldap)
+  o smarty (maybe some parts for gui rendering)
+  o phpHtmlLib (abstraction of basic html tags and more highlevel widgets, gui/forms-to-data binding)
+  o netfrag.org
+    o yakka as navigation-backend
+      o on-the-fly generation of navigation-structure
+      o page-rendering, -dispatching and -layout
+        o maybe integrate these together to get max. overview over all details 
+           to be able to provide enough abstraction in implementation:
+          o current dispatcher from yakka (Engine 1.0?, Engine 2.0?)
+          o dispatchrequest (the generic dispatcher which listens at http://cvs.netfrag.org and http://news.netfrag.org)
+          o glib/Application/AbstractRequest (a component which grew out of a custom application once,
+             but was refactored two times after that (<custom-app> -> flib/Site/Request -> org.netfrag.glib/Application/AbstractRequest)
+    o org.netfrag.glib for tying all that together
+
+o PEAR::Auth::Kerberos???
+
+o nfoweb: "powered by" - page
+  o lamp: linux, apache, mysql, php
+  o other daemon software: inn, OpenLDAP, OpenSSH, Kerberos 5, sendmail, amavis, Cyrus
+  o other software: TWiki, phpWiki, viewcvs, newsportal
+  o other languages: bash, perl, python, ruby, etc., etc.
+  o make links...
+  o include process view???
+  o link to "IntegratesWith"-page: PIMs, Offices
+
+o integrate glib/Data/Driver/Proxy with PEAR::Cache
+  o use DB::RPC for this!
+  
+o integrate Application::Config with PEAR::Config
+
+o use PEAR::Tree
+  o look at http://opensource.visionp.de/modules/project/tree.php
+  o as base data container for "app::menu", "phpHtmlLib::TreeNav"
+  
+o integrate Data::Encode with I18N - Internationalization???
+
+o prepare patches for pear.php.net
+  o configurable timestamp format for PEAR::Log::file
+  o no fatal php errors from PEAR::XML::RPC
+  
+x why not PEAR::Config?
+  * This class allows for parsing and editing of configuration datasources.
+  * Do not use this class only to read datasources because of the overhead
+  * it creates to keep track of the configuration structure.
+
+o Data::Storage and logging via Log::Dispatch - DEEP RECURSION again!!!
+
 
 
 
 </pre>
 
 <hr/>
-$Id: joko_2003-02.html,v 1.11 2003/02/05 20:43:54 joko Exp $
+$Id: joko_2003-02.html,v 1.15 2003/02/05 23:43:55 joko Exp $
 
 </body>
 </html>