Summary: | Moz-free Outlook Address Book driver | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | Lionel Elie Mamane <lionel> |
Component: | Database | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | NEW --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | medium | CC: | caolanm, d.ostrovsky, dr, ernstke+freedesktopbugzilla, iplaw67, libreoffice, lionel, michael.meeks, mst.fdo, sbergman, thomas-libo |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Windows (All) | ||
Whiteboard: | EasyHack DifficultyInteresting SkillCpp SkillSQL | ||
i915 platform: | i915 features: | ||
Bug Depends on: | 56904 | ||
Bug Blocks: | 56902 |
Description
Lionel Elie Mamane
2012-11-09 06:11:32 UTC
David Ostrovsky dixit in http://lists.freedesktop.org/archives/libreoffice/2012-November/040889.html > I personally think it is a no go to have two different approaches for > O and OE integration. > As discussed with Fridrich on LO Congress, i took a look at seamonkey > way to handle it. They simple open MAPI.DLL > and use WAB restriction API to access it. Moreover the algorithms and > the data strucures in mozab > (and therefore in mork driver) seems to match 1 to 1 to these api. > So one straightforward way to integrate both O and OE would be to > borrow these 5 files from seamonkey tree and adapt it for our need. As remarked by Michael Meeks in http://lists.freedesktop.org/archives/libreoffice/2012-November/040905.html, following that path, probably better to take that code off *latest* Seamonkey or even better Thunderbird rather than copying the ancient thing we have in-tree. adding LibreOffice developer list as CC to unresolved EasyHacks for better visibility. see e.g. http://nabble.documentfoundation.org/minutes-of-ESC-call-td4076214.html for details So what is the current name for the API? "Windows Address Book (WAB) API" or "Windows Contacts API" apparently they make a new one with every windows release? Adding self to CC if not already on |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.