Thought I would jump in here and respond to a few of your comments/
suggestions...
First off, the Datejs library is actually built from 4 separate
modules (CultureInfo, core, parser, sugarpak). We compile all of them
together creating one date.js for each language/culture/country during
our final
Nicolas Hoizey schrieb:
This came through my feed reader this morning, and I thought it looked
like the kind of thing jQuerians might enjoy:
http://www.datejs.com/
I really don't like the weird syntax they use.
This Date.today().next().thursday(); is not real chaining IMHO. Even
more (
> > This came through my feed reader this morning, and I thought it looked
> > like the kind of thing jQuerians might enjoy:
> > http://www.datejs.com/
I really don't like the weird syntax they use.
This Date.today().next().thursday(); is not real chaining IMHO. Even
more (3).days().ago();
Chai
that's pretty dang cool. I like the syntactic sugar. I was amazed that for
all it's coolness when I entered "tomorrow at 8:15PM" that it understood
that as tomorrow at 8:15AM... it ignored my AM/PM designation! It only works
off of a 24 hour clock. That's a little disappointing, but not so much as
Erik Beeson schrieb:
Hello all,
This came through my feed reader this morning, and I thought it looked
like the kind of thing jQuerians might enjoy:
http://www.datejs.com/
It's a Date library with lots of parsing capabilities and jQuery style
chainable syntactic sugar. It's ~25k minified (
25k is a lot for Javascript, yes but include it in the bottom of your
page and the 25k will be the last to process while not holding your
page captive. This works great for anything form related because date
entry is usually lower in the page/form. For dates, functionality
matters over size.
Ma
6 matches
Mail list logo
