Skip to content
This repository was archived by the owner on Sep 5, 2024. It is now read-only.
This repository was archived by the owner on Sep 5, 2024. It is now read-only.

mdDateTime - a date time picker #648

Closed

Description

@mlb6

Hi,

It would be very nice to have a date and a time picker.
This could be inspired by this project : http://amsul.ca/pickadate.js
Here are my suggestions (based on use case I already had in some e-commerce projects):

  • Ability to select 1 or multiple dates (To select a technical appointment with your cable company)
  • Ability to select a period (To select dates of departure and return in a travel website)
  • Ability to enable or disable dates based on a model of availability.
  • Ability to display 1 or multiple calendars.

Thanks

Activity

  1. sunny9240 commented on Nov 14, 2014

    @sunny9240

    +1

  2. jimmywarting commented on Nov 14, 2014

    @jimmywarting

    -1
    I hate everything that tries to be better then blinks native input date & time controller
    You are never really going to get the same functionality as the native. It will be bloated with more code dosen't work as good with validation/keyboard shortcuts/styling (overflow: hidden; inline position absolute/fixed) etc. mark my words: There will be bugs to fill. I could give you a hole page with flaws i have seen over the year with all of the picker i have came across. No one have ever been as good as the native.

    Have you looked at datetime-local in the newest Android or IOS? its amazing! Responsive & localized with both timezone and language.

    One thing you will never be able to fix is letting the picker (date, time, datalist & select) to flow outside of the document/iframe that is smaller then 100x30px

  3. kpgarrod commented on Nov 14, 2014

    @kpgarrod

    @jimmy that's an interesting perspective. Do you prefer IE's implementation
    of over pickadate?

    On 14 November 2014 11:24, Jimmy Karl Roland Wärting <
    notifications@github.com> wrote:

    -1
    I hate everything that tries to be better then blinks native input date &
    time controller
    You are never really going to get the same functionality as the native. It
    will be bloated with more code dosen't work as good with
    validation/keyboard shortcuts/styling overflow: hidden; inline position
    absolute/fixed etc. I could give you a hole page with flaws i have seen
    over the year with all of the picker i have came across. No one have ever
    been as good as the native.

    Have you looked at datetime-local in android or ios? its amazing!
    Responsive & localized with both timezone and language.

    One thing you will never be able to fix is letting the picker (date, time,
    datalist & select) to flow outside of the document/iframe that is smaller
    then 100x30px

    —
    Reply to this email directly or view it on GitHub
    #648 (comment).

    Keith Garrod

    Tel: +27-83-3000-988
    Fax: +27-86-5757781

  4. jimmywarting commented on Nov 14, 2014

    @jimmywarting

    no... yes... I'm not sure.

    They would eventually catch up and make crapy date picker eventually some day. And then my website would be ready to support it when it lands. It's all about progressive enhancement. Why should modern user suffer because of IE? It will still work but not as good. It's not like something will break. They will still be able to enter a date and time.

    I would perhaps want a fallback solution. Tell them how to enter a correct date with ngMessage. Perhaps use a mask:ed input with the support of parser/formaters

  5. jimmywarting commented on Nov 14, 2014

    @jimmywarting

    Btw, datalist and datetime-local makes a grate combo especially in android at least! demo
    That is one thing that no picker has... as far as i have seen

    blink is continues going to improve the picker even further then it is today and i get all the updates for free!

  6. ThomasBurleson commented on Nov 14, 2014

    @ThomasBurleson
    Contributor

    This component is planned for Q1, 2015 availability.

  7. added this to the milestone on Nov 14, 2014
  8. marcysutton commented on Nov 15, 2014

    @marcysutton
    Contributor

    The advantage of a Material date-picker versus native ones is a cohesive look & feel and interactive experience across all platforms. Every native date-picker looks different.

  9. kpgarrod commented on Nov 15, 2014

    @kpgarrod

    +1
    On 15 Nov 2014 02:54, "Marcy Sutton" notifications@github.com wrote:

    The advantage of a Material date-picker versus native ones is a cohesive
    look & feel and interactive experience across all platforms. Every native
    date-picker looks different.

    —
    Reply to this email directly or view it on GitHub
    #648 (comment).

  10. jimmywarting commented on Nov 15, 2014

    @jimmywarting

    Then i want it to be very accessibility. Everything you can do with the native should be possible with the material

  11. marcysutton commented on Nov 16, 2014

    @marcysutton
    Contributor

    Yes, all components must be accessible! The date picker will be a challenging one to get right, just as tabs were.

  12. jimmywarting commented on Nov 16, 2014

    @jimmywarting

    I want to have that tab-able functionality that change focus on yyyy-MM-dd --:--
    When I have focus on the month and enter number 2 on my keyboard it should choose 02 and go to next focusable part (dd) since there is no other month that begins with number 2. but if i enter 1 i should stay on the month until i go to the next one or with tab or my arrow key or enter 10, 11 or 12 then go to the next one.

    And on my android device i want something totally different? You are definitely up for a real challenging if you are going to win over the native input field. Even that <datalist> or something equal counts to convince me to use a custom picker instead

  13. mlb6 commented on Nov 16, 2014

    @mlb6
    Author

    @jimmywarting thanks for sharing with us your wishes regarding this functionality. Till now, the material design team did an amazing job. So, let them decide what should be the best user experience for this functionality. I'm pretty sure you won't be disappointed about the result.

  14. kpgarrod commented on Nov 17, 2014

    @kpgarrod

    @martin +1
    On 17 Nov 2014 00:03, "Martin Le Bas" notifications@github.com wrote:

    @jimmywarting https://github.com/jimmywarting thanks for sharing with
    us your wishes regarding this functionality. Till now, the material design
    team did an amazing job. So, let them decide what should be the best user
    experience for this functionality. I'm pretty sure you won't be
    disappointed about the result.

    —
    Reply to this email directly or view it on GitHub
    #648 (comment).

  15. 89 remaining items

  16. edinella commented on Jun 16, 2015

    @edinella

    +1

  17. jojoyuji commented on Jun 16, 2015

    @jojoyuji

    +1

  18. MacgyverMartins commented on Jun 16, 2015

    @MacgyverMartins

    +1

  19. modified the milestones: 0.11.0, on Jun 16, 2015
  20. ThomasBurleson commented on Jun 16, 2015

    @ThomasBurleson
    Contributor

    We are actively working on this component.
    Locking the conversation for now...

  21. locked and limited conversation to collaborators on Jun 16, 2015
  22. modified the milestones: , 0.11.0 on Aug 14, 2015
  23. jelbourn commented on Aug 18, 2015

    @jelbourn
    Contributor

    md-datepicker has landed in master. Please file specific bugs and features requests going forward.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions