Date: 19/12/2006
| I had a read of the iCalendar RFC and decided that my previous recurring UI attempt was not flexible enough, and so I redesigned the UI somewhat. This is a shot from my UI builder, obviously it'll be nicely laid out at runtime:
This time around I've added more control, although I think it's harder to understand what everything does. Basically I'm trying to expose these fields:
Rule:
freq = [daily, weekly, monthly, yearly]
repeat = [int]
by day = [mon,tues,wed,thur,fri,sat,sun]
by month = [1,12]
by year = [year,...]
by pos = [int]
End:
none
date = [dd/mm/yyyy]
count = [int]
Basically the first 2 fields, "freq" and "repeat" generate a list of days, which then gets limited by the "By Day", "By Month", "By Year" and "By Pos" fields.
So if you wanted all the fridays in Feb, you would set Freq=Day, Repeat=1, ByDay=Fri, ByMonth=Feb.
If you wanted the 3rd Saturday in every month, StartDate=a saturday, Freq=Week, ByPos=3
Can you think of some important cases that aren't covered by this UI?
|
exosceleton 18/12/2006 12:14pm
| "So if you wanted all the fridays in Feb, you would set Freq=Day, Repeat=1, ByDay=Fri, ByMonth=Feb."
why would freq be Day, not week?
i'm sure it's correct but it is harder to understand (as you said).
But i think it will all make more sense once one can actually see the result, and try a few.
and a few examples in the help file would help a lot, there are not that many variations. |