This is not a question and I hope I this won't sound like spam. But I just
want to give some praise to the fantastic Eric Person (is that his name??)
and elm-seeds. https://elmseeds.thaterikperson.com/
44 episodes now posted at a regular interval - that's good stamina. Clear
and to the point
I'd back this too.
On Tuesday, January 24, 2017 at 11:21:31 PM UTC+1, Robert Lee wrote:
>
> Would anyone else find --Html.Attributes.none-- useful?
>
> none : Html.Attribute a
>
> Use cases look like the following.
>
>
>
> view: Model -> Html.Html Msg
> let
>
Yeah, the problem is that when we are talking about contentEditable divs and
spans there is no "defaultValue" attribute!
--
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
I've got a problem. We need to use contentEditable elements and while
editing them, the caret jumps to the beginning of the box everytime the
model updates. This derives from the fact that the browser holds some state
about the caret position outside the model (the horror), and we reset that
Yeah but that was kind of my point though. In an app where 'something' (using
your example) is the main piece of data, say a list of todos, then I wouldn't
want the whole slice thrown away on every update? Not too familiar with the Elm
core so I dont know where to look!
--
You received this
I'm sure many of you have sen Richard Feldmans amazing talk on impossible
states from Elm conf. In there he uses a Union Type for working with his
data
History =
History =
{ current: Question
, others: List Question }
This essentially means every time we want to update something in the
Ok Max, thanks I'll give it a go and see how it works out.
On Monday, October 24, 2016 at 4:13:33 PM UTC+2, Max Goldstein wrote:
>
> If you're going to refer to items by ID a lot, you should probably use a
> dictionary keyed on ID. Assuming items is a record with an id field:
>
> { model |
>
| The names were inspired by Dict.insert and Dict.update, which were the
closest to what I was looking for.
Yeah, I'm probably just too used to that dot notation.
I don't know why but
items.replaceItemById id item
looks better than
replaceItemById items id item
. Somehow it feels like a
Hey you guys! I've started to build out my first real Elm app and I'm
loving it. On my model there is a field called items
Model
...
items : List Item
...
which is a list of the type Item. Coming from a rails mindset I created an
"updateItemById" -function, which I use like this
>
>
>
>
>- What is the system supposed to do: RegisterWithCredentials String
>String
>- What happened in the system: ClickRegistrationSubmit String String /
>TapRegistrationSubmit String String
>
>
> Let's have an argumented discussion around this :}
>
I think one of the main
> If you implement the Router in Elm (the implementation starts with Elm), then
> Pages are a reasonable abstraction.
In this scenario - do you wire the state from each separate “page” up into the
top level app.elm (or wherever the routing lives), or do you let each page
manage it’s own
23 PM UTC+2, Peter Damoc wrote:
>
> On Tue, Sep 20, 2016 at 5:18 PM, Lars Jacobsson <lars.jac...@gmail.com
> > wrote:
>
>> Peter - just out of curiosity: How did you split those 8000 LOC up? Did
>> you go for a structured component/react type splitup, or did you s
Peter - just out of curiosity: How did you split those 8000 LOC up? Did you
go for a structured component/react type splitup, or did you split
"organically" when the need occurred?
>
>
> Another large amount of time was spent trying to integrate a carousel. I
> ended up reimplementing a bare
Peter - just out of curiosity: How did you split those 8000 LOC up? Did you
go for a structured component/react type splitup, or did you split
"organically" when the need occurred?
On Monday, September 19, 2016 at 3:08:43 PM UTC+2, Peter Damoc wrote:
>
> I keep postponing this for a few weeks
14 matches
Mail list logo
