theproductguy/cutetime

CuteTime is a customizable jQuery plugin that automatically converts timestamps to formats much cuter. Also has the ability to dynamically re-update and/or automatically update timestamps on a controlled interval.

cutetime's Issues

101 years per century?

Why every century has 101 years in CuteTime?

$.cuteTime('2011-06-28');
"just now"

$.cuteTime('1911-06-28');
"101 years ago"

$.cuteTime('1811-06-28');
"202 years ago"

$.cuteTime('1711-06-28');
"304 years ago"

$.cuteTime('1611-06-28');
"405 years ago"

$.cuteTime('1511-06-28');
"507 years ago"

$.cuteTime('1011-06-28');
"1014 years ago"

$.cuteTime('0001-06-28');
"2039 years ago"

cuteTime display on iPad/iPhone

On iPad, sometimes the function cuteTime display all the time as "just now" instead of the expected value.

PHP ISO8601 date format

Hi,

There's a small problem with dates with ISO8601 format from PHP. When date is formatted with DATE_ISO8601 format, CuteTime's regexp can't recognize it. That's because:

date(DATE_ISO8601) => "Y-m-d\TH:i:sO" => eg. "2004-02-12T15:19:21+0000" - notice lack of ":" in timezone.

source: http://php.net/manual/en/function.date.php

ps. date('u') is working fine, but it's PHP5+ only.

Trim the text before any computation

I like this plugin. We use this in my web application: http://o.pckg.in/deals-crawler. But the plugin just doesn't work if the text contains any extra whitespace. In HTML it is always possible to have some extra text between the elements. You should modify the plugin to execute $.trim() before doing any regex matching.

-Thanks
Sankar.

very localiced 1970-error

Hi

we are using cutetime in our webproduct and I have a quite strange error.
We are all mostly using Chromium on Ubuntu Machines for development and just on my computer there is a problem where the displayed time is always 1.Jan 1970 (so probably timestamp '0')

This happens with my local development server, our test server and even in production. But NOT when I use another browser.

So it's save to say that it's a local Chromium thing

I'm not using any proxies (anymore), I turned off all extensions, looked through all preferences (twice) and updated my system. 'date' in cl gives me a sensible output. I don't see a JavaScript error in Chromiums console

Short: I'm lost.

This is not a big issue (to me) since it doesn't happen to ANYBODY else and I don't expect you to take me by the hand. But have you ever experienced or heard about this? Any ideas?

Changeable TS_ATTR?

Could you please move TS_ATTR attribute to settings?

"data-" attributes are not xhtml friendly and I'd like to change "data-timestamp" to something else (title or property/content in xhtml+rdf) so it would validate.