367893 - Moving features from prototype event dialog to core event dialog

Status: RESOLVED WORKSFORME

(Calendar :: General, enhancement)

Description

[cmtalbert]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a2pre) Gecko/20070122 Calendar/0.6a1

This is a placeholder bug for the features we would like to move from the prototype event dialog bug to the core event dialog in the 0.5 release timeframe.

Because this is an evolving design, I do not want to post preliminary information here, but I needed this bug to dupe against.

Please see the newsgroup link above for the full discussion.

Reproducible: Always

Steps to Reproduce:
1.Use core dialog -- works ok
2.Use nifty features of prototype

Actual Results:  
Disappointed about not having the new features in the core dialog.

Expected Results:  
Want some of the nifty features in the core dialog.

Comment 2

[David Gessel]

Is it possible to attach a screen shot of the prototype UI for the event dialog?

Comment 3

[Michael Büttner (no reviews TFN)]

The full specification can be found at http://wiki.mozilla.org/Calendar:SMB_Event_Dialog

Some more screen shots can also be found at the calendar blog [http://weblogs.mozillazine.org/calendar] from last week - "Calendar Sneak Preview Part 1 - The event dialog".

Please also note that the implementation is already fully functional and can be enabled by setting the "calendar.prototypes.wcap"-pref to true.

Comment 4

[David Gessel]

could we consider something like
http://www.black-rose.org/sunbird/event1b.png
The pop-up menu should have a list of "favorites" rather than a list of all time-zones.  There should be an option for "other" which would bring up a graphic time-zone picker and favorites list manager and allow new favorites to be added to the list (and old favorites to be removed)

The key issue is supporting easy scheduling of flights that cross time zones.  The departure and arrival times are usually reported in local time, and are therefore different.  

I'd think the default behavior would be to link the start time zone with the end timezone and only unlink them if one explicitly sets the end time zone differently.

Comment 5

[Stefan Sitter [:ssitter]]

The former (prototype) dialog has completely replaced the (former) core dialog for some time now, see Bug 403886. Therefore this bug isn't needed anymore.