Kroupware Merge

This report was contributed by by Cornelius Schumacher

Steffen, Lutz, Günter and Cornelius discussed how to finish the merge of the kroupware branch into the HEAD branch. There is still missing the Free/Busy handling, the configuration, changes to the attendee tab of the todo editor and some minor things.

We agreed on the details how to proceed with the merge (see below). To get all the functionality into the HEAD branch we can temporarily merge the kokroupware file and resolve the remaining isssues in the HEAD branch.

The kroupware developers will send patches. As the HEAD branch is diverging quickly from the 3.1 and the kroupware branch it will be less work, if the merge is done as soon as possible.

Details:

• The KNotes view in KOrganizer will be removed. This will be replaced by the KNotes plugin in Kaplan. There is a make_it_cool branch in knotes which saves the data to iCalendar. This should be changed to be able to also use the IMAP resource (see report about new resource framework) to store the notes data to the kolab server.
• The signal/slots communication will be replaced by DCOP calls. This will make some ugly things go away like the KMail main window pointer in KOrganizer.
• The attendee tab of the event editor with integrated free/busy view is too big for small screen resolutions. The free/busy view will be moved to an own tab which also includes the controls for setting start and end time of an event. Adding/editing attendees in the free/busy view tab will be handled by context menus and maybe inline editing in the gantt widget. The attendee tab will remain as it is in the non-kroupware branches. The 12/24 hour format switch will be replaced by accessing the KDE preferences via KLocale.
• The attendee tab of the todo editor has been replaced in the kroupware branch. Currently it uses a #define to switch bewteen the two versions. This will be changed to be configurable at run-time. Which attendee tab is used in the editor will be chosen by the number of attendees associated with the todo. If there is none or only one, the kroupware version is used, if there are more the standard conformat version from HEAD is used.
• There are some issues with Outlook interoperability where Outlook doesn't conform to the iCalendar/iTIP standards or does only support a subset of it. There are good reasons to be interoperable with Outlook and this might justify an configuration option to enable Outlook compatible behaviour. This shouldn't limit the ability to behave standards-compliant, though.
• Accessing calendar data on the kolab server will be handled by a IMAP resource talking via DCOP to KMail.

| back to meeting overview |

[ Edit ]