Persistence as a View

[luigy]

I've started playing in a branch in adding functionality and following the TodoMVC spec

I'm curious how would you approach implementing persistence?
My first thought was just make a View and combine it, but Ohm restricts me from doing that or does it provide another way to hook up?

Also, @Boothead would you be interested in dropping virtual-dom in favor of React?
I like what Joel is doing with react-haskell

[commandodev]

Hi Luigi,

The function that runComponent is built from has a base version here: https://github.com/boothead/oHm/blob/master/src/Ohm/Component.hs#L87 that takes a (model -> IO ()) which would be a good fit for your putLocalStorage function.

I would be interested in using react, especially given the recent announcement about react native! The only couple of times I've looked at it the OO feel of the components didn't sit that well. Having said that, @joelburget's library looks pretty cool so I could certainly imagine a react derived view for oHm. Do you want to have a try with it?

[commandodev]

One comment on your branch:

I find architectures like this easier to reason about if I think about the ModelEvents (the ones that are passed as the first argument to the model) as "something that has happened". So ItemDeleted EditTextChanged etc. UI Events (the ones emitted from the UI) I usually like to think of as commands. For example DeleteItem EnterEditText.

In my todo mvc example because I'm only using one type for both concepts, I'm treating it as commands from the UI being passed directly to the model. So if you're wondering which parts should be split up, it's not only when you split components to consider, but also when you move from one event type for a component, to one type for the commands from the UI and one for the input to the model.

Hope that helps :-)

[joelburget]

Happy to help where I can with react-haskell! I think the structure I've been advocating with react-haskell is more or less the same as you use in oHm. We should chat using something higher bandwidth than this issue.

[commandodev]

Hey Joel,

Yes it would be good to have a chat. I seems at first glance that ohm and react-haskell are fairly complementary. I've gone at it from the point of view of the flow of data, with the rendering being handled fairly trivially. On the other hand I love what you've done with the animations in react-haskell - I was planning to shamelessly steal it actually :-).

What would be a good way to chat? Skype/email? Are you in NYC?

Cheers,
Ben

[joelburget]

Hey Ben, I'm road tripping at the moment. Hello from Nashville! I will be in NYC next Saturday (the 14th) so we could chat in person then! However, tomorrow's my last travel and I'm eager to work on this stuff next week, so a chat sometime this weekend would be ideal for me.

Skype works. I'm joel.burget.

[commandodev]

Let's try for Saturday evening my time? I'm ben017f

[luigy]

Nice! I didn't expect this to happen and would like to join as well. My skype is itzluigy

@Boothead thanks, I'll give it a try. This chat should totally happen to expand more on it :)
@joelburget I see you've started your journey before even leaving the states ha!
Drinks on me when you get here!

[commandodev]

Hi Guys, Going to have to give it a miss this evening. How about tomorrow around this time (2000 UTC)?

Cheers,
Ben

[joelburget]

@luigy For sure, let's meet up! I'll be there in about a week.
@Boothead Works for me. See you then!