237 |
|
|
238 |
o PEAR::Auth::Kerberos??? |
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 |
|
|
274 |
</pre> |
</pre> |