I'll qualify everything by saying Leopard's is the first version of
iCal I've tried to use, having come from many years with Palm Desktop.
For local only? Sure. But for Server calendars? How do I, with one
user ID
have separate calendars for meetings with my Boss vs. Lunch dates
vs. events
related to my son vs. doctors appointments vs. etc., yadda?
We seem to have this running OK here (if I'm not misunderstanding what
you're trying to do).
To simplify things, we created a separate user (schedules) and we get
everyone to add this as a user - this avoids us having to have
multiple accounts listed for each user. We then simply set up a
(server) calendar for each of the categories required on the
'schedule' user. If someone want to have a personal calendar they
simply set it up on their own account on the server (or locally). Of
course, we're NOT using invites/appointments etc so YMMV.
It's hard to hit the widget right, and why would I want to set up an
event
on a calendar and ONLY enter the name? That's the default. You only
enter
the name. Kind of useless. It's an event that one can reasonably
assume
needs more information than a title. What great advantage is there
in making
me do extra work?
Have to agree with this - the general usability is pretty poor (as is
the aesthetics). I hate the way you double click an event, and then
have to click an 'edit' widget to edit something. Seems like poor GUI
to me but I'm sure others will disagree. Palm you just double clicked
and could do pretty much everything there. Also don't like the fact
it doesn't have 'weekday only' support for repeating events but I'm
probably getting a little picky.
If you only ever need one calendar, and have very simple needs, iCal
is
okay. If you have a more complicated calendaring/groupware life, it
kind of
blows.
you're probably right but at least we have shared calendaring working
now which we didn't have a few months ago - for that I'm thankful.
