I tried creating a new test calender in O2K and added one or two items to it. I told KO/Pi to import the entries from the new calender and it works fine. What suggestion can you make for a next step?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=82932\"][{POST_SNAPBACK}][/a][/div]
What are you trying to accomplish, exactly?
The redraw issue is due to the anemic processor in the Zaurus. Sharp calendar is fast simply because it's very simple. I suppose thats the case with Qalendar as well, though I haven't tried it.
I don't think the blame for the lack of speed can be placed squarely on the processor - most of it seems to come from the OS side.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=83004\"][{POST_SNAPBACK}][/a][/div]
It's a combination of silly processor, silly kernel, and kdepim/pi being a silly high level graphical app.
After seeing some of the latest Palm devices the other day, I decided to pull out my old Clie SJ30 - a Dragonball ~200Mhz (?) based palm - and was amazed at how fast even the older model switched between applications, and how fast the calendar apps quickly switched between views. Granted the resolution might only be half of the Z, and perhaps the featureset might be smaller (though I find Agendus quite capable).
Look at the Palm PIM apps. They don't draw much at all.
It's true that Sharp's default calendar and Qualendar don't have quite as many features as KO/Pi, and hence might be considered 'simple'. However, I don't think there's anything necessarily wrong with 'simple' - especially in a PDA, which is how I generally use my Zaurus.
Totally agree. Part of why the Palm apps are very good is because they make very smart feature/functionality/interface compromises. I'd say they maintain about 70%-80% of the kdepim functionality with 20% the interface weight. Pretty impressive, IMHO.
Also, does having more features mean that a program should run slower? Isn't that usually referred to as bloat?
Depends. I think bloat is a combination of feature creep combined with an interface that allows those features to get in the way of the average user. Kdepim is bloated, but not overly so: it catters to a different crowd that the Palm and Windows Mobile devices.
Don't get me wrong, I really like KO/Pi... I just wish it was snappier.
Can't argue with you there but Lutz has been making decent progress in that department. Try and go back to the early version: they're litteraly painful to use.
Kdepimpi is just completely graphic: until the Linux pocket devices pack 3D-accelerators and a hardware-accelerated compositor+renderer, they'll never be as snappy as simple PDA-only apps.
That said, if you (or anyone else for that matter) have concrete suggestions, I'm always more than ready to examine and discuss them. A good idea's a good idea, doesn't matter where it comes from.
