These are chat archives for indrimuska/angular-moment-picker

16th
May 2017
Tomas Laskauskas
@thfrlw
May 16 2017 06:47
hi there @indrimuska, pickers performance aint that great when I have 10+ fields using picker, is there any way to use one picker for all those fields instead of generating/wrapping html around each one ?
Indri Muska
@indrimuska
May 16 2017 07:00
Hi @thfrlw, I've pushed a new v0.10 release few days ago that appends and shows one picker at the time to the document.body without using Angular. With this in place we should have gain a little more performances, so I'd suggest you to try this version and see if it works better than the previous one (0.9)
Tomas Laskauskas
@thfrlw
May 16 2017 08:04
wow, it does perform much better, lets say 1.5s vs 0.2s with 18 picker fields. Thanks.
Indri Muska
@indrimuska
May 16 2017 08:05
Good! Happy to hear that! :smile:
Tomas Laskauskas
@thfrlw
May 16 2017 08:30
is there a way to pass all(combined) settings (as object ?) to input using single attribute? I mean those max-date, min-date, etc.. I know about Provider, but I have more than one type of picker i need.
Tomas Laskauskas
@thfrlw
May 16 2017 13:00
and picker will go out of screen if field is near right edge.
Indri Muska
@indrimuska
May 16 2017 16:53
Hi @thfrlw, Moment Picker Provider is useful to have common settings for all the pickers in your application, but some properties are related to the single instance and are not available in the Provider (e.g. maxDate). Depending on your requirements, you can create a component to wrap all properties into a single object. On the other side, I don’t think I’ve understood your issue about the picker that goes out of screen, could you please further argue?