Wouter, looks good. Yeah, it's not a big deal if the counter is nested or
not in this case. Just one thought - I'm not sure that the generic
signature of the CounterView.view is useful here:
view : msg -> msg -> Int -> Html msg
Yes, keeping the signature generic allows you to avoid importing
Hi am trying to get my drag and drop user interface to work with touch
events. I have it working fine by subscribing to the mouse events
from https://github.com/elm-lang/mouse
I would like to do something similar with touch. I
tried knledg/touch-events but it works with attributes not with
>
> Here's what I've been working on. The recent git history is all about
> refactoring. Haven't introduced 'sub-components with state' or w/e and
> don't see it coming soon. It's an Elm-SPA with a Phoenix backend:
> https://github.com/knewter/time-tracker
Josh, make sure to share this
>
> Here's what I've been working on. The recent git history is all about
> refactoring. Haven't introduced 'sub-components with state' or w/e and
> don't see it coming soon. It's an Elm-SPA with a Phoenix backend:
> https://github.com/knewter/time-tracker
>
Looks interesting. Thanks for
>
> I would love to know how to do this!
> Can anyone point me to a brain-dead-simple practical and working example
> for a non-expert Elm user like myself?
OK, so here is my take at an alternative multiple counters approach.
{- Model needs to hold a list of counter values
Any counter in the
>
> I would love to know how to do this!
> Can anyone point me to a brain-dead-simple practical and working example
> for a non-expert Elm user like myself?
OK, so here is my take at an alternative multiple counters approach.
import Html exposing (Html, div, button, text)
import Html.App
>
> I would love to know how to do this!
> Can anyone point me to a brain-dead-simple practical and working example
> for a non-expert Elm user like myself?
OK, so here is my take at an alternative multiple counters approach.
First, putting everything in one (monolithic) module:
import Html
>
> I would love to know how to do this!
> Can anyone point me to a brain-dead-simple practical and working example
> for a non-expert Elm user like myself?
OK, so here is my take at an alternative multiple counters approach.
First, putting everything in one (monolithic) module:
import Html
Wow, that's beautiful, thanks so much!!
--
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 elm-discuss+unsubscr...@googlegroups.com.
For more options, visit
>
>
> For newcomers to Elm, *wouldn't it be better to change the scaling from 1
> to multiple counters in the guide in a different way? *
> E.g.
>
>1. Build everything in 1 module, e.g. save a copy of counter.elm as
>counter-list.elm
>2. Change every building block (Model, Msg,
I'm also interested in best practices (performance wise) for using
frameworks. Should I import external libraries in my index.html file or
should I use elm packages. What's the better approach?
For example:
Should I import PureCSS im my index.html using
On Sunday, August 28, 2016 at 10:14:43 AM UTC+2, Richard Feldman wrote:
>
> Components should only update their own private non-shared state that
>> other components don't need. Shared states such as your server queue are
>> updated at the highest level and each sub component merely receives a
12 matches
Mail list logo
