• Status New
  • Percent Complete
  • Task Type Bug Report
  • Category Backend/Core
  • Assigned To No-one
  • Operating System All
  • Severity Low
  • Priority Medium
  • Reported Version
  • Due in Version Undecided
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: Flyspray
Opened by jahto - 23.08.2015

FS#2038 - Jscalendar must be replaced with something else

It's old. There has been a newer version 2.0. Even that one is not supported anymore, although some documents still remain available. The calendar component relies on its language translations files to be complete, or it breaks. Unfortunately, as I found out a few weeks ago, they are not, after switching the default language from english to my native one. Without having a good replacement for it, some of the translations for flyspray itself we've been getting lately are half-way unusable. Not for an ordinary user, but for anyone actually having to edit a task and its due date.

This task is a sub task of FS#1737 - Javascript Overhaul
Project Manager

Can we use HTML5 builtin date input tag? How do user agents support choosing dates (iPhone, Android, Desktop browsers, ..)
In future (FS1.1+) the database fields used for storing dates should be future proof datetime fields.
Timestamp ends 2037 if i remember. Always store as UTC 0.
calculations done with user timezone setting. (or project location setting).

The big solution would be:

- put everything Javascript into jsfile(s), no more inline javascript. Enables using Content Security Policies

- choose ONE jslibrary (jquery?), use a date chooser widget/plugin based on that.

jahto commented on 24.08.2015 19:00

I really wish that the new date input tag could be the right solution. So we could just drop one dependency. Have to test. If we still need to do it with javascript, I'm somewhat biased to using angularjs, but only because I'm working on a project that uses it and have to finally learn some javascript and one framework. I think I saw some date chooser during summer that was implemented using it.

Whatever the final solution, for me it's enough that it doesn't break if it hasn't some unmaintained translation file available or something there is missing.

For database, changing a few fields to biginteger should probably be enough. But I'm not yet very worried about that, there aren't many tasks where the due date would be over the actual overflow date (at 03:14:08 UTC on 19 January 2038).


Available keyboard shortcuts


Task Details

Task Editing