On Tue, August 15, 2006 11:49 am, bbuchs said:
>
> I would argue that "less is more". One of the most fantastic things about
> jQuery and the syntax is that it's so damn light. What's the most common
> scenario for a date picker in a web app? Is it really neccessary to pick a
> date 2, 3 years in the future?
>
> Othewise, great plugin Kelvin. My only suggestions would be (1) to remove
> the extra markup and use a DOM creation method or a wrap() to add the
> container DIV, and (2) instead of doing INIT calls to use something more
> "jquery-esque":
>
> $("input.mydate").datePicker({format:'mm/dd/yyyy', startdate:'08/15/2006',
> enddate:'08/31/2006'});
>
> But that's just me... Great work!I would second this. The init method in use currently, if I understand it correctly, means that multiple date pickers on the same page must have the same settings. That is not always desirable. Passing a config object as in bbuchs's example above would not only look cleaner, it would make each picker independently configurable. Spiffy! Now, if there were a way to make the start and end dates dependent on another date picker field, then you'd have support for "from" and "to" date fields, automatically enforcing the the to can't be after the from. That would be highly cool. :-) That said, this is still a most excellent plugin! --Larry Garfield _______________________________________________ jQuery mailing list [email protected] http://jquery.com/discuss/
