| 208 |
o look at http://pear.php.net/package-info.php?pacid=124&release=1.2.3 |
o look at http://pear.php.net/package-info.php?pacid=124&release=1.2.3 |
| 209 |
o look at http://smarty.php.net |
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 |
|
|
| 241 |
|
|