Am 09.11.2012 07:22, schrieb Lionel Elie Mamane:
>>All these solutions would not require a "new" driver, we just generate
>>the correct ADO connect URL and hand it off to the ADO driver (as we
>>do for .mdb / .accdb files).
>>As to accessing Outlook express address book,
>>This would require an actual driver, that handles the SQL itself, like
>>mork for Mozilla.
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.
Another promissing option would be to pick up this wrapper library:
http://svn.jetbrains.org/omeaopen/trunk/Omea/Src/Plugin/Primary/EmapiLib/
not sure about License: It is GPL.
>Do you think you could take your findings here and split them up into
>filed easy (or challenging) hacks ?
Done.https://bugs.freedesktop.org/show_bug.cgi?id=56902  and dependencies.
Thanks!
In addition we shouldn't forget:
* mork driver ist still not activated on windows: to access 
Thunderbird/Icedove AB mozab driver is still in use
* deprecate moz shipping as it may be needed for some extensions. That 
why Stephan reverted my patch:
"don't compile moz module on all non windows platforms"
Regards
David
Context
- Re: fdo#51004: some progress and 10 years old bug pending (continued)
 
   
 
  Privacy Policy |
  
Impressum (Legal Info) |
  
Copyright information: Unless otherwise specified, all text and images
  on this website are licensed under the
  
Creative Commons Attribution-Share Alike 3.0 License.
  This does not include the source code of LibreOffice, which is
  licensed under the Mozilla Public License (
MPLv2).
  "LibreOffice" and "The Document Foundation" are
  registered trademarks of their corresponding registered owners or are
  in actual use as trademarks in one or more countries. Their respective
  logos and icons are also subject to international copyright laws. Use
  thereof is explained in our 
trademark policy.