Break up timepicker's model into separate values

[wesleycho]

This change is to break up the model into separate values, i.e. hours, minutes, and seconds. This is to fix date related issues for a component that shouldn't rely on date objects at all.

[pkozlowski-opensource]

@wesleycho since I'm looking into timepicker in the context of https://github.com/ng-bootstrap/ng-bootstrap I would like to brainstorm here.

I totally agree that using Date object is sub-optimal and we should use another data structure instead. What is your current thinking regarding the exact data structure? For me it could one of:

• string (possibly with a configurable parsing / formatting strategy)
• A predefined data structure (ex. {hour: 12, minute: 15: second: 00})
• any arbitrary data structure where a user is obliged to provide parsing / formatting utility

At the end of the day we want sth like: <input ng-model="timeExp" bs-timepicker> and we need to define:

• allowed values for timeExp
• how to turn value of timeExp to a string (we need it so we can display a selected time in the input field)

Thought?

[wesleycho]

I'm a fan of using an object (second option), that way it is a nice & expected structure, and simple enough for a user to work with (i.e. modifying a date object with the time values to submit to a server).

Allowed values - we should validate that the object is explicitly as we expect (predefined data structure).
Converting to string - given predefined structure, would be very easy to convert to string for each input using a leftPad function.

[pkozlowski-opensource]

I'm a fan of using an object (second option), that way it is a nice & expected structure, and simple enough for a user to work with

I agree. Let's start with this. We could always add more formats as we go.

[sendilkumarn]

I too agree we could use the object. I think it is more flexible.