MozillaWiki

Calendar:Deprecated:Feature Requirements/Roadmap Review: Difference between revisions

Calendar Discussion

Calendar:Deprecated:Feature Requirements/Roadmap Review (view source)

Revision as of 17:15, 26 July 2006

531 bytes removed ,  26 July 2006
m
Calendar:Feature Requirements/Roadmap Review moved to Calendar:Deprecated:Feature Requirements/Roadmap Review: Deprecating
m (sp)
 
 
(22 intermediate revisions by 15 users not shown)
Line 1: Line 1:
The current [http://www.mozilla.org/projects/calendar/requirements.html Calendar Feature Requirements] and [http://www.mozilla.org/projects/calendar/roadmap.html Roadmap] documents on the website seem to be a bit out of date.
'''THIS IS A DEPRECATED DOCUMENT'''


I've copied them here so we can edit them
= Calendar Feature Requirements (revision 2.0) =


-lilmatt
This document covers all the requirements, which we want to accomplish in the coming months and years. Please note, that this is not a roadmap. Since we currently lack active developers we have no timeframe for all the uncompleted features.


A lot of the functionalities have already been completed. These are shown as striked-through. The rest is either being worked on or needs developer attention. If you want to contribute to the project these tasks are your best way to get into it. Please see the FAQ and the developer guide for information on how to contribute to the project.


Calendar Feature Requirements (revision 2.0)
== Appearance & Performance ==
 
This document covers all the requirements, which we want to accomplish in the coming months and years. Please note, that this is not a roadmap. Since we currently lack active developers we have no timeframe for all the uncompleted features.


A lot of the functionalities have already been completed. These are shown as striked-through. The rest is either being worked on or needs developer attention. If you want to contribute to the project these tasks are your best way to get into it. Please see the FAQ and the developer guide for information on how to contribute to the project.
* New theme using new toolkit and Winstripe-style icons.
Table of Contents
* Review of calendar performance especially with large files.
* Support for archiving old events and tasks.


  1. Appearance & Performance
== Alarms==
  2. Alarms
  3. Associating
  4. Categories
  5. Exporting
  6. Events
  7. Importing
  8. Integration
  9. Invitations
  10. Multiple People
  11. Printing
  12. Remote Access
  13. Search
  14. Settings
  15. Synchronization
  16. To Do List
  17. Views
  18. Standalone Build (Sunbird)


1. Appearance & Performance
* The format of the alarm will be to open up a dialog window. The user will be able to dismiss the alarm, or snooze it for X number of minutes, days or hours, where X is an integer.
* Alarms give a snooze function (remind me in X minutes, snooze past event start, remember status when Calendar is turned off).
* Snoozing alarms should persist. If you snooze an alarm, and then shut Calendar down, it should remember that the alarm was snoozed.
* Alarms that have passed when calendar/sunbird was not running will go off on Calendar start-up.
* Alarms can be turned on or off per calendar.
* Alarms can be turned off globally.
* Alarms can be set X minutes, days or weeks before the event.
* The user should be able to snooze events for a certain time, and for a certain amount of time before the event. [Remind me again [___] (mins / hrs / days) (from now / before event)] PARTIALLY COMPLETE (just regular snooze)
* The user should be able to see all the alarms that have not gone off.


    * New theme using new toolkit and Winstripe-style icons.
== Associating ==
    * Review of calendar performance especially with large files.
    * Support for archiving old events and tasks.


2. Alarms - tracker bug
* Events can have locations assigned to them.
* Events can have notes or bookmarks attached to them.
* Calendar events can have files attached to them.
* Events can have attendees (contacts or mailing lists) associated to them (after Server support).
Alarm popup window shoud be always on top. (or should have been an option to set it)
Alarm for tasks work only for due date at the moment. When it is dismissed and I set a new due date the alarm is turned off.


    * The format of the alarm will be to open up a dialog window. The user will be able to dismiss the alarm, or snooze it for X number of minutes, days or hours, where X is an integer.
== Categories ==
    * Alarms give a snooze function (remind me in X minutes, snooze past event start, remember status when Calendar is turned off).
    * Snoozing alarms should persist. If you snooze an alarm, and then shut Calendar down, it should remember that the alarm was snoozed.
    * Alarms that have passed when PC has been off will go off on Calendar start-up.
    * Alarms can be turned off globally.
    * Alarms can be set X minutes, days or weeks before the event in the form of pop-up or email.
    * The user should be able to snooze events for a certain time, and for a certain amount of time before the event. [Remind me again [___] (mins / hrs / days) (from now / before event)] PARTIALLY COMPLETE (just regular snooze)
    * The user should be able to see all the alarms that have not gone off.
    * The user should be able to have multiple alarms for the same event. You could have one to remind you to prepare for the event, and another that the event is occurring.
    * Alarms must go off when calendar is not running.
    * Email that is sent out needs to be configurable (e.g include notes from event, "%user wrote:")


3. Associating - tracker bug
* Categories should be user-definable (add/edit/delete functions).
* Field to associate with any event (meeting, Address, Call, etc.) to a category. There could be some default categories (e.g., Family, Friends, Work, Clients, Subcontractor, Restaurants, Computer) or perhaps example category sets for different purposes (e.g. business, software development, education, single person, family)
* Events can be filtered based on categories.
* Events can be associated with multiple categories.
* Should be able to be colored based on differing categories


    * Events can have locations assigned to them.
== Exporting ==
    * Events can have notes or bookmarks attached to them.
    * Calendar events can have files attached to them.
    * Events can have attendees (contacts or mailing lists) associated to them (after Server support).


4. Categories - tracker bug
* Ability to export to another ICS file on file system or WebDAV folder.
* Ability to export only selected events.
* Export to HTML (pretty much the same as Print).


    * Categories should be user-definable (add/edit/delete functions).
== Events ==
    * Field to associate with any event (meeting, Address, Call, etc.) to a category. There could be some default categories (e.g., Family, Friends, Work, Clients, Subcontractor, Restaurants, Computer)
    * Events can be filtered based on categories.
    * Events can be associated with multiple categories.


5. Exporting - tracker bug
* Events can be added, edited or deleted and (if applicable) re-published via WebDAV.
* Events can be all-day events or even span multiple days.
* Events can be repeated every X days, weeks, months or years as well as on every X-day or Yth of each month.
* Repeating events can have exceptions applied to them.


    * Ability to export to another ICS file on file system or WebDAV folder.
=== Add / Edit / Delete Events ===
    * Ability to export only selected events.
    * Export to HTML (pretty much the same as Print).


6. Events - tracker bug
* The user must be able to add/edit/delete an event regardless of its location (local or remote) if they have enough permissions. PARTIALLY COMPLETE (no remote, requires calendar server)


    * Events can be added, edited or deleted and (if applicable) re-published via WebDAV.
=== Repeating events ===
    * Events can be all-day events or even span multiple days.
    * Events can be repeated every X days, weeks, months or years as well as on every X-day or Yth of each month.
    * Repeating events can have exceptions applied to them.


6.1. Add / Edit / Delete Events
* Events can repeat every X day, week, month or year.
* Events can repeat every week on certain days of the week, eg. Monday and Tuesday of every week.
* Events can repeat every day of a certain month and a certain date of every month. eg. 19th of every month, or 3rd Monday of every month.
* Users should be able to add exceptions to repeating events.


    * The user must be able to add/edit/delete an event regardless of its location (local or remote) if they have enough permissions. PARTIALLY COMPLETE (no remote, requires calendar server)
== Importing ==


6.2. Repeating events
* Import MS Outlook and other popular calendar data.
* Import other Mozilla calendar data (see 5 - Exporting).
* Import vCalendar data directly from clipboard


    * Events can repeat every X day, week, month or year.
== Integration ==
    * Events can repeat every week on certain days of the week, eg. Monday and Tuesday of every week.
    * Events can repeat every day of a certain month and a certain date of every month. eg. 19th of every month, or 3rd Monday of every month.
    * Users should be able to add exceptions to repeating events.


7. Importing - tracker bug
* Receiving an email invitation should bring the calendar up to prompt to import file.
* Finish integration with Thunderbird as an extension.
* Accept Outlook invitations.


    * Import MS Outlook and other popular calendar data.
== Invitations ==
    * Import other Mozilla calendar data (see 5 - Exporting).


8. Integration - tracker bug
* You should be able to email invitations to people to inform them and invite them to the event. (using WebDAV only)
* Guests will be alerted when the event is modified or deleted (Pop-up to offer re-notification). (needs Calendar Server support, see 10. Multiple People)
* Responses to invitations that come via email will prompt to import into the calendar.


    * Receiving an email invitation should bring the calendar up to prompt to import file.
== Multiple People ==
    * Finish integration with Thunderbird as an extension.
    * Accept Outlook invitations.


9. Invitations - tracker bug
* The calendar should be able to show other people's calendars, and let you edit events for other people with the proper permissions. (Completed using WebDAV only)
*Ability to store multiple calendars on a calendar server, options for the calendar software include:
**Sun Java System Calendar Server (formerly Sun's ONE calendar server )
**phpGroupWare
**eGroupWare
**OpenGroupWare.org (OSS version of Skylix)
**Exchange4Linux (formerly Bill's WorkGroup Server)
**WebCalendar


    * You should be able to email invitations to people to inform them and invite them to the event. (using WebDAV only)
== Printing ==
    * Guests will be alerted when the event is modified or deleted (Pop-up to offer re-notification). (needs Calendar Server support, see 10. Multiple People)
    * Responses to invitations that come via email will prompt to import into the calendar.


10. Multiple People - tracker bug
* Printing of day, week, month view with or without his calendar events as displayed on screen.
* Printing support for tasks together with categories, percentage complete and due dates.
* Print list of events with start and end dates, categories and locations.
* Print only what is defined by the drop down "View" menu or the current search.
* Option to leave out white space, i.e. Only print when I'm busy.


    * The calendar should be able to show other people's calendars, and let you edit events for other people with the proper permissions. (Completed using WebDAV only)
== Remote Access ==
    *


      Ability to store multiple calendars on a calendar server, options for the calendar software include:
* Users can access and subscribe to remote calendar files, re-publishing them with permission. (using WebDAV only)
          o Sun's ONE calendar server
          o phpGroupWare
          o eGroupWare
          o OpenGroupWare.org (OSS version of Skylix)
          o Exchange4Linux (formerly Bill's WorkGroup Server)


11. Printing - tracker bug
== Search ==


    * Printing of day, week, month view with or without his calendar events as displayed on screen.
For saved searches, see the 17. Views which enables the "View" drop down menu
    * Printing support for tasks together with categories, percentage complete and due dates.
    * Print list of events with start and end dates, categories and locations.
    * Print only what is defined by the drop down "View" menu or the current search.
    * Option to leave out white space, i.e. Only print when I'm busy.


12. Remote Access - tracker bug
* The user should be able to do a simple (quick) search for events.
* Search facility from toolbar allowing quick search based on title, location and description (notes).
* The user should not have to press a search button, it should search automatically after a certain period of time has elapsed since typing.
* The user should be able to do an advanced search for events (design done).
* Pop-up window to enable advanced search by selection of what fields to search in (including time and date). [Design already done]


    * Users can access and subscribe to remote calendar files, re-publishing them with permission. (using WebDAV only)
== Settings ==


13. Search - tracker bug
* Options to configure start of week, hours in day and alarm defaults (as well as others).
* Option to pick colours for each calendar.
* You should be able to see the week number.
* Ability to set text colour for calendars as well as highlight colour.
* Setting dialog needs updating to new style (see Firefox and Thunderbird as examples).


For saved searches, see the 17. Views which enables the "View" drop down menu
== Synchronization ==


    * The user should be able to do a simple (quick) search for events.
* Sync data with mobile devices:
    * Search facility from toolbar allowing quick search based on title, location and description (notes).
** Palm Pilot (custom format)
    * The user should not have to press a search button, it should search automatically after a certain period of time has elapsed since typing.
** Pocket PC (runs Outlook PocketPC version)
    * The user should be able to do an advanced search for events (design done).
** Nokia mobile phones (format?)
    * Pop-up window to enable advanced search by selection of what fields to search in (including time and date). [Design already done]
** Sony Ericsson mobile phones (format? - java based)
** Apple iPod (uses ics) [raccettura [http://robert.accettura.com/archives/2005/11/07/ipod-sync/ started work]]


14. Settings - tracker bug
SyncML support will help a bit. Try Sync4j support http://www.funambol.com/opensource/


    * Options to configure start of week, hours in day and alarm defaults (as well as others).
This software might work: Sync4jmozilla http://sourceforge.net/projects/sync4jmozilla
    * Option to pick colours for each calendar.
    * You should be able to see the week number.
    * Ability to set text colour for calendars as well as highlight colour.
    * Setting dialog needs updating to new style (see Firefox and Thunderbird as examples).
    * Change all preferences to be stored under MozillaCalendar rather than below Mail or Thunderbird.


15. Synchronization - tracker bug


    * Sync data with mobile devices:
How about motorola or some java for phone application?
          o Palm Pilot (custom format)
          o Pocket PC (runs Outlook PocketPC version)
          o Nokia mobile phones (format?)
          o Sony Ericsson mobile phones (format?)
          o Apple iPod (uses ics) [DIGITALgimpus started work]


16. To Do List - tracker bug
== To Do List ==


    * Sidebar for displaying to do task list.
* Sidebar for displaying to do task list.
    * Alarms for to do tasks.
* Alarms for to do tasks.
    * To do list for simple tasks.
* To do tasks should be searchable (see 13 - Search)
    * To do tasks should be searchable (see 13 - Search)
* To do tasks should appear in main view, if global option is set.
    * To do tasks should appear in main view, if global option is set.
* To do tasks comment-textfield should be larger
    * To do list should be viewable by category, due date and percentage completed.
* To do list for simple tasks.
* To do list should be viewable by category, due date and percentage completed.
* To do list should be viewable as tree (by category, due date and percentage completed).


17. Views - tracker bug
== Views ==


    * Day, week, multi-week and month views, supporting resizing and multiple events at one time.
* Day, week, multi-week and month views, supporting resizing and multiple events at one time.
    * List of all events, configured by View or Search options.
* List of all events, configured by View or Search options.
    * The month view should show the trailing/following days of the previous/next month, not just the days of the current month.
* The month view should show the trailing/following days of the previous/next month, not just the days of the current month.
    * Show a work week view which shows a user specified amount of days (some people work Mon - Fri, others work Tue - Sat).
* Show a work week view which shows a user specified amount of days (some people work Mon - Fri, others work Tue - Sat).
    * In-line editing for events in both list view and calendar view.
* In-line editing for events in both list view and calendar view.
    * Drop down "View" menu should be configurable (as in Thunderbird/Mail) and provide Save option.
* Drop down "View" menu should be configurable (as in Thunderbird/Mail) and provide Save option.


17.1. Day View / Week View
=== Day View / Week View ===


    * When switching to day view, it should scroll until a certain time is at the top (like 8 AM).
* When switching to day view, it should scroll until a certain time is at the top (like 8 AM).
    * Events that occur at the same time as each other should still be shown (ie. be squished side by side).
* Events that occur at the same time as each other should still be shown (ie. be squished side by side).
    * You should be able to double click on an hour and then have the new event dialog pop up for that time.
* You should be able to double click on an hour and then have the new event dialog pop up for that time.
    * Day view - Configurable hours in day.
* Day view - Configurable hours in day.
    * Week view - Monday to Friday support for Week view.
* Week view - Monday to Friday support for Week view.
    * You should be able to delay double click on an hour and then have an inline edit box pop up for easy and quick calendar adding.
* You should be able to delay double click on an hour and then have an inline edit box pop up for easy and quick calendar adding.
The actual day should be always marked in every view. (now it is only in month view)


17.2. Month View
=== Month View ===


    * It should be able to be resized to any width and height.
* It should be able to be resized to any width and height.


17.3. MultiWeek View
=== MultiWeek View ===


    * Multiweek view should display a grid of days (similar to month view).
* Multiweek view should display a grid of days (similar to month view).
    * Multiweek view should display weeks relative to current week (not current month).
* Multiweek view should display weeks relative to current week (not current month).
    * Multiweek view should display T weeks total, where T is a user settable preference.
* Multiweek view should display T weeks total, where T is a user settable preference.
    * Multiweek view should display P previous weeks, where P is a user settable preference.
* Multiweek view should display P previous weeks, where P is a user settable preference.


18. Standalone Build (Sunbird)
== Standalone Build (Sunbird) ==


    * Make standalone build compile from the mozilla trunk.
* Make standalone build compile from the mozilla trunk.
    * Make standalone build really standalone (resolve the dependency on building it on top of Mozilla Firefox.
* Make standalone build really standalone (resolve the dependency on building it on top of Mozilla Firefox.
    * Complete the artwork/theme in standalone build.
* Complete the artwork/theme in standalone build.
    * Resolve integration issues (mail and browser integration)
* Resolve integration issues (mail and browser integration)






Mozilla Calendar Roadmap
= Mozilla Calendar Roadmap =


This page documents our goals and feature requirements for our upcoming releases. Since we currently lack active developers, no timeframe for upcoming releases can be given.
This page documents our goals and feature requirements for our upcoming releases. Since we currently lack active developers, no timeframe for upcoming releases can be given.


For a more thorough overview of our completed and uncomplete features, please visit our Feature Requirements page.
For a more thorough overview of our completed and uncomplete features, please visit our Feature Requirements page.
Calendar 0.9 - "Almost there..."
 
== Calendar 0.9 - "Almost there..." ==


Items to resolve:
Items to resolve:


    * 1. Appearance & Performance - New theme; Ability to archive old events and tasks.
* 1. Appearance & Performance - New theme; Ability to archive old events and tasks.
    * 3. Associating - Events can have files attached to them.
* 3. Associating - Events can have files attached to them.
    * 4. Categories - Events can have multiple categories.
* 4. Categories - Events can have multiple categories.
    * 5. Exporting - Export to HTML
* 5. Exporting - Export to HTML
    * 8. Integration - Complete integration with Thunderbird.
* 8. Integration - Complete integration with Thunderbird.
    * 11. Printing - Support for printing To do tasks; Support for printing list of events.
* 11. Printing - Support for printing To do tasks; Support for printing list of events.
    * 14. Settings - Option to set text colour for calendars; New independent preference folder.
* 14. Settings - Option to set text colour for calendars; New independent preference folder.
    * 16. To do - Tasks to appear in main view (if option set); Filter views by category, date due...
* 16. To do - Tasks to appear in main view (if option set); Filter views by category, date due...


Calendar 1.0 - "Finally!"
== Calendar 1.0 - "Finally!" ==


Items to resolve:
Items to resolve:


    * 1. Appearance & Performance - Performance increase especially when dealing with large files.
* 1. Appearance & Performance - Performance increase especially when dealing with large files.
    * 2. Alarms - Configurable email; Alarms triggered when Thunderbird/Mail only is running.
* 2. Alarms - Configurable email; Alarms triggered when Thunderbird/Mail only is running.
    * 8. Integration - Accept Outlook invitations.
* 8. Integration - Accept Outlook invitations.
    * 11. Printing - Option to leave out white-space; Print only results from search or "View" filter.
* 11. Printing - Option to leave out white-space; Print only results from search or "View" filter.
    * 13. Search - Pop-up window for advanced search.
* 13. Search - Pop-up window for advanced search.
    * 14. Settings - Change settings dialog to new style and theme.
* 14. Settings - Change settings dialog to new style and theme.
    * 16. To do - Search facility.
* 16. To do - Search facility.
    * 17. Views Drop down "View" filter menu should be configurable.
* 17. Views Drop down "View" filter menu should be configurable.


Plans for the time after 1.0
== Plans for the time after 1.0 ==


We will branch into 1.0 and 2.0 trees which are developed concurrently
We will branch into 1.0 and 2.0 trees which are developed concurrently


Branch 1.0 will probably follow this release plan:
Branch 1.0 will probably follow this release plan:
1.1: Bug Fixes
*1.1: Bug Fixes
1.2 - 1.4: Beta Releases of Stand alone build, Sunbird
*1.2 - 1.4: Beta Releases of Stand alone build, Sunbird
1.5 - 1.1: Build re-release as stand alone build, Sunbird
*1.5 - 1.1: Build re-release as stand alone build, Sunbird


Branch 2.0 will probably follow this release plan:
Branch 2.0 will probably follow this release plan:
1.6 - 1.7: Alpha Releases of next generation release
*1.6 - 1.7: Alpha Releases of next generation release
1.8 - 1.9: Beta Releases of next generation release
*1.8 - 1.9: Beta Releases of next generation release
2.0: Release of next generation calendar, both as extension and stand-alone build
*2.0: Release of next generation calendar, both as extension and stand-alone build
Calendar 2.0
 
== Calendar 2.0 ==


Items to resolve before a 2.0 release:
Items to resolve before a 2.0 release:


    * 9. Invitations - Guests will be alerted when events changed; responses automatically imported.
* 9. Invitations - Guests will be alerted when events changed; responses automatically imported.
    * 10. Multiple People - Support for various calendar servers.
* 10. Multiple People - Support for various calendar servers.
    * 15. Synchronization - Support for sync with mobile devices.
* 15. Synchronization - Support for sync with mobile devices.
    * 17. Views - In-line editing for events in both list view and calendar view.
* 17. Views - In-line editing for events in both list view and calendar view.
    * 18. Standalone Build - Full support; as feature complete and as stable as Calendar
* 18. Standalone Build - Full support; as feature complete and as stable as Calendar
 
Tray notification should be part of sunbird.
 
 
'''THIS IS A DEPRECATED DOCUMENT'''
Lilmatt
441

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/3089...29958"