Dave: We've gotten to the point where we are hitting the limits of the OEone UI design for calendar. I think we need to revist it, and I'm wondering how much time you've got over the next little while. I'd recommend you download and install our XPI, its had some great work done on it over the past week or two! Here's an issue that just popped up: The unifinder. (We took out categories by the way.) When someone clicks on an event, should it select all the repeating events in the right hand view? If so, when they hit Edit, which event are we editing, the first one? (We're running into a problem with exceptions to repeating events). I imagine we're going to have the same problem if we want to try and delete one occurence of the event. Let me know if you've got time for this bug.
I have some time (the next couple weeks look pretty good) :) We might be able to improve on this, here is how Outlook does it. 1) User selects an event that is recurring. Only that event gets selected. 2) The user opens the event, a dialog appears with the the following options: (x) Open this occurrence. ( ) Open the series. 3) Similarly, when the user tries to delete the event they get the following options: (x) Delete this occurrence. ( ) Delete the series. I'm going to get the latest calendar. Perhaps we could meet to come up with an initial list of areas to address.
I would like it if the unifinder displayed the next fifty (preferably user- definable) events starting at the beginning of the currently selected day. This would be the shown day in the day view or the selected day in week/month. Each occurance of an event would appear as a discrete event here. Opening one of these would allow for edit like normal but when hitting ok to confirm changes, a dialog box pops up: +------------------------------------------------+ | You have edited a repeating event. | | Apply the changes you have made to | | | | [*All* Occurances of this Event] | | | | [This Occurance and All *Following*] | | | | [The *Current* Occurance only] | | | | [Cancel] | +------------------------------------------------+ Where the *ed words are bold. This is similar (the wording is slightly different) to how PalmOS DateBook does it and makes sense to me. The buttons are long, and I'm not sure if that fits with good UI design, but that's my request.
The feature does add power to the product. It would allow some one to specify a range of time (say a month out of town) and change the events. It makes sense to decide on the exact UI design once all the requirements have been collected (it's painful to bolt them in or rip them out later). Does the Palm design make sense? Pros: - the buttons provide immediate access to the functionality (they are efficient) Cons: - they don't fit consistently with the use of buttons in the rest of the dialogs in Mozilla - they look bulky
Adding Mike Norton to cc: list. He wanted to stay in the loop regarding these changes.
We solved the problem for exceptions to repeating events by using the Evolution model for adding in exceptions. I don't think this is an issue any longer.
Default QA Contact for Calendar has changed. If you wish to remain the QA contact for this bug, feel free to change it back.
The bugspam monkeys have been set free and are feeding on Calendar :: Sunbird Only. Be afraid for your sanity!