| 204 |
|
|
| 205 |
o integrate timestamp into log-output of CPAN's Log::Dispatch!? |
o integrate timestamp into log-output of CPAN's Log::Dispatch!? |
| 206 |
|
|
| 207 |
|
o integrate PEAR::Translation with smarty |
| 208 |
|
o look at http://pear.php.net/package-info.php?pacid=124&release=1.2.3 |
| 209 |
|
o look at http://smarty.php.net |
| 210 |
|
|
| 211 |
|
o send patch for PEAR/Log/file.php |
| 212 |
|
|
| 213 |
|
o make patch for PEAR/XML/RPC.php |
| 214 |
|
|
| 215 |
|
o refactor to PEAR::DB - drivers |
| 216 |
|
o glib/Data/Driver/Proxy.php |
| 217 |
|
o glib/Data/Driver/RPC/Remote.php |
| 218 |
|
|
| 219 |
|
o integrate autogenerated api-documentation for code@netfrag.org |
| 220 |
|
use PhpDocumentor: http://phpdocu.sourceforge.net/ |
| 221 |
|
|
| 222 |
|
o phpLdapBrowser using components from |
| 223 |
|
o PEAR (DB_ldap) |
| 224 |
|
o smarty (maybe some parts for gui rendering) |
| 225 |
|
o phpHtmlLib (abstraction of basic html tags and more highlevel widgets, gui/forms-to-data binding) |
| 226 |
|
o netfrag.org |
| 227 |
|
o yakka as navigation-backend |
| 228 |
|
o on-the-fly generation of navigation-structure |
| 229 |
|
o page-rendering, -dispatching and -layout |
| 230 |
|
o maybe integrate these together to get max. overview over all details |
| 231 |
|
to be able to provide enough abstraction in implementation: |
| 232 |
|
o current dispatcher from yakka (Engine 1.0?, Engine 2.0?) |
| 233 |
|
o dispatchrequest (the generic dispatcher which listens at http://cvs.netfrag.org and http://news.netfrag.org) |
| 234 |
|
o glib/Application/AbstractRequest (a component which grew out of a custom application once, |
| 235 |
|
but was refactored two times after that (<custom-app> -> flib/Site/Request -> org.netfrag.glib/Application/AbstractRequest) |
| 236 |
|
o org.netfrag.glib for tying all that together |
| 237 |
|
|
| 238 |
|
o PEAR::Auth::Kerberos??? |
| 239 |
|
|
| 240 |
|
o nfoweb: "powered by" - page |
| 241 |
|
o lamp: linux, apache, mysql, php |
| 242 |
|
o other daemon software: inn, OpenLDAP, OpenSSH, Kerberos 5, sendmail, amavis, Cyrus |
| 243 |
|
o other software: TWiki, phpWiki, viewcvs, newsportal |
| 244 |
|
o other languages: bash, perl, python, ruby, etc., etc. |
| 245 |
|
o make links... |
| 246 |
|
o include process view??? |
| 247 |
|
o link to "IntegratesWith"-page: PIMs, Offices |
| 248 |
|
|
| 249 |
|
o integrate glib/Data/Driver/Proxy with PEAR::Cache |
| 250 |
|
o use DB::RPC for this! |
| 251 |
|
|
| 252 |
|
o integrate Application::Config with PEAR::Config |
| 253 |
|
|
| 254 |
|
o use PEAR::Tree |
| 255 |
|
o look at http://opensource.visionp.de/modules/project/tree.php |
| 256 |
|
o as base data container for "app::menu", "phpHtmlLib::TreeNav" |
| 257 |
|
|
| 258 |
|
o integrate Data::Encode with I18N - Internationalization??? |
| 259 |
|
|
| 260 |
|
o prepare patches for pear.php.net |
| 261 |
|
o configurable timestamp format for PEAR::Log::file |
| 262 |
|
o no fatal php errors from PEAR::XML::RPC |
| 263 |
|
|
| 264 |
|
x why not PEAR::Config? |
| 265 |
|
* This class allows for parsing and editing of configuration datasources. |
| 266 |
|
* Do not use this class only to read datasources because of the overhead |
| 267 |
|
* it creates to keep track of the configuration structure. |
| 268 |
|
|
| 269 |
|
o Data::Storage and logging via Log::Dispatch - DEEP RECURSION again!!! |
| 270 |
|
|
| 271 |
|
|
| 272 |
|
|
| 273 |
|
|
Parent Directory
| 
Revision Log
| 
Patch
