[Kroupware] Outlook-Enhancement
Jon Bendtsen
jon at kollegiegaarden.dk
Fri Mar 5 17:27:57 CET 2004
Den 5. mar 2004, kl. 15:31, skrev Stefan Lang:
> I would like to diskuss this once more!
>>>> On Wednesday 03 March 2004 11:42, Stefan Lang wrote:
>>>>> We have an employee in our company, who is able to develop a
>>>>> "plugin"
>>>>> for M$ Outlook which is able to store its calendar-content
>>>>> "regulary"
>>>>> in vcal-format! My questions are:
>>>>> 1) Is this a "workaround" to share calendar informatinon (not
>>>>> freebusy) between Outlook- and Kontact-Users?
>>>>
>>>> This is not a workaround, it would be the real solution!
>>>
>>> Well, the question is if it will work for 100% e.g. hwo does he
>>> solve the
>>> GUID issue? (OL needs the GUID and a lot of other internal data of a
>>> calendar item in order to keep internal references correct)
>>>
>>> So basically this means that the plugin must not only be able to
>>> write
>>> (easy) but also to read the vcals in all their beauty.
>
> I know, there are people with more experience and knowledge, regarding
> this
> topic, around , like I do ........but
>
> What, if we don't touch Outlook, let it store its calendar information
> the way
> it wants, and convert it to vcal on the server.....perhaps "in" kolab!
That is not as scaleable as doing everything in the client.
> Advantages:
> 1) We don't have to struggle with OL.....and its many many Versions and
> subversions (patches, servicepacks). It's a nightmare to develop a
> software
> covering all those shi...y versions.
Wouldnt we still need to code something to store the ms format on the
kolab server?
> 2) We would improve kolab and not an "enemies" product! ;-)
Good point.
> 3) There are perl-based tools for READING tnef-files around, so perl
> could be
> our friend! For WRITING these files, I didn't find anything! :-(
reverse the perl code ?
> Disadvantage(s):
> 1) We must convert from TNEF-Format to vcal and back again, if someone
> modifies the OL-users calendar with a kontact-client!
i dont think that would happen very often.
JonB
More information about the Kroupware
mailing list