OK, Guys, fecal matter is gonna rain down hard.
My critics to KoPI:
1. Size. The whole operation is not small, it's noticable. Putting them on QuickLaunch works on the startup speed, but somehow defeats the purpose of having a PDA.
2. Clutter. If I want to edit a calendar entry, I don't want to have tabs, because usually, I neither have attendees. Look at the Opie Calendar applet. That's the way it should work, because a PDA is not a PC. Setting the fonts to 'tiny' lessened the problem, but did not do away with it. Make a "Today" application. Much easier to keep everything on it. And then have seperate Todo and Calenda apps.
3 The installation process puts them into the wrong tab - use the provided Opie PIM tab, it works just as well as the custom one. And People don't go looking for it unless they're really motivated to use it.
KaPI:
1. Size.
2. The scrollbutton should be in the contantcs list at startup so I can use the cursor keys to select a name, and then use the center button to pop up all the information on that contact.
3. A new address? More tabs around than needed. Take a close look at the Opie Contacts application, it somehow worked out that problem.
1) can probably be solved by putting them into ROM and replacing the Opie PIMs completely. Since they share a thing or two, RAM usage can be alleviated.
For the others - remember that you're programming for a PDA, not a PC. Have a look at Konqueror/Embedded. The developers there got it almost right. What KaPI and KoPI are trying is to get a PC application running a 320x240 screen, and like my ancestry says "Son, this dog won't hunt.".
Also, people are interested in Turn-Key solutions. Basically, applets on the PDA and a syncing solution that will sync the whole data without having the user start shell scripts. KitchenSync was not too bad at it.
I could live with the Pi-Sync stuff one day, but you have to fix