Skip to content

Major bugfix for calling timepicker on a jQuery collection, formatting, + misc #37

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
2 commits merged into from
Nov 18, 2010

Conversation

doublerebel
Copy link
Contributor

Hi Trent,

I see you've caught some of my typos, thanks. This code was rebased from your latest commits.

I fixed some formatting issues with long lines and mixed tabs and spaces. I also made some changes to simplify calling timepicker with different sets of arguments, based off the code that the Datepicker plugin uses. The major change is that a new Timepicker will be created for each input in a jQuery collection, previously I had not written this correctly. To do this a _newInst() fn was created.

I haven't had a chance yet to test the regional settings, do you have any regional-ized testcases I could use for example?

HTH,

Charles

Reuse jQuery obj for buttonPanel
var statement consolidation
Shortened default option code for $.fn.timepicker()
… jQuery collection

Fixed $buttonPanel typo
Consolidated .timepicker(), .datetimepicker() fns by using .apply()
Fixed == to === when comparing null and undefined in extendRemove fn (thanks JSLint!)
@trentrichardson
Copy link
Owner

I keep getting a this.each is not a function?

I think the regional stuff probably works. My only test was to pass in the translations as options and that worked fine.

@trentrichardson
Copy link
Owner

Fixed it and committed

This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants