--- joko/doc/SampleTasks/joko_2003-02.html 2003/02/05 22:43:56 1.13 +++ joko/doc/SampleTasks/joko_2003-02.html 2003/02/26 16:56:01 1.67 @@ -1,248 +1,891 @@ - -
-- - -- -
- -o flib: - o include & boot - o include-paths - o configKey (servername) => servername/appname - o make glib - o RPC::Remote: just can talk to single rpc-server!!!! -o app-cleanup: - o replace ../img/ through img/ globally (in all files found) - o grep -ri "../img" | modify.pl --regex=s/\.\.\/img/img/g [--in-type=filelist] - o refactor replace_cvs.pl to: - finder.pl -R --regex=/CVS/Root . | modify.pl --regex=s/:pserver:/:ext:/ [--in-type=filelist] - o is it possible to actually parse settings && arguments (not just "options") using Getopt::Long?? - o else: look at CPAN more detailed or make a CliCmd::Option + CliCmd::Argument = CliCmd::Setting!! - O refactor Getopt::Simple to Getopt::Easy and add features!? a) argument/option-mechanism b) restrict option-mech - symbol: O=Ongoing - c use Getopt::Auto??? - x make Getopt::Easy!!! - - -o 0. Oef::Request -> ... -o 1. CliCmd::Setting -> Oef::Request -> [hibernate] -> [wakup] -> Oef::Engine -> Oef::>Task -> Oef::Response - o need to freeze a Oef::Request -o 2. CliCmd::Setting -> Oef::Request -> Oef::Engine -> Oef::Task -> [hibernate] -> [wakup] -> Oef::Response - o need to freeze a Oef::Engine - -o Oef::Base bases on DesignPattern::Object and DesignPattern::Bridge - -o refactor DesignPattern::Object::Logger to Oef::Base::Logger - -o use phpHtmlLib - widgets in a wiki (yakka!) - -o rename Data::Storage::Handler::NetLDAP to Data::Storage::Handler::LDAP - -o register: data-storage.[perl.]netfrag.org - -o look at ''!!! - o better use 'utf-8' to achieve full i18n? - -o add descriptive words (undelete, etc.) and references to similar projects to mini-howto_trashcan-under-linux_libtrash.html - -o proarc - professional document archiving, indexing, distributing and publishing - o archiver - archive --reference|meta|content --check-descents=*.txt--type=file|document - o indexer - index , use mnoGoSearch's indexer - o manager - o build sets of data - o make distribution lists - o manage global settings (base-paths/-urls, etc.) - o edit object details (public-url, acls, etc.) - o edit global and/or per-object metadata - o to-be-published (@) - o to-be-indexed - o build manager-rules on top of that - o distributor - o prepare/distribute sets of data - o publisher - o publish data to given url@server - a) prepared machine-readable sets for distribution - b) human-readable material (e.g.: generated indexes, overviews, details, descent-documents) - o add collaboration on top of that! - o (technical) annotations, pbb, etc. - o what is already there? - x found: ProArc, OpenArc - but nothing seems to be truly *open*! - -o Gtk Rules | phpRules - an abstract rule chain editor - o modes: dispatchmail, dispatchrequest, ipchains? - o look at Outlook 2000, Ximian Evolution, Horde - -o iSerienbrief (mac & win32) - -o freier xml-editor für win32? (nicht auf msxml3 basierend?) - -o Data::Storage - - overview - - just gives you a handle to a preconfigured data-source. - - it's a meta-module on our way to unified data access. - - details - It also lets you add additional methods to this handle from - specified Perl-modules acting as "plugins". - It's delivered with "Handlers" ready for talking to rdbms-databases, - flat-file databases (csv, etc.), structured files (INPADOC, XML) and - oo-rdbms-mappers (orms) - in our case "Tangram" (from CPAN). - -o Resources, Ontologies, Information Delivery - o RSS, RDF, RDFS - -o modifier.pl - o soap <-> rpc-xml - o Tangram-Schema <-> RDF Schema (RDFS) - -o use nntp//rss!!! - -o cvssync - o option AUTOCOMMIT - o option AUTOADD - o mode GUI - -o sieve & XML??? - -o cvs & kerberos??? - -o enhance Mail::Audit::Dispatch - x recieveMail -> dispatchmail & Mail::Audit::Dispatch - o Mail::Audit::Dispatch::Folder::Mbox (by joko, the main part of the former recieveMail, just uses Mail::Audit) - o Mail::Audit::Dispatch::Spool (by joko, a little part of the former recieveMail, just uses Mail::Audit) - x Mail::Audit::Dispatch::Newsgate (by joko, uses Net::NNTP) - o Mail::Audit::Dispatch::Folder::Cyrus1 (by jonen, acts as sendmail MDA instead of /usr/sbin/cyrdeliver, but re-dispatches to it again after resolving addresses against an arbitrary data source, see 'Data::Map' stuff....) - o Mail::Audit::Dispatch::Faxgate (by janosch, uses /usr/bin/sendfax; still inside 'mail-handler', tbr) - o Mail::Audit::Dispatch::Smsgate (by janosch, uses /usr/bin/yaps; still inside 'mail-handler', tbr) - o could also use /usr/bin/smssend or some module from CPAN - o Mail::Audit::Dispatch::Response (by joko, notifies sender that his/her mail was processed by arbitrary system) - o send autoresponse with subject: "Your bug-request was filed." when mailing to bugs@netfrag.org (done by gateway@netfrag.org) - o actually do file the message at nfo.support.queue (done by gateway@netfrag.org) - o maybe cc: to or integrate with tutos or other ticketing system (bugzilla)???) - o this should be the basic functionality needed to implement known features as "autoresponder" or "vacation" on top of this - -o write about: - o path-structure inside dev-cvs (->bareface, ->janosch) - o path-structure inside sysadmin-cvs (hosts, skels) (->jonen) - o path-structure at web/pub (->jonen) - -o enhance newsportal - o features for ArticleViewer: - o embedded images - o MIME capability - o HTML frameset capability - o show in external window - o convert to HTML tables!? - -o a StartingPoint: TUTOS Project/Product Overview - -o generate some documentation for flib and glib automagically - o use JavaDoc? see ->phpHtmlLib - o use phpDoc? see ->Xyz - -o yakka: - o SeperationOfWikiCoreFeatures - o revisioning - o EnhancementOfCoreFeatures - o object oriented linking/referencing - o reference maintenance capabilities (copy, move, unlink) (+clone, +deep_copy) - o reference structuring (make set, add more metadata) - o use RDF and/or RDFS? - o look at RDFWiki.... - o EnhancementOfFrontend - o ReIntegrationOfWikiCoreFeatures - -o "outsource" mysql from quepasa.netfrag.org to h1.service.netfrag.org - -o establish slapd on h1.service.netfrag.org - -o faxabruf für w2hfax (sendfax -d -p) - o konvertiere empfanges dokument von ps nach pdf, tiff? - -o look at bonsai? - -o scripts from janosch - -o php-4.3.0??? - -o emacs? - -o check if backend-logging still works!? - -o pear-1.0? - -o patch PEAR::XML::RPC - o look at http://cvs.php.net/co.php/pear/XML_RPC/RPC.php - o look at http://marc.theaimsgroup.com/?l=pear-dev&m=103578377822397&w=2 - o provide better patch introducing new error-codes and messages for "local errors": - o "could not connect to remote server, failed to open socket" - o "could not send data, but socket is open" - -o python in php: integrate python-library from w2hfax!? - -o task list - start apache1 (click) - start mysql (type net start mysql) - start internet explorer (click) - start explorer (press win-key & e) - navigate to target - open in ultraedit - -o php-enhancements!? - o mixin inheritance for php? - o manipulating the symbol table? - -o install PEAR::Log-1.5.3 - o re-integrate (and maybe submit) patches to have timestamp formatted in a different way - -o integrate timestamp into log-output of CPAN's Log::Dispatch!? - -o integrate PEAR::Translation with smarty - 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 ( -> flib/Site/Request -> org.netfrag.glib/Application/AbstractRequest) - o org.netfrag.glib for tying all that together - -o PEAR::Auth::Kerberos??? - - - -