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 build process out of convenience for the end user developer. You are more than welcome to piece together the modules as required. Basically only the CultureInfo and core.js files are required. The Parser and SugarPak are optional. The complete library is 25k because theirs a lot going on. If you have recommendations for optimizations, please let us know. There's more information regarding the modules on the projects GoogleCode home page. See http://www.datejs.com/googlecode/. I guess it all comes down to how much Date processing power you require. I imagine if you're building a scheduling app, the Datejs library is going to come in real handy. We compress with JSMin. Why? Because we like JSMin. There's something very reassuring about Crockford's work and once gzipped, there's very little difference between the various compression options/ combinations. Obviously if you pass the bits through Packer there's some up front savings. The choice is yours. @Nicolas Hoizey - I find your syntax suggestion of Date.today().next('thursday') to be rather goofy. We have something much cleaner, faster and explicit, Date.parse('next thursday'). What happens if you don't pass the string parameter (eg Date.today().next()) into .next(), what does that return? How is that any different than leaving off the final function call on (3).days()? which would return '3' by the way. @Chris Jordan - Your sample "tomorrow at 8:15PM" is working now. You caught a small bug that we weren't testing for. Hope this helps answer some of your questions. On Nov 29, 1:28 pm, Jörn Zaefferer <[EMAIL PROTECTED]> wrote: > 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 (3).days().ago(); > > > Chaining suppose you can remove last call and still get something. > > > What would (3).days(); mean? > > > jQuery like syntax would probably be more Date.today().next('thursday'); > > Good point. You should post that to their mailing list. > > Jörn
