[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-pim
Subject:    Re: [Kde-pim] [PATCH] KOrganizer
From:       tech () bishop ! dhs ! org
Date:       2003-08-03 22:55:01
[Download RAW message or body]

> > Any other objections or suggestions?
> 
> Yes, take very short events (and don't set the hour too large, otherwise you 
> don't see the problem). The really great thing about Tim's patch was that it 
> detected short events and in that case didn't print the time span header. 
> You, however, just print the header in any case, and allocate at least as 
> much space as is needed for the header. 
> This has two bad consequences:
> - - First, the actual description of short (up to ~1 hour in my hour size) the 
> event description won't be printed, and instead the time will be shown (which 
> is clear  from the timetable anyway). 
> - - And second, zero-time events (Yes, people are really using them. There are 
> at least 3 bug reports each with three or four duplicates about that!) and 
> very short events allocate at least the space needed for the header. If you 
> set the "Hour size in schedule view" to a rather small value, such zero-size 
> events will allocate 45 Minutes or more!!! 

My two cents: Reinhold is right.  I use both korganizer and iCal, and
while iCal is pretty, I much prefer entering short appointments into
korganizer, due to all the reasons he stated.  And I have a need to
enter about 10 15-minute long appointments a week, all crowded together, 
so this is a Big Deal.  Doing it on my Palm is even nicer, and is how I
do it if I have it in front of me.  Am I the only person around here
that does four-way syncs?  That is, I have my iBook w/iCal, desktop 
w/korganizer, handspring w/Datebook, and my T68i w/it's calendar.
Things get a bit messy sometimes :-)

David

_______________________________________________
kde-pim mailing list
kde-pim@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-pim
kde-pim home page at http://pim.kde.org/
[prev in list] [next in list] [prev in thread] [next in thread]