KOrganizer / KO/Pi (KOrganizer Platform independent)

[drboom]

Zautrix: you rock...
I just tried 1.6.6b and c.  Both versions seem to have the wrong (no execute) on the db2 import file.  

Also, the second time I did a sync in korganizer with the dtm, kopi decided that all local entries should be deleted (repeat syncs said nothing needed to be done) - deleting the ics file and resync\'ing got my data back.

kopi was extremely slow (I stopped counting after 5 minutes) with each operation with my full calendar data.  Deleting my calendar dtm files and resync\'ing with outlook and limited data set produced reasonable speed.  Before shrinking my data, my dtm file was around 600k and the corresponding ics file was over 1.4M, after my dtm is about 100k with the ics at around 280k.  This seems like quite a dramatic multiple, why?  I\'d like to bring my historical data back in, is there a way to improve performance with this?

Feature request:
The best view for me seems to be the \'what\'s next\' view - is there a way to change/add/whatever the \"in x days\" to mention the corresponding day of the week (i.e. Monday)?

kopi is incredible, thanks for all the hard work.  Jon

[Morpheus]

Zautrix,

I downloaded 1.6.6c and tried to sync with DTM, but the same problems occurred.  Running from the console, I managed to capture the following output before it crashed and rebooted my Zaurus:

bash-2.05$ QTime::setHMS Invalid time 31:63:63.000
QTime::setHMS Invalid time 31:63:63.000
QTime::setHMS Invalid time 31:63:63.000
QTime::setHMS Invalid time 31:63:63.000
QTime::setHMS Invalid time 31:63:63.000
QTime::setHMS Invalid time 31:63:63.000
QTime::setHMS Invalid time 31:63:63.000
QTime::setHMS Invalid time 31:63:63.000
QTime::setHMS Invalid time 31:63:63.000
QTime::setHMS Invalid time 31:63:63.000
QTime::setHMS Invalid time 31:63:63.000
QTime::setHMS Invalid time 31:63:63.000
QTime::setHMS Invalid time 31:63:63.000
QTime::setHMS Invalid time 31:63:63.000
QTime::setHMS Invalid time 31:63:63.000
QTime::setHMS Invalid time 31:63:63.000
QTime::setHMS Invalid time 31:63:63.000
QTime::setHMS Invalid time 31:63:63.000
QTime::setHMS Invalid time 31:63:63.000
QTime::setHMS Invalid time 31:63:63.000
QTime::setHMS Invalid time 31:63:63.000
QTime::setHMS Invalid time 31:63:63.000
QTime::setHMS Invalid time 31:63:63.000
QTime::setHMS Invalid time 31:63:63.000
QTime::setHMS Invalid time 31:63:63.000
QTime::setHMS Invalid time 31:63:63.000
SlZDataManager::readUshortItem error in CardRead 3 0 0
SlZDataManager::readUshortItem error in CardRead 4 0 0
SlZDataManager::readUshortItem error in CardRead 1 0 0
SlZDataManager::readUshortItem error in CardRead 1 0 0
SlZDataManager::readUshortItem error in CardRead 5 0 0
SlZDataManager::readUshortItem error in CardRead 6 0 0
SlZDataManager::readUshortItem error in CardRead 2 0 0
SlZDataManager::readUshortItem error in CardRead 19 0 0
QTime::setHMS Invalid time 31:63:63.000
QTime::setHMS Invalid time 31:63:63.000
QTime::setHMS Invalid time 31:63:63.000
QTime::setHMS Invalid time 31:63:63.000
QTime::setHMS Invalid time 31:63:63.000
QTime::setHMS Invalid time 31:63:63.000
QTime::setHMS Invalid time 31:63:63.000
KOEventViewerDialog::setSyncMode 1
KO: Saving File in 61 secs!
KO: Start saving data to file!
KO: Saving File in 600 secs!
KO: Needed 235 ms for saving.    

# Then it listed the synchronization summary which I couldnt capture because of crash

KOEventViewerDialog::setSyncMode 0

# The KO Event above is the last thing I saw on the console before it locked
# my Zaurus up, then after about 3-4 mins it rebooted.

[danr]

@danr
Strange, that the db2file was left out when installing.
What do you mean exactly with your minor feature request?

I think what actually happened was the db2file binary wasn\'t set with execute permissions, so when I tried running it from the command line, it couldn\'t be found in my path, so I copied it over manually.

My request is this: if you use some of the Sharp apps, such as datebook or addressbook, pressing the key which loaded up the app (such as the calendar button) will change the view in the app itself.  I thought this would be a useful addition to KO/Pi, whereby if it\'s assigned to the calendar button, pressing this button when it\'s loaded will alternate between different views (being able to select which views to alternate between would be even better!)

I\'d like to say a big thanks for continuing your improvements of KO/Pi.  I\'ve released GPL software myself in the past and know what it\'s like to receive lots of support requests, so hats off to your continuing enthusiasm.

Daniel

[bluedevils]

My DTM info transferred synced, but then kopi and the sharp PIM became completely slow.  I was patient and it sometimes took 15 minutes for the app to respond.  I restored my data and I have cleared the sharp DTM.  I\'ll try to sync later to find out if that has any effect.

[zautrix]

Hi,

I have found and fixed many bugs in the DTM syncing.
It should work now much better.
I think, I have fixed the crash as well, because I have changed DTM access a little.

I have added the \"Cancel\" (Cross-out) Option for events/todos. Cancelled events are displayed stricked out. And alarms of cancelled events/todos are ignored .

I added config options for the todo-view and for the month-view.

You get a new event in the month view, if you click in a cell on the number of the date.

z.

[cortez]

I have added the \"Cancel\" (Cross-out) Option for events/todos. Cancelled events are displayed stricked out. And alarms of cancelled events/todos are ignored .

Thanks man, it\'s great to have this back!

[snufkin]

Zautrix,

Appreciate your great work!  I\'ve downloaded the latest version (1.6.7a) and it seems no significant change.  Syncing with DTM seems no problem to me but after syncing, the speed is extremely slow.

I have 583 items synced to KO/Pi and the mycalendar.ics is around 262k bytes.   Frankly, I don\'t know whether the slow speed is caused by DTM sync or not.


I ran it in console and nothing strange came out.

[Morpheus]

Zautrix,  You are a Star!!  The DTM sync worked flawlessly.  Now I can really start to use this cool PIM.

I have a small request:  When I sync the DTM, an appointment is created as I expected, but it has a duration of 2 hrs.  Could you change the default duration of this to something less obtrusive.  15 or 30 minutes max would be preferred.

Thanks again for an excellent application.

Jason

[brycenut]

Zautrix,
Just put 1.6.7a on and it works great. Thanks for all the great work.  Apparently my former problem was related to an old icon I had that never got refreshed, as the new icon created by 1.6.7a works, and the older one still doesn\'t.  Regarding launching from a terminal, I realized I had been trying to launch with the command \"korganizer\", which still gives me the same message, rather than \"kopi\", which starts it fine.

Again, thanks for the great work. It\'s a very nice piece of software.

[Morpheus]

Missing libqpepim.  I just installed the addressbook plugin, but I got a message saying Plugin Missing when I try to use it.  The message also says the Qtopia plugin requires libqpepim.  Is this what I need?  if so, where do I get it from?

Jason

[zautrix]

The Qtopia addressbook plugin is for Qtopia Pim, not for Sharp-DTM Pim.
I should change the error message of the plugin ....

[bluedevils]

yes the sync is a definite bonus, but it does bring an old problem to the fore front.  How do you maintain sync and not have two PIMs alarm you?  On the surface it seems like a bit of a catch 22

[elvis]

Canceling a repeat event cancels every single future event. Could this behavior be changed to canceling only the event chosen? For example, I have a class next Tuesday that was cancelled. I marked it as cancelled in KO/Pi but that had the effect of marking every single future class as cancelled -- I only wanted to make a single class as cancelled not all of them!

I\'ve also noticed one of the configuration screens (the date format screen) kind of looks ugly because the example string runs right off screen on the 5500. You might consider removing this or changing it so it looks better.

Thanks for all the hard work.

[zautrix]

Hi elvis,

yes the recurrence handling is not optimal.
Your suggestion is good, but it is not possible to do this in the used data structure of ical files.
I have added the following:
Now you can move recurring enents in Agenda View. It you move a recurring event, the date is added automatically to the exception list of dates for the recurrence and a new non-recurring clone is created.
Now you have changed the time/date of one recurrence.
If you do want to remove it completely, just delete the newly created non-recurring clone.
(Or move it back and cancel it ).

All:

As mentioned above, 1.6.7b is available. New features:
Now saving of descriptions/journals to plain text file is possible: In listview/searchlist select some entries. Choose pulldown menu Save Journal/Description. Second big change: Now you can move recurring events in Agenda View. It you move a recurring event, the date is added automatically to the exception list of dates for the recurrence and a new non-recurring clone is created.

I have compiled a new version for windows as well, such that you are up to date on windoos too.

z.

[snufkin]

zautrix,

haveyou also solved the slow speed problem in this release?  i\'d love to be a volunteer to test it