steffen: server/kolab-horde-fbview/kolab-horde-fbview/fbview/kronolith/docs CHANGES, NONE, 1.1 CREDITS, NONE, 1.1 INSTALL, NONE, 1.1 RELEASE_NOTES, NONE, 1.1 TODO, NONE, 1.1

[cvs at intevation.de]

Author: steffen

Update of /kolabrepository/server/kolab-horde-fbview/kolab-horde-fbview/fbview/kronolith/docs
In directory doto:/tmp/cvs-serv18388/kolab-horde-fbview/kolab-horde-fbview/fbview/kronolith/docs

Added Files:
	CHANGES CREDITS INSTALL RELEASE_NOTES TODO 
Log Message:
Fbview in separate package

--- NEW FILE: CHANGES ---
(This appears to be a binary file; contents omitted.)

--- NEW FILE: CREDITS ---
================================
|| Kronolith Development Team ||
================================

===============
Core Developers
===============

Chuck Hagenbuch <chuck at horde.org>
- original concept
- all current code (this really can change)
- PEAR DB:: and MCAL drivers


=======
Drivers
=======

MCAL                Chuck Hagenbuch <chuck at horde.org>
MySQL (deprecated)  Luc Saillard <luc+kronolith at alcove.fr>
PEAR DB             Chuck Hagenbuch <chuck at horde.org>


============
Localization
============

Arabic (Syria)          Platinum Development Team <devteam at platinum-sy.net>
Brazilian Portuguese    Samuel Mota <samuel at bumerangue.com>
Bulgarian               Miroslav Pendev <miro at cybershade.us>
Chinese (Simplified)    Zhang Bo <boozhang at sdb.ac.cn>
Chinese (Traditional)   David Chang <david at thbuo.gov.tw>
Czech                   Pavel Chytil <pchytil at asp.ogi.edu>
Danish                  Bill Edgington <horde at 0x20.com>
                        Martin List-Petersen <martin at list-petersen.dk>
Dutch                   Jan Kuipers <jrkuipers at lauwerscollege.nl>
Finnish                 Leena Heino <liinu at uta.fi>
French                  Mikhaël Janson <mik at galaxie.net>
                        Benoit St-André <ben at benoitst-andre.net>
German                  Jan Schneider <jan at horde.org>
Greek                   Stefanos I. Dimitriou <support at teiath.gr>
                        Silligardos Xristoforos
                        Anagnostopoulos Apostolis
Hungarian               Laszlo L. Tornoci <torlasz at xenia.sote.hu>
Italian                 Giovanni Meneghetti <gmeneghetti at infvic.it>
Korean                  J.I Kim <aporie at netian.com>
Lithuanian              Darius Matuliauskas <darius at lnk.lt>
                        Vilius Sumskas <vilius at lnk.lt>
Norwegian Bokmaal       Torstein S. Hansen <huleboer at techbee.no>
Norwegian Nynorsk       Per-Stian Vatne <psv at orsta.org>
Polish                  Maciek Uhlig <muhlig at us.edu.pl>
Romanian                Eugen Hoanca <eugenh at urban-grafx.ro>
                        Marius Dragulescu <mariusd at urban-grafx.ro>
Russian                 Anton Nekhoroshih <anton at valuehost.ru>
                        Fedor A. Fetisov <faf at ssc.ru>
Slovak                  Leo Mrafko <leo at oel.sk>
Swedish                 Andreas Dahlén <andreas at dahlen.ws>

$Horde: kronolith/docs/CREDITS,v 1.31 2004/01/28 12:42:01 jan Exp $

--- NEW FILE: INSTALL ---
==============================
|| INSTALLING Kronolith 2.0 ||
==============================

This document contains instructions for installing the Kronolith
web-based calendar application on your system.

For information on the capabilities and features of Kronolith, see the file
README in the top-level directory of the Kronolith distribution.


OBTAINING Kronolith
-------------------

Kronolith can be obtained from the Horde website and FTP server, at

   http://www.horde.org/kronolith/
   ftp://ftp.horde.org/pub/kronolith/

Bleeding-edge development versions of Kronolith are available via CVS; see
the file docs/HACKING in the Horde distribution for information on
accessing the Horde CVS repository.


PREREQUISITES
-------------

To function properly, Kronolith requires the following:

  1. A working Horde installation.

     Kronolith runs within the Horde Application Framework, a set of
     common tools for Web applications written in PHP. You must
     install Horde before installing Kronolith.

     The Horde Framework can be obtained from the Horde website and
     FTP server, at

        http://www.horde.org/horde/
        ftp://ftp.horde.org/pub/horde/

     Many of Kronolith's prerequisites are also Horde prerequisites.
     Be sure to have completed all of the steps in the INSTALL
     file for the Horde Framework before installing Kronolith.

  2. MCAL or SQL support in PHP.

     Kronolith store its data either using the MCAL extension, or in
     an SQL database. Build PHP either --with-mcal or with whichever
     SQL driver you require; see the Horde INSTALL file for more
     details on using databases with Horde.

     If you are using MCAL, and don't have support for it in PHP
     already, here are instructions for compiling libmcal and
     PHP. Make sure to use libmcal 0.7 and libmcal drivers 0.9, or later.

     (Note that there are RPMs for libmcal and a libmcal-aware PHP if
     you use RedHat. You can get these from the Horde site:
     ftp://ftp.horde.org/pub/RPMS/)

     Check out libmcal from CVS:
     > cvs -d :pserver:anonymous at cvs.libmcal.sourceforge.net:/cvsroot/libmcal login
     (leave Password blank)
     > cvs -d :pserver:anonymous at cvs.libmcal.sourceforge.net:/cvsroot/libmcal co libmcal

     Check out icap and mstore from CVS, UNDER libmcal:
     > cd libmcal
     > cvs co icap mstore

     Compile:
     > cd icap
     > make
     > cd ../mstore
     > make
     > cd ..
     > ./configure --with-icap --with-mstore
     > make; make install
     additionally copy *.h to /usr/local/mcal/include

     > mkdir /var/calendar
     > chmod 1777 /var/calendar

     cd to php4 src directory
     configure php with --with-mcal=/usr/local/mcal and other regular options
     make and make install

     cd to apache directory
     make and make install

     restart your httpd server

     make the mstore password file /etc/mpasswd
     use the htpasswd program from apache
     for the first time use
     > htpasswd -c /etc/mpasswd username
     and for adding more users don't use the -c switch

     You only need one username to run kronolith. The calendars for
     the different horde users are managed automatically.


INSTALLING Kronolith
--------------------

Kronolith is written in PHP, and must be installed in a web-accessible
directory. The precise location of this directory will differ from
system to system. Conventionally, Kronolith is installed directly underneath
Horde in the webserver's document tree.

Since Kronolith is written in PHP, there is no compilation necessary;
simply expand the distribution where you want it to reside and rename
the root directory of the distribution to whatever you wish to appear
in the URL. For example, with the Apache webserver's default document
root of '/usr/local/apache/htdocs', you would type:

   cd /usr/local/apache/htdocs/horde
   tar zxvf /path/to/kronolith-1.0.tar.gz
   mv kronolith-1.0 kronolith

and would then find Kronolith at the URL

   http://your-server/horde/kronolith/


CONFIGURING Kronolith
---------------------

1. Configuring Horde for Kronolith

   a. Register the application

      In horde/config/registry.php, find the applications['kronolith'] stanza.
      The 'show' parameter should already be marked '=> true'.
      If you have changed the location of Kronolith relative to Horde,
      either in the URL or in the filesystem or both, you must
      update the 'fileroot' and 'webroot' settings to their correct
      values.

2. [Only if you are using SQL, not libmcal] Creating the database table

   The specific steps to create the Kronolith database table depend
   on which database you've chosen to use.

   First, look in scripts/drivers/ to see if a script already
   exists for your database type. If so, you should be
   able to simply execute that script as superuser in your
   database. (Note that executing the script as the "horde" user will
   probably fail when granting privileges.)

   If such a script does not exist, you'll need to build your own, using
   the file kronolith.sql as a starting point. If you need
   assistance in creating databases, you may wish to let us know on
   the Kronolith mailing list.

   You will also need to make sure that the "horde" user in your
   database has table-creation privileges, so that the tables that
   PEAR DB uses to provide portable sequences can be created.


3. Configuring Kronolith.

   To configure Kronolith, change to the config/ directory of the
   installed distribution, and make copies of all of the configuration
   "dist" files without the "dist" suffix:

      cd config/
      for foo in *.dist; do cp $foo `basename $foo .dist`; done

   Documentation on the format of those files can be found in each
   file; open each in an editor and make changes as suggested within.
   The default values are reasonable, but may not be appropriate for
   your site, so it is best to check them before preceeding.

   You must login to Horde as a Horde Administrator to finish the
   configuration of kronolith.  Use the Horde "Administration" menu item to
   get to the Administration page, and then click on the "Configuration"
   icon to get the Configuration page.  Select "Calendar" from the selection
   list of applications, and click on the "Configure" button.  Fill in or
   change any configuration values as needed.  When done click on "Generate
   Calendar Configuration" to generate the conf.php file.  If your web server
   doesn't have write permissions to the configuration directory or
   file, it will not be able to write the file.  In this case, cut and
   paste the returned configuration information into the file
   kronolith/config/conf.php.

   Note for international users:  Kronolith uses GNU gettext to provide local
   translations of text displayed by applications; the translations are
   found in the po/ directory.  If a translation is not yet available
   for your locale (and you wish to create one), or if you're having
   trouble using a provided translation, please see the horde/docs/TRANSLATIONS
   file for instructions.

4. Testing Kronolith

   Use Kronolith to create, modify, and delete events. Test at
   least the following:

     - Creating a new event
     - Creating a recurring event
     - Modifying an event
     - Deleting an event


OBTAINING SUPPORT
-----------------

If you encounter problems with Kronolith, help is available!

The Horde Frequently Asked Questions List (FAQ), available on the Web
at

  http://www.horde.org/faq/

The Horde Project runs a number of mailing lists, for individual
applications and for issues relating to the project as a whole.
Information, archives, and subscription information can be found at

  http://www.horde.org/mail/

Lastly, Horde developers, contributors and users also make occasional
appearances on IRC, on the channel #horde on the freenode Network
(irc.freenode.net).

Please keep in mind that Kronolith is free software written by volunteers.
For information on reasonable support expectations, please read

  http://www.horde.org/support.php

Thanks for using Kronolith!

The Horde team
kronolith at lists.horde.org

$Horde: kronolith/docs/INSTALL,v 1.13 2003/11/18 20:00:41 ericr Exp $

--- NEW FILE: RELEASE_NOTES ---
<?php
/**
 * Release focus. Possible values:
 * 0 - N/A
 * 1 - Initial freshmeat announcement
 * 2 - Documentation
 * 3 - Code cleanup
 * 4 - Minor feature enhancements
 * 5 - Major feature enhancements
 * 6 - Minor bugfixes
 * 7 - Major bugfixes
 * 8 - Minor security fixes
 * 9 - Major security fixes
 */
$this->notes['fm']['focus'] = 5;

/* Mailing list release notes. */
$this->notes['ml']['changes'] = <<<ML
After almost two years of work, the Horde Team is proud to announce the first
alpha release of the Kronolith Calendar Application version 2.0.

Kronolith is the Horde calendar application. It provides web-based calendars
backed by either a SQL database or the MCAL library. Supported features
include shared calendars, remote calendars, meeting management, alarms,
recurring events, and a sophisticated day/week view which handles arbitrary
numbers of overlapping events.

This is a preview version that should not be used on production
systems.  Some small parts are missing and there are still a few bugs,
some of which are listed below.  You should not use this preview
version over existing production data.

The API, configuration items, or features may change before the final
release, but we encourage widespread testing and feedback via the mailing
lists or our bug tracking system. Translations are not ready to be updated
yet, since some strings will change before the final release.

The major changes compared to the Kronolith 1.x versions are:
    * Shared calendars.
    * Meeting management through iCalendar and iTip messages.
    * Event reminders through email.
    * iCalendar import and export.
    * Generation of free/busy information.
    * Remote calendars.

Known issues:
    * Documentation is not completely updated yet.
ML;

/* Freshmeat release notes. */
$this->notes['fm']['changes'] = <<<FM
Support for shared calendars has been added.
Meetings can now be managed through iCalendar and iTip messages.
Email-based event reminders have been added.
iCalendar data can now be imported and exported.
Free/busy information is being generated automatically now, for use in Outlook
or other calendar applications.
Remote calendars have been added.
FM;

$this->notes['name'] = 'Kronolith';
$this->notes['fm']['project'] = 'kronolith';
$this->notes['fm']['branch'] = 'FRAMEWORK_3';

--- NEW FILE: TODO ---
=====================================
|| Kronolith Development TODO List ||
=====================================

- Finish scripts/eventd to flexibly send reminders.

- Need a UI for deleting exceptions to a recurring event.

- A separate location to select the calendars to display in the
summary. Currently the summary displays what ever you had selected the
last time you were in Kronolith.

- The option to not have any personal calendars displayed, now with
remote calendars this would be a desirable option.

- Remove the assumption that each calendar is using the same
backend. Ideally it should be possible to have a local calendar using
sql or mcal and a remote calendar using another driver (eg wcap or
whatever mozilla uses).

- Drivers should handle the permissions checks instead of accessing
shares directly (outside drivers) to get the permissions for an event
or calendar. One day we might have a calendar backend that knows about
permissions.

- Allow publishing calendars to a remote site as iCalendar files.

- Allow direct access to calendars in iCalendar format (for working
directly with Mozilla Calendar, Apple's iCal, and similar programs as
a remote calendar server).

- Saving of individual events as .ics files.

- Support for searching a local file system for freebusy info.

- Support for searching freebusy.office.microsoft.com for freebusy
info.

- Automatically locate a meeting time.

- Add a quick tool for planning meeting agendas.

- Handle resource scheduling/management somehow, either per-calendar
or by kinds of calendars, including rules for when overlapping
appointments are allowed, etc.


$Horde: kronolith/docs/TODO,v 1.12 2004/05/12 19:57:35 chuck Exp $