Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

Task #4314 (closed)

Opened 13 years ago

Closed 13 years ago

Last modified 12 years ago

2nd round Calendar Investigation Trac Timeline-Images Tab

Reported by: saloynton Owned by: jburel
Priority: minor Milestone: OMERO-Beta4.3
Component: General Version: n.a.
Keywords: n.a. Cc: atarkowska, jburel, wmoore
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: n.a.
Sprint: 2011-02-24 (6)

Description (last modified by saloynton)

A further more specific investigation of application only calendar will be considered. This has been implemented because of the differences in the range of web based calendar applications that in many cases would not be applicable to a standard application.

The initial selection of apps that have been singled out:

  • Thunderbird with Lightning.
  • iCal.
  • Rainlendar.
  • Facebook (event driven calendar view).
  • OMERO Web mobile.

UPDATE: The items highlighted in bold are completed in the document attached.

UPDATE: The remaining two apps have been reviewed. The one aspect raised in the discussion of the work was the advantage of an event driven calendar view. This removed the need to fully implement a calendar and so face the challenge of making it compatible with other existing calendars. As well facing the challenge of forcing users to adopt a new calendar.

  • The general finding from the minor investigation was the event driven calendar based feed might be a more suitable technique of presenting calendar history. With large amount of information, a key challenge is ensuring a suitable selection of information filters.

NOTE: Before ticket closed need to check where the priority is for the work and if more suitable to pick up later?

Conclusion
The conclusion for the work is that for key requirement identified for Calendar functionality is that it will move forward adopting the model of the event driven feed to manage the user history.

This is to prevent the requirements for the calendar functionality of becoming over complex and over bloated. This is due to the functionality of the traditional calendar. In the inclusion of the traditional calendar it introduces the problem of dealing with the use for planning daily schedule and for planning the next few months. This is not required for the calendar functionality.

Based on this the web mobile application can be used to explore the functionality. The ticket has been created #4425 (Update gretzky with webmobile) to allow the user testing with the mobile client to explore the feedback interface.

Attachments (2)

Application based apps only of calendar functionality.docx (1.0 MB) - added by saloynton 13 years ago.
Screen shots of apps only of calendar/event driven functionality
Application based apps only of calendar functionality.2.docx (1.9 MB) - added by saloynton 13 years ago.

Change History (17)

comment:1 Changed 13 years ago by saloynton

  • Description modified (diff)

comment:2 Changed 13 years ago by saloynton

  • Status changed from new to accepted

comment:3 Changed 13 years ago by saloynton

  • Owner saloynton deleted
  • Status changed from accepted to new

Changed 13 years ago by saloynton

Screen shots of apps only of calendar/event driven functionality

comment:4 Changed 13 years ago by saloynton

  • Description modified (diff)

comment:5 Changed 13 years ago by saloynton

  • Owner set to saloynton

comment:6 Changed 13 years ago by saloynton

comment:7 Changed 13 years ago by saloynton

  • Status changed from new to accepted

comment:8 Changed 13 years ago by saloynton

  • Description modified (diff)

comment:9 Changed 13 years ago by saloynton

  • Owner saloynton deleted
  • Status changed from accepted to new

comment:10 Changed 13 years ago by saloynton

  • Description modified (diff)
  • Owner set to jburel

comment:11 Changed 13 years ago by jburel

  • Owner changed from jburel to saloynton

comment:12 Changed 13 years ago by jburel

  • Owner changed from saloynton to jburel

comment:13 Changed 13 years ago by jburel

  • Cc wmoore added
  • Description modified (diff)

comment:14 Changed 13 years ago by saloynton

  • Description modified (diff)
  • Resolution set to fixed
  • Status changed from new to closed

comment:15 Changed 12 years ago by jburel

Scott: did you put the conclusion in another document e.g. word/google? b/c this will be lost as soon as the ticket is closed.

Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.70167 sec.)

We're Hiring!