Not sure what you mean by that.
When creating or modifying a tiddler, TiddlyWiki simply uses the system
time for the tiddler's created/modified timestamp.
-- F.
Not sure what the underlying purpose here is, but I would guess that
server-side adaptations (like ccTiddly) use the respective hosting
server's time rather than the user's local system time:
http://www.tiddlywiki.org/wiki/Server-Side_Solutions
-- F.
Good point - there should be an option to use UTC for timestamps.
Will bring this up with the dev team, and maybe I can whip up a plugin
for it as well.
-- F.
Try adding the following code to a tiddler tagged with "systemConfig":
http://tiddlywiki.pastebin.com/f7f590131
Note that this automatically sets the "use UTC" option to "true" on each
startup.
This change is being considered for inclusion in the core:
http://trac.tiddlywiki.org/ticket/651
-- F.
If the operating system is configured correctly, that offset should be
calculated automatically!?
> P.s.: Million thanks to FND for all his help till now. Lets hope that
> the time synchronization gets successfully integrated into TiddlyWiki
> adding to its feature list.
UTC is a tricky issue, because it's easily misunderstood by users.
That's why we're still unsure whether to include this patch in the core.
Does the plugin code I'd posted not work for you?
-- F.
Sounds about right.
> I think this could be because all the system in my company sync their
> clock from a unique server dedicated for a particular country (maybe).
> If that is the case then the system does not have any ways of finding
> what the UTC time is.
I doubt that server returns the local time as UTC - that'd be really
weird...
Try creating a "systemConfig"-tagged tiddler with the following code:
var offset = (new Date()).getTimezoneOffset();
alert(offset);
That should display the respective timezone offset on startup (in minutes).
> So if the team member know that he is woking in a timezone which is
> 5hrs behinde UTC (or any timezone which can be taken as a standard)
> and enter it in the box.
I guess the Date.prototype.toUTC() function could be adapted to prompt
for offset input - but that wouldn't be a clean/reliable solution...
-- F.
Glad to hear that - I was really puzzled for a while...
> I was checking it using the TaskTimerPlugin [...]
> The plugin seems to be taking the system time directly and does not
> consider this offset time. Any suggestions will be of great help.
Well, Eric could update the date initializations in his plugin to
support the chkUseUTC option suggested in the core ticket*.
However, I'm not sure whether this makes sense until UTC support
actually makes it into the core. Let's wait for his response (you might
need to start a dedicated thread to capture his attention - but wait a
few days first).
(Dev note: Maybe it would make sense to introduce a getCurrentDateTime()
function for future-proof encapsulation of date initializations.)
-- F.