Mimi Yin wrote:
I am forwarding this bug to the Dev-List as I think it's an important
usability issue we should address in the web UI for 1.0:
*Background:*
In the interest of performance, we currently only look 1 month into
the future when loading recurring events into the Triage Table in the
Chandler Hub web UI.
This means that the web UI won't display a recurring event under the
following circumstances:
1. the recurring event *starts* more than 1 month into the future
2. you have deleted the next occurrence, creating a recurrence gap of
more than 1 month
3. the recurring event recurs at an interval more than 1 month apart
(e.g. annually recurring holidays)
Given that we will be shipping 1.0- Desktop with a shared U.S.
Holidays calendar, out of the box, I think we need to make it so that
at least Scenario #3 works well in the web UI.
From Randy's comment below, it seems the amount of work required to
correctly load "the next occurrence of a recurring event series" for
all 3 scenarios is out of scope for 1.0
However, we can implement a smaller change that would take annually
recurring events and look 1 year into the future to find the next
occurrence.
*Randy, even though Chandler doesn't support bi-monthly and bi-annual
recurrence rules. We do support importing them. Would it be possible
to simply expand this exception to include any recurring events that
have a recurrence rule of more than 1 month?*
Its possible, its just a matter of checking for different recurrence rules.
Is this an accurate summary Randy?
Yes, very. We can also try to make #1 work a little better by searching
further in to the future for recurring events. In fact I think we can
get all 3 scenarios somewhat working for 1.0 using the current apis.
-Randy
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
