| Summary: | possibility to merge iCal files | ||
|---|---|---|---|
| Product: | [Applications] ktimetracker | Reporter: | Thorsten Staerk <dev> |
| Component: | general | Assignee: | Zoltan Gyarmati <mr.zoltan.gyarmati> |
| Status: | CONFIRMED --- | ||
| Severity: | wishlist | CC: | aspotashev, david, faure, s.suther |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
merge 2 ical files
export option - very unready The karm merge assistant, karrma.pl |
||
|
Description
Thorsten Staerk
2005-08-02 23:44:27 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. Created attachment 12055 [details]
merge 2 ical files
This patch is only a notice for myself. It needs rethinking (urgently).
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.
Created attachment 12409 [details]
export option - very unready
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.
*** Bug 139782 has been marked as a duplicate of this bug. *** 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 ? 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? 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. *** Bug 264225 has been marked as a duplicate of this bug. *** 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. |