[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-pim
Subject: [Kde-pim] KOrganizer docs
From: "Carlos Leonhard Woelz" <carloswoelz () imap-mail ! com>
Date: 2005-08-30 14:21:40
Message-ID: 1125411700.15664.241785138 () webmail ! messagingengine ! com
[Download RAW message or body]
Hi,
As you probably noticed, commited the new KOrganizer docs. I would
appreciate if the people who have been working in the calendar resources
could check the new groupware resources section for completness and
correction (especially, updating supported server versions), as I don't
have access to the servers, (with exception of Kolab).
From the commit log, Volker Krause (SLOX and OX), Will Stephenson
(Groupwise and SLOX), Reinhold (various), Cornelius, Tobias
(eGroupware), etc. are the ones I am looking for... please take a look.
Cheers,
Carlos Woelz
Here is the text for easy quoting:
<snip the obivious ones>
--------
Birthdays from KAddressBook
Add this resource to view birthdays from contacts in KAddressBook in
your calendar. The birthday appears in your calendar as a read only
event and without associated time.
Journal Entries as Blogs on Server
Add this resource to be able to publish your journal entries as
blogs, directly on blog servers, such as blogger and drupal.
Bugzilla To-do List
Add this resource to load bugzilla open bugs as to-dos. Bugzilla is
an open source bug tracking system. If you are a developer working
on a project that uses bugzilla, you can use this resource to view
as to-dos the open bugs of the applications or libraries you are
interested in (they are called “products” and / or “components” in
bugzilla). This resource is available as part of the KDE Software
Development kit.
XML Feature Plan
Add this resource to load a XML Feature Plan as to-dos. The XML
Feature Plan is a scheme designed to document the new features of
future software releases. It was designed to fit the KDE release
schedule needs, but can be helpful for any software project. The
information from the XML file can be used to control feature
freezes, to report the new features of new release or the status of
the new features of a future release.
GroupDav Server (e.g. Open Groupware)
If you have access to a server that supports the GroupDav protocol,
add this resource in order to be able to to save (and load) events
and to-dos to the server. To add the resource, you will need to know
the server URL, your user name and your password. The GroupDav
protocol supports the storage of contacts, so you may want to add
and configure the KAddressBook resource too.
As of June 2005, the groupware servers that implement this protocol
are the OpenGroupware server and the Citadel server. An up to date
list can be obtained at the GroupDav website.
Novell Groupwise Server
If you have access to a Novell GroupWise Server (version 6.5 or
later), add this resource in order to be able to to save (and load)
events, free/busy information and to-dos to the server. To add the
resource, you will need to know the server URL, your user name and
your password. There is support for storage of contacts, so you may
want to configure KAddressBook resource.
The most practical way to configure the access to a GroupWise server
is to use the groupwisewizard wizard. You can start it from the
command line prompt:
$groupwisewizard
The wizard will configure not only KOrganizer to use the GroupWise
resources, but KMail, KAddressBook too.
Calendar on IMAP Server via KMail
If you have access to a server that shares calendar data via IMAP,
add this resource in order to be able to to save (and load) events,
to-dos, free/busy information and journal entries to the server. To
enable IMAP access, you will need to configure KMail first, then add
the KOrganizer resource. Also, since you are using KMail to contact
the server, KOrganizer will open KMail automatically, and use it to
access your data. The “IMAP server via KMail” schema supports the
storage of contacts, so you may want to add the KAddressBook
resource too.
The main implementation of this schema is the Kolab Server. As of
June 2005, the groupware servers that implement the “Kolab 1” and
“Kolab 2” protocols are the Kolab server, version 1 and 2, and the
Citadel server (Kolab 1 only). An up to date list can be obtained at
the Kolab website.
The most practical way to configure the access to a Kolab server is
to use the kolabwizard wizard application. You can start it from the
command line prompt:
$kolabwizard
If you want to configure KMail yourself instead of using the wizard,
you can access the configuration by choosing the Settings->Configure
KMail... menu item. Click the Accounts icon in the configure dialog
sidebar and add the IMAP server as a disconnected IMAP incoming
account. Now click the Misc icon in the sidebar and click the
Groupware tab to enable and configure the IMAP resource folder
options. Only then you can add the KOrganizer (and KAddressBook)
resources. For more information on configuring KMail, consult the
KMail handbook.
Calendar on Exchange Server (Experimental)
If you have access to a Exchange 2000 Server, add this resource in
order to be able to to save (and load) events to the server. To add
the resource, you will need to know the server URL, your user name
and your password. There is support for (read only) contacts, so you
may want to configure KAddressBook resource.
Calendar in Remote File
Add this resource to be able to save and load your events, to-dos
and journal entries from a remote file. There are two main
advantages of keeping your calendar data in a remote server: you can
access your data even if you are away from your computer, and you
can let other people (for instance, a secretary) view it. KOrganizer
keeps a cache of the data locally.
A screenshot of KOrganizer's Remote File Resource Configuration
A screenshot of KOrganizer's Remote File Resource Configuration
You can configure the resource to be read only, keeping the remote
file untouched. In this case, you won't need to supply a “Upload to”
location, just a “Download from” location for the remote file. If
you plan to use a writable remote resource, you will have to supply
both locations. The reason to have separate locations, is that some
servers may have an upload queue, a place where you need to put the
upload file, different from where it will be. In most cases, if you
have write access to the remote file, the Upload to and Download
from file locations should be the same.
It is important to understand that the remote file resource does not
add or remove individual items from the remote file, it simply saves
the remote file over local cache when downloading and save the local
cache over the remote file when uploading. Therefore, if the
resource is read only, it makes sense to set the Automatic Reload
option to an Regular interval, but if not (if the resource is
writable), it is recommended to reload the file only before starting
to edit it, by setting the Automatic Reload option to On startup,
and to save it before exiting, by setting the Automatic Save option
at least to On exit, or better yet, if you have a fast and stable
connection to the remote file, set it to On every change to avoid
data loss.
Warning:
If you add, change or remove events, journal entries or to-dos and
reload the remote file, all your local changes will be lost, and the
file will revert to its previous state. This can happen in different
scenarios (for instance if the system crashes, KOrganizer will
reload the remote file on the next start, if you set the Automatic
Save to Never, or if you set the Automatic Reload to a regular
interval). If you plan to use calendar resource in writable mode,
make sure that your connection is stable, configure the resource to
save the file on each change, (or on frequent intervals) and don't
reload the file in regular intervals.
A related, but opposite problem, is that two users can not safely
edit the same remote file at the same time, because the remote file
resource does not offer a conflict resolution mechanism. For
instance, if someone else changes (and saves) the remote file, after
you loaded it, and a some time later you save the file, his changes
will be lost.
SUSE Linux OpenExchange Server
If you have access to a SUSE Linux OpenExchange Server, version 4.1,
add this resource in order to be able to to save (and load) events,
free/busy information and to-dos to the server. To add the resource,
you will need to know the server URL, your user name and your
password. There is support for storage of contacts, so you may want
to configure KAddressBook resource.
The most practical way to configure the access to a GroupWise server
is to use the sloxwizard wizard. You can start it from the command
line prompt:
$sloxwizard
The wizard will configure not only KOrganizer to use the
OpenExchange resources, but KMail, KAddressBook too.
eGroupware Server (via XML-RPC)
If you have access to a eGroupware Server, version 1.0, add this
resource in order to be able to to save (and load) events, free/busy
information and to-dos to the server. To add the resource, you will
need to know the server URL, your user name and your password. There
is support for storage of contacts, so you may want to configure
KAddressBook resource.
The most practical way to configure the access to a eGroupware
server is to use the egroupwarewizard wizard. You can start it from
the command line prompt:
$egroupwarewizard
The wizard will configure not only KOrganizer to use the eGroupware
resources, but KMail, KAddressBook too.
_______________________________________________
kde-pim mailing list
kde-pim@kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
kde-pim home page at http://pim.kde.org/
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic