--- nfo/perl/scripts/outlook2ldap/libs/Torus.README.html 2003/01/19 07:45:05 1.1 +++ nfo/perl/scripts/outlook2ldap/libs/Torus.README.html 2004/11/10 08:19:53 1.4 @@ -1,116 +1,134 @@ - -
--
Torus
--
- Torus is a module to ease migration from Outlook.-
+- + - +
++
+
+NAME
+Torus
++
+
+DESCRIPTION
++ Torus is a module to ease migration from Outlook.+Torus uses CPAN's Win32::OLE to access Microsoft's MAPI locally and - CPAN's Net::LDAP to connect to a remote OpenLDAP-server (slapd).-+ CPAN's Net::LDAP to connect to a remote OpenLDAP-server (slapd).+Access to these storage-implementations is wrapped via Data::Storage. - Core functionality of Torus is currently provided from Data::Transfer::Sync.-+ Core functionality of Torus is currently provided from Data::Transfer::Sync.+We are starting with Contacts/Adresses, will go along with Messages, Calendar-Items and Journaling-Features. - The "rest" should be able to be modeled and implemented on top of this.-+ The "rest" should be able to be modeled and implemented on top of this.+This is more a reference implementation than anything actually useful. ;-) You'll also like to take a look at: - - Kroupware Project: http://kroupware.kde.org - - Outlook Connector Project: http://otlkcon.sourceforge.net - - bynari InsightConnector: http://bynari.net/index.php?id=7--
-NEWS
--
2003-01-18 - initial check-in
--
-REQUIREMENTS
-+ - Kroupware Project: http://kroupware.kde.org + - Outlook Connector Project: http://otlkcon.sourceforge.net + - bynari InsightConnector: http://bynari.net/index.php?id=7++
+
+NEWS
++
+2003-01-18 - initial check-in
++
+
+REQUIREMENTS
+Win32::OLE Net::LDAP Data::Storage Data::Transfer::Sync - ... and all their dependencies--
-AUTHORS / COPYRIGHT
-- The Data::Storage module is Copyright (c) 2002 Andreas Motl. - All rights reserved.-+ ... and all their dependencies++
+
+AUTHORS / COPYRIGHT
++ The Torus module is Copyright (c) 2002-2004 Andreas Motl. + All rights reserved. + Mail to <andreas.motl (at) ilo.de> for improvements and suggestions.+You may distribute it under the terms of either the GNU General Public - License or the Artistic License, as specified in the Perl README file.--
-CONTRIBUTORS
-- Jan Hoffmann <jan@romain-volk.com> - Sebastian Utz <s.utz@tunemedia.de>--
-SUPPORT / WARRANTY
-- Data::Storage is free software. IT COMES WITHOUT WARRANTY OF ANY KIND.--
-BUGS
--
-TODO
-+ License or the Artistic License, as specified in the Perl README file.++
+
+CONTRIBUTORS
++ Jan Hoffmann <janosch (at) netfrag.org> + Sebastian Utz <su (at) rotamente.com>++
+
+SUPPORT / WARRANTY
++ The Torus module is free software. IT COMES WITHOUT WARRANTY OF ANY KIND.++
+
+BUGS
++
+
+TODO-SHOWSTOPPER
++ o sync items from ldap back to outlook++
+
+TODO
+- outlook2ldap - essential modules: - Net::LDAP - Convert::ASN1 / BER1 - Unicode::String - MIME::Base64 o use setup.pm with autoinstall, use ExtUtils::MakeMaker and/or h2xs - x extend logging/debugging-output (logfiles below log/) o enhance mapping through expressions o provide multiple use of same fields o provide mechanism to concatenate fields @@ -127,20 +145,13 @@ o 3.spalte in outlook_ole_fields.csv: für "genSchema.pl" o wenn 2.spalte und/oder 3. leer, dann wird kein mapping gemacht (genSchema sowieso nicht) --> see etc/_future! - +- beliebige outlook-ordner zu ldap-ou's mappen - + fest deklarierte (level 1) - o tief referenzierte (level X) (!!!) (backup->Addressen->XYZ - Addressen) o daten "rückwärts" übertragen! - + bugfix: utf8 o mapping aufbohren (csv -> xml) - integrate "schema"-property _per-field_!!! o have the engine use this o maybe provide cross-checks --> see etc/_future! - o clean-up debugging (levels) - + debugging-level does not work when error occours in Net::LDAP::Entry while adding... - + display MAPI-object as hash o transfer statistics - o zugriff auf outlook ohne rückfrage gewähren? + o zugriff auf outlook (2002) ohne rückfrage gewähren? o v.a. wichtig, wenn integrierter zugriff (z.b. durch outlook-plugin) stattfindet + verwenden _aller_ attribute, die mit einem address-eintrag assoziiert sein können? + mileage (reisekilometer) kommt! @@ -164,10 +175,6 @@ o regex fails: o introduce some "highlevel-splitting" of ldap-addresses o fix problems occoured 2003-01-06/07 @barschwaechter: rules, access to mapi, etc. (see email) - + syncOutlookContacts.pl --mapidump - + provide better workflow for development phase(s) - + configurable debugging - + configurable tracing o do a _true_ sync! (no delete/add) o handle folder-mapping/-creation completely _before_ continuing with single entries o create non-existant and stuff.... @@ -197,23 +204,22 @@ o Outlook (OLE) o Perl (Variables, Objects) o LDAP-Server (Handle) --- - + integration with Data::Storage and Data::Transfer - + thrown away "L:" and "R:" o declarations for/in Data::Transfer::Sync - o split 'syncOutlookContacts.ini' into 'torus.ini' and 'outlook2ldap.ini' - o 'syncOutlookContacts.pl' reads 'outlook2ldap.ini' and runs 'feed.pl' - + Data::Transfer::Sync now utilizes DesignPattern::Object and DesignPattern::Bridge-- + o for Horde: o helper: some kinda "genSchema.pl" - o app: LDAP-Browser--
-IDEAS
-+ o app: LDAP-Browser++ o split 'syncOutlookContacts.ini' into 'torus.ini' and 'outlook2ldap.ini' + o 'syncOutlookContacts.pl' reads 'outlook2ldap.ini' and runs 'feed.pl' + + o check howto handle outlook-profile logon + o mode to transfer all items in bunch + o use a news- (nntp) server to (maybe) mimic journalling-functionality++
+
+IDEAS
+o acl based permissions (use Data::ACL?) o combine Torus::Xyz with Device::Xyz somehow? o assure published stuff contains no client-specific informations (HMI, ...) @@ -242,13 +248,9 @@ o navigate via "cd" through containers, show items/entries via (e.g.) "dump"(?) and stuff... ... the interactive feeling/behaviour is similar to navigating in a filesystem via a commandline-interface (CLI) o sum up "must-have" features of known synchronization-tools for (e.g.) ... - o s25@once - o siemens custom sync (S45Sync.exe?) - o Nokia Communicator - o SyncML (it's not a device from a manufacturer, it's actually a XML-standard) -> sync4j@sourceforge o use news (the nntp-protocol) for journalling-functionality - o have mapping stored inside ldap as well+ o have mapping stored inside ldap as well