Thread: [Fremantle Maemo5] [Announce] Qalendar -- a replacement for the default calendar
View Single Post
jackburton is offline jackburton
2013-09-16 , 14:51
Posts: 466 | Thanked: 661 times | Joined on Jan 2009
#71
Originally Posted by gidzzz View Post

2a) A special distant date

But I'd rather go for 2038, most likely 2^31-1 seconds since 1970 UTC, because the whole 2037 is still completely valid. I think this would be as close to due-less as calendar-backend permits. Such tasks would not have their date displayed in Qalendar.

@jackburton: I installed MaeCalTasks to see exactly how it works, but If the screenshot is from 1.0.0-5, then I am doing something wrong or there's a bug, because I don't see the buttons with "X", "Today" and "Tomorrow".
The latest versions were built during the Nokia to community transition while the autobuilder was down. You can get the latest from here:
http://talk.maemo.org/showpost.php?p...2&postcount=73

I also have a question: was 2037 just simpler to use? Or is it to allow also the stock calendar to set such date? I guess It would be nice if Qalendar was compatible with MaeCalTasks in this matter, but I see no definitive reason to choose 2037 over 2038.
It was just simple. Also, the The furthest time that can be represented this way is 03:14:07 UTC on Tuesday, 19 January 2038 according to Wikipedia. So setting any date to 2038 could cause overflow when stored back to the DB. Also, I wanted a way to maintain the original due day and month in case one wants to revert. You could use the last real int for the time structure as a sentinel value, but I'm just using the year portion. Also, I have a filtering mechanism to create custom views for tasks. Since due-less tasks are so far out in the future, these will not be shown.

Or is that X button just a shortcut to toggle the year and 2037 tasks do not get any kind of special treating (2b)?


2b) Just a distant date

There would be a shortcut to set the date to 2037 and that's it. I think it would feel like a quick hack, so I do not really like it.
Sometimes quick hacks "just work". I focused on other more "value-add" items that I wanted first such as my filtering system.

I also created a dynamic way to create system configuration options in the DB. This allows for adding new configs to new versions without huge data structure changes. Poke around there, too.
 

The Following 6 Users Say Thank You to jackburton For This Useful Post: