Bug 110063 - possibility to merge iCal files
Summary: possibility to merge iCal files
Status: CONFIRMED
Alias: None
Product: ktimetracker
Classification: Applications
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Compiled Sources Linux
: NOR wishlist
Target Milestone: ---
Assignee: Zoltan Gyarmati
URL:
Keywords:
: 139782 264225 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-08-02 23:44 UTC by Thorsten Staerk
Modified: 2019-11-12 21:11 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
merge 2 ical files (5.70 KB, patch)
2005-08-02 23:51 UTC, Thorsten Staerk
Details
export option - very unready (6.01 KB, patch)
2005-08-28 16:56 UTC, Thorsten Staerk
Details
The karm merge assistant, karrma.pl (3.81 KB, text/plain)
2005-11-16 04:03 UTC, David Bremner
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Thorsten Staerk 2005-08-02 23:44:27 UTC
Version:           1.6 (using KDE Devel)
Installed from:    Compiled sources
OS:                Linux

(request by David and Kalle via Mail)

Please add a possibility to merge two iCal files. Scenario:
You are on a trip, using karm on your laptop. For your monthly report, you need to merge the iCalendar file on your desktop with that on your laptop.
Comment 1 Thorsten Staerk 2005-08-02 23:47:29 UTC
I just wonder if that wasn't exactly why we enabled remote resources.
Too bad, I have already programmed a patch - that needs rethinking.
Comment 2 Thorsten Staerk 2005-08-02 23:51:31 UTC
Created attachment 12055 [details]
merge 2 ical files

This patch is only a notice for myself. It needs rethinking (urgently).
Comment 3 David Faure 2005-08-03 10:18:32 UTC
On Tuesday 02 August 2005 23:47, tstaerk wrote:
> I just wonder if that wasn't exactly why we enabled remote resources.


A remote resource requires to be online all the time, doesn't it?

The typical use case for importing an ical file from another computer,
is that other computer was used offline (in a train, plane, etc.).
Can't use a remote resource then.
Comment 4 Thorsten Staerk 2005-08-28 16:56:54 UTC
Created attachment 12409 [details]
export option - very unready
Comment 5 David Bremner 2005-11-16 04:03:07 UTC
Created attachment 13489 [details]
The karm merge assistant, karrma.pl

Well, I worked up a quick and dirty solution for my needs.

It seems pretty hard to do a decent job of merging tasks with the 
current timestamp scheme. Every task (VTODO) gets the same timestamp, 
and the last-modified tag is updated too. At least in version 1.5.1.
I guess some dialog could walk the user through the merge, but at least the
simple stuff, determining whether a task has been deleted, or is actually new,
ought to be possible just based on timestamps.

I rebuild the task times based on the history events. Of course, even if this 
is correct, it still requires an ever growing history file.
Comment 6 Thorsten Staerk 2007-01-09 13:03:02 UTC
*** Bug 139782 has been marked as a duplicate of this bug. ***
Comment 7 Thorsten Staerk 2007-01-09 13:06:58 UTC
David Fa., thanks for this idea - it is requested by David Fö. as well. 
David Fö.: David B. provided a workaround, a merging-tool for two ics-files. 

You motivate me to do this in KDE 4.

Any more David to comment on this ?
Comment 8 David Förster 2007-01-09 18:52:14 UTC
Already suggested in the duplicate report: Wouldn't it be simpler to just split the file into one for each session (time from 'start' to 'stop').

Cumulative time would then have to be calculated from multiple files but the concurrency issue would be solved. It would then be possible to use similar ressources like for the other pim data, wouldn't it?

Comment 9 Thorsten Staerk 2007-01-10 22:18:59 UTC
No, would not be simpler, because we have developed karm to use the ical libs of KDE PIM. Thanks for the suggestion, if you want to supply help for developing karm, look at http://wiki.kde.org/ktimetracker.
Comment 10 Thorsten Staerk 2011-02-26 00:17:20 UTC
*** Bug 264225 has been marked as a duplicate of this bug. ***
Comment 11 Andrew Crouthamel 2018-09-04 18:53:00 UTC
Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years so I will be closing this bug.