Thanks Fred! I've tried your solution and at least I got to confirm a personal fear: it's scary big. 1.7MB might not seam much but... I'll be honest, I don't like artifacts this big . The inspector says that it will take 17 seconds over a regular 3G connection to load this.
This also feels like a glorious opportunity. On Wed, Sep 28, 2016 at 1:41 AM, Frederick Yankowski <[email protected]> wrote: > I took Peter’s gist as a basis and made a repo out of it: > https://github.com/fredcy/elm-polymer-calendar > > My version uses a small bit of native code to convert the JS Date value > from the calendar component (sent as a JS event) into an Elm Date value. > That avoids the kluge I had before using toString and Date.fromString to > do the conversion (with manual munging of the string necessary in between). > > I spent a little time getting it to work in the latest Chrome, Firefox, > and IE. I also packaged it up into a near-minimal distribution which can be > seen at https://fredcy.github.io/elm-polymer-calendar/ > > > -- > You received this message because you are subscribed to the Google Groups > "Elm Discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- There is NO FATE, we are the creators. blog: http://damoc.ro/ -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
