Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'iCal 3 is a disaster' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
iCal 3 is a disaster
Authored by: loren_ryter on Nov 21, '07 04:54:02AM

Hate to be piping this all over but iCal 3 is a total disaster. It is a major step down in terms of productivity and not just because of the drawer issue. The major show stopper is that it responds to AppleEvents up to 20 times slower than iCal 2 on Leopard. One of the Mac's big advantages is the integrated application aspect of it. iCal is not the greatest calendar program, but the promise of being able to DO THINGS with your information outside of iCal is a big one. Leopard killed that. Any attempt to interact with iCal data via AppleEvents, if your iCal database is big enough, results in a permanent iCal hang. Plus the major under the hood problems have not been resolved -- the way iCal deals with recurring events involves parsing a recurrence string.



[ Reply to This | # ]
iCal 3 is a disaster
Authored by: scott_a_m on Nov 22, '07 04:12:49AM

I understand your frustration with existing code that uses Apple Events.

However, Leopard introduces the CalendarStore framework, which gives access to iCal's underlying data directly, and is far, far quicker. So while existing code may have slowed down, developers should be able to start migrating to incorporate even faster access to the data using a more direct route.



[ Reply to This | # ]