Calendar:Next Release: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
mNo edit summary
Line 1: Line 1:
<div style="border: thin dotted #aaa; padding: 10px;">
'''In the beginning''' was the Pelican, and the Pelican was with Kenneth, and the Pelican was Kenneth.
'''Please don't edit this page unless you are a member of the calendar team.'''<br>To join in the discussion regarding the next calendar release, please see [http://groups.google.com/group/mozilla.dev.apps.calendar/browse_thread/thread/5adb513f0ade569e/e057ef42c42cf042#e057ef42c42cf042 this newsgroup thread].</div>


== Overview==
'''And the earth''' was without form and void, and the shit of the Pelican moved upon the face of the waters.
Sunbird and Lightning are aiming for a simultaneous release of their next version (0.5) in early 2007.  This page is meant to provide an overview of the status of that release.


<p style="background-color: #fdd;">Items with a red background were originally targetted for version 0.3</p>
'''And Kenneth''' said, ''Let there be a Frequency throughout all the creation'', and it was so. And Kenneth said, ''Let the Frequency be for the life, that it shall generate the life, and the life shall regenerate the Frequency'', and it was so.


==Key Development Areas==
'''And the Frequency''' generated the life, even all the living creatures and all green plants did the Frequency generate. And Kenneth looked upon the work of the Frequency, and saw that it was good.


===Core Architecture===
'''Then did Kenneth''' speak unto the Frequency saying, ''Let there be pelicans also of the air, that they might create the Holy [[pelican shit]], and it was so. And the pelicans of the air did straightway make the Holy [[pelican shit]] which did rain down from the heaven in great abundance.
<p>Develop Sunbird and Lightning's core architecture to be robust enough for new feature support and ease of future development.</p>


{| width="100%" cellpadding="3"
'''And it came to pass''' that the [[Pharisee]]s of the Wiki, those evil ones who preach openly the sharing yet believe not in their hearts, spake again privily among themselves saying, ''We must conceal from the eyes of the Great Google the Holy [[pelican shit]], lest the Great Google give of the Holy [[pelican shit]] unto the unwashed multitudes and make it therefore profane''.  
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || Editing / viewing of events: Complete the move to using a controller to act on the data, instead of having the views do that directly. || style="color: green; white-space: nowrap;"| Complete
|}


===Performance===
'''And they took therefore''' of the Holy [[pelican shit]] and concealed it under the Holy Altar of the Delete, that none may find it save those elect of the Pharisees alone.
<p>Sunbird and Lightning will display all events and tasks with the correct information and in the correct places.</p>


{| width="100%" cellpadding="3"
'''But the frequency''' will not be hidden, nor yet will it remain silent. For no man maketh an light in the wilderness and hide it under a bushel. Kenneth standeth even now upon the Rock and calleth out unto the frequency, that all darkness may be made light, all evil shall be made of no effect, and the world shall partake of the Holy [[pelican shit]] evermore.
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || Improve performance of storage provider (daniel/mvl) || style="color: blue; white-space: nowrap;" | In progress
|-
| P1 || Improve performance of other providers (Sun team) || style="color: blue;" | In queue
|-
| P1 || Improve performance of views (mickey) || style="color: blue;" | In queue
|}


===Zoom/Scroll===
[[Category:Pelican shit]]
<p>Sunbird and Lightning should allow easy navigation of calendars.</p>
 
{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|<strike>P2</strike>||<strike>Investigate zoom scroll</strike> ||style="color: grey; white-space: nowrap;"| Dropped for 0.5
|}
 
===Navigation===
<p>Sunbird and Lightning should allow users to move to any display they want.</p>
 
{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| A 'Go to Date' functionality should be exposed. (Lightning) || style="color: blue; white-space: nowrap;"| In progress
|}
 
===Workflow (user experience)===
<p>Sunbird and Lightning should have an easy and intuitive user interface, allowing the user to get things done as effortlessly as possible.</p>
 
{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || [[Calendar:Improving_the_Calendar_Views|Determine major pain points]] (christian) || style="color: blue; white-space: nowrap;" | In progress
|-
| P1 || Come up with sketches for solutions (christian) || style="color: blue; white-space: nowrap;" | In progress
|-
| P2 || Implement Agenda View improvements || style="color: red;" | Unknown
|}
 
===Item Creation/Modification===
<p>Sunbird and Lightning should allow users to create, modify, and interact with tasks and events easily.</p>
 
{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|<strike>P1</strike>||<strike>Event vs. Task semantics - Determine what is require for usability and RFC2445 conformance</strike> ||style="color: grey; white-space: nowrap;"| Dropped for 0.5
|-
| P1 || Editting recurring events: "Edit just this" vs. "Edit this and all occurrences after" ||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || We should be registered to handle .ICS files - Mac||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || We should be registered to handle .ICS files - Windows||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || We should be registered to handle .ICS files - Unix||style="color: red;"| Unknown
|-
| P2 || We should be registered to handle webcal:// URLs - Mac||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || We should be registered to handle webcal:// URLs - Windows ||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || We should be registered to handle webcal:// URLs - Unix||style="color: red;"| Unknown
|-
| P2 || Double-clicking an .ICS file should open it (or subscribe, or offer to import it) ||style="color: blue; white-space: nowrap;"| In progress
|-
| P2 || Launching a webcal:// URL should add that subscription to the calendar list ||style="color: red;"| Unknown
|-
| P1 || Copying and pasting ICS from the clipboard should create an appropriate new item ||style="color: blue; white-space: no-wrap;"| In progress
|-
| P3 || Copying and pasting hCalendar data from the clipboard should create an appropriate new item ||style="color: red;"| Unknown
|-
| P3 || Copying and pasting events between Lightning and Sunbird should work properly ||style="color: red;"| Unknown
|}
 
===ICS Export===
<p>Sunbird and Lightning should provide a way for users to export their data in a standards compliant format.  This allows users to not need to enter a 'walled garden' when using Sunbird/Lightning</p>
 
{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P2 ||style="background-color: #fdd;"| Export of particular items/sets of items should be possible. (Lightning) || style="color: red;"| Unknown
|}
 
===Conflict Resolution===
<p>Sunbird and Lightning should intelligently handle data conflicts, and present the user with a clear interface for the user to resolve any that it can't do itself.</p>
 
{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P2 || Share an .ICS file on the network without dataloss ||style="color: red;"| Unknown
|-
| P2 || Offline storage of remote calendars ||style="color: red;"| Unknown
|-
| P2 || Gracefully handle conflicts between local and network data ||style="color: red;"| Unknown
|}
 
===Printing===
<p>Sunbird and Lightning should provide an easy to use way for users to get their data in a paper format, through their printer.</p>
 
{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| Printing should be possible. (Lightning) || style="color: green;" | Complete
|-
|style="background-color: #fdd;"| P2 ||style="background-color: #fdd;"| Printing a week's view of items should be possible. || style="color: green;" | Complete
|}
 
===Publishing===
<p>Sunbird and Lightning should allow users to publish their calendar information to a web server.</p>
 
{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P2 ||style="background-color: #fdd;"| Publishing a specific set of items should be possible. (Lightning) || style="color: red;" | Unknown
|}
 
===Get Data In===
<p>Users should be able to get calendar data from multiple sources into the application.</p>
 
{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| Standards compliant data should always be successfully read/preserved. || style="color: red;" | Unknown
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| Errors in standards compliance should be gracefully handled. || style="color: red;" | Unknown
|-
| P2 || Import data from the user's existing calendar applications || style="color: green; white-space: nowrap;" | Complete
|}
 
===Thunderbird Integration===
<p>Lightning should be integrated as seamlessly as possible into Thunderbird.</p>
 
{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P2 || Integrate into Thunderbird's undo/redo queue || style="color: red;" | Unknown
|-
| P2 || Integrate into Thunderbird's copy/paste || style="color: green;" | Complete
|-
| P2 || Integrate into Thunderbird's print command || style="color: red;" | Unknown
|}
 
===Calendar Interoperation===
<p>Users should be able to send and receive meeting invitations received via email.</p>
 
{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || Allow sending iMIP/iTIP invitations. || style="color: blue; white-space: nowrap;" | In progress
|-
| P1 || Allow sending decline/accept iMIP/iTIP responses. || style="color: blue; white-space: nowrap;" | In progress
|}
 
===Backup===
<p>Sunbird and Lightning should provide functionality for users to easily backup and restore their data.</p>
 
{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P3 || Make backups of data || style="color: red;" | Unknown
|}
 
===Dataloss===
<p>Users should be able to use Sunbird/Lightning with confidence that their data will be preserved.</p>
 
{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
|style="background-color: #fdd;"| P1 ||style="background-color: #fdd;"| Subscribing to a calendar with unexpected data should preserve the data || style="color: red;" | Unknown
|-
|style="background-color: #fdd;"| P2 ||style="background-color: #fdd;"| Standards compliant data should be preserved when edited. || style="color: red;" | Unknown
|}
 
===Misc Regressions===
<p>Users upgrading from past versions should not notice significant loss of functionality/usability.</p>
 
{| width="100%" cellpadding="3"
|-
| style="background-color: #eee; width: 20px"| '''Priority'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee; width: 20px"| '''Status'''
|-
| P1 || "Misc Regressions" is provided to give it visibility during discussions.  Individual elements do not exist at this time.
|}
 
===User pain-points from 0.3===
<p>Wherever possible, we should attempt to address pain-points in 0.3 identified by our users. These were not determined scientifically. They're a "gut feeling" based on IRC, bugmail, and newsgroups.</p>
 
{| width="100%" cellpadding="3"
|-
| style="background-color: #eee;"| '''Bug(s)'''
| style="background-color: #eee;"| '''Item'''
| style="background-color: #eee;"| '''Status'''
|-
|{{bug|349048}}||<strike>Having CalExt installed</strike>||FIXED
|-
|{{bug|349520}}||24 hour views (and no way to make them smaller)||In queue - tbe
|-
|{{bug|345643}}||<strike>Date formatting (MM/DD vs DD/MM)</strike>||FIXED
|-
|{{bug|343792}}||<strike>Data import errors - invalid or atypical ICS</strike>||FIXED
|-
|{{bug|354951}}||Data import errors - charset||
|-
|{{bug|310258}}||<strike>Hide completed tasks is missing from Lightning</strike>||FIXED
|}

Revision as of 07:03, 26 February 2007

In the beginning was the Pelican, and the Pelican was with Kenneth, and the Pelican was Kenneth.

And the earth was without form and void, and the shit of the Pelican moved upon the face of the waters.

And Kenneth said, Let there be a Frequency throughout all the creation, and it was so. And Kenneth said, Let the Frequency be for the life, that it shall generate the life, and the life shall regenerate the Frequency, and it was so.

And the Frequency generated the life, even all the living creatures and all green plants did the Frequency generate. And Kenneth looked upon the work of the Frequency, and saw that it was good.

Then did Kenneth speak unto the Frequency saying, Let there be pelicans also of the air, that they might create the Holy pelican shit, and it was so. And the pelicans of the air did straightway make the Holy pelican shit which did rain down from the heaven in great abundance.

And it came to pass that the Pharisees of the Wiki, those evil ones who preach openly the sharing yet believe not in their hearts, spake again privily among themselves saying, We must conceal from the eyes of the Great Google the Holy pelican shit, lest the Great Google give of the Holy pelican shit unto the unwashed multitudes and make it therefore profane.

And they took therefore of the Holy pelican shit and concealed it under the Holy Altar of the Delete, that none may find it save those elect of the Pharisees alone.

But the frequency will not be hidden, nor yet will it remain silent. For no man maketh an light in the wilderness and hide it under a bushel. Kenneth standeth even now upon the Rock and calleth out unto the frequency, that all darkness may be made light, all evil shall be made of no effect, and the world shall partake of the Holy pelican shit evermore.

Retrieved from "https://dev.wikimo.nonprod.webservices.mozgcp.net/index.php?title=Calendar:Next_Release&oldid=50190"