[Korganizer-devel] [Bug 28583] Too many holidays: ~/.holiday please

Erik Anderson erikanderson3 at gmail.com
Sun Feb 8 11:00:23 CET 2009


http://bugs.kde.org/show_bug.cgi?id=28583





--- Comment #8 from Erik Anderson <erikanderson3 gmail com>  2009-02-08 11:00:22 ---
(In reply to comment #7)
> Thank you, Reinhold, for your suggestion. 
> It works just fine in both KDE 3.5.10 and 4.1.x .
> Actually, I made a link from .kde4/... to .kde/..., so both see the same file.
> That covers (not solves) the need for multiple calendars as in 
> http://bugs.kde.org/show_bug.cgi?id=92471
> 
> Erik, I don't understand why ical would be any better. After all, you can
> import iCalendar, isn't it the same ? 
> 

Hello Michael --

I see you later commented over in the Bug 92471 report.  As noted there, my
suggestion about .ics files was prompted by:

* my need to have more than one holiday 'region' shown at once (described in
more detail in the Bug 92471 thread), whereas Korganizer only allows (allowed?)
one and only one 'region';
* confusion as to why Korganizer needs a whole new format to describe holidays
when .ics already does the job;
* and a desire for simplicity and better interoperability by using the already
widely employed .ics format.


> After all, you can import iCalendar, isn't it the same?

While functionally offering the same end result, it's terribly confusing to
have a "Holiday" setting in the Korganizer GUI that is limited to only one
'region'; and even should the holiday files be expandable to include more than
one 'region', it's also terribly confusing to have to learn a completely new
file format simply to define holidays that may already be fully described in
existing and downloadable .ics files.  

My suggestion was made primarily for simplicity's sake -- Korganizer's holiday
file format is not so widely known, requires more work of the end user to add
to, is more confusing than .ics (IMHO), and increases the code and GUI
complexity and reduces the usability of the UI -- all to duplicate
functionality that already exists (i.e., import .ics files defining the
holidays you want).  The whole holiday 'region' code could be entirely removed
from Korganizer, streamlining the codebase and simplifying the UI, and most of
us wouldn't miss it -- and those that did could achieve the same result using
.ics files.  

I guess I'm just confused as to why we need all of this separate functionality
for holidays.  

There's my $0.02.  :)  YMMV.  

Cheers,

-- Erik Anderson


-- 
Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


More information about the Korganizer-devel mailing list