Re: [elm-discuss] Support for binary data

2017-09-06 Thread Christophe de Vienne
gt; > > -- > Zach Kessin > Teaching Web Developers to test code to find more bugs in less time > Skype: zachkessin > +972 54 234 3956 / +44 203 734 9790 / +1 617 778 7213 > > -- > You received this message because you are subscribed to the Google

Re: [elm-discuss] Re: Can we get a patch release of elm-lang/core?

2017-07-31 Thread Christophe de Vienne
;> Is 6.0.0 very close to being released, or can I get a patch release >for >> this bug? :) >> > >-- >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 &g

Re: [elm-discuss] Systemic problem in Object Oriented languages

2017-07-20 Thread Christophe de Vienne
Le 20/07/2017 à 12:15, Peter Damoc a écrit : > > > On Thu, Jul 20, 2017 at 12:49 PM, Christophe de Vienne > mailto:christo...@cdevienne.info>> wrote: > > > Well, it is more an intuition after more than 20 years of coding that an > elaborated opinion. >

Re: [elm-discuss] Systemic problem in Object Oriented languages

2017-07-20 Thread Christophe de Vienne
tween data & logic makes things a lot cleaner, easier to understand and maintain. I do realize I would need to elaborate a little more to be convincing on this, but so far it is all I got :-) -- Christophe de Vienne -- You received this message because you are subscribed to the Google Gro

Re: [elm-discuss] Systemic problem in Object Oriented languages

2017-07-20 Thread Christophe de Vienne
se 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 > <mailto:elm-discuss+unsubscr...@googlegroups.com>. > For more option

Re: [elm-discuss] Re: Implementing websocket-based protocol - lessons learned

2017-05-24 Thread Christophe de Vienne
Le 23/05/2017 à 18:13, 'Rupert Smith' via Elm Discuss a écrit : > On Tuesday, May 23, 2017 at 3:30:44 PM UTC+1, Christophe de Vienne wrote: > > It is what I did at first, but it has serious drawbacks. The biggest > was > that a subscription implies an updat

Re: [elm-discuss] Re: Best practices to create examples for an elm package?

2017-05-23 Thread Christophe de Vienne
e.json' in the 'example' directory, and it has '../src', '.' as source-directory. About test, with elm-tests you also have a separate elm-package.json in tests/. -- Christophe de Vienne -- You received this message because you are subscribed to the Google Grou

Re: [elm-discuss] Re: Implementing websocket-based protocol - lessons learned

2017-05-23 Thread Christophe de Vienne
Le 23/05/2017 à 16:23, 'Rupert Smith' via Elm Discuss a écrit : > On Tuesday, May 23, 2017 at 3:04:01 PM UTC+1, Christophe de Vienne wrote: > > A discussion around a concept of "middleware", able to define its own > Cmd and Sub that it could rewrite a

Re: [elm-discuss] Re: Implementing websocket-based protocol - lessons learned

2017-05-23 Thread Christophe de Vienne
Hi Le 23/05/2017 à 15:50, 'Rupert Smith' via Elm Discuss a écrit : > On Monday, May 22, 2017 at 4:08:13 PM UTC+1, Christophe de Vienne wrote: > > I will make some tests with now that the plain version is working > properly. > > > Would be interesting to

Re: [elm-discuss] Re: Implementing websocket-based protocol - lessons learned

2017-05-22 Thread Christophe de Vienne
:59, 'Rupert Smith' via Elm Discuss a écrit : > On Monday, May 22, 2017 at 8:46:14 AM UTC+1, Christophe de Vienne wrote: > > * not being an effect module has clear pros : > - we can rely on other effect modules (in my case: WebSocket and > Random) > &g

[elm-discuss] Implementing websocket-based protocol - lessons learned

2017-05-22 Thread Christophe de Vienne
Hi everyone, Last week I coded a NATS [1] client, which is a PUB/SUB messaging system, in Elm [2]. It was very instructive and the result is pretty satisfying so far. Along the way I learned a few things that might be of use for others wanting to do this kind of client. * The WebSocket API is a

Re: [elm-discuss] Re: Implementing a protocol on top of WebSocket: should I build a effect module ?

2017-05-18 Thread Christophe de Vienne
2017 at 5:02:55 PM UTC+1, Christophe de Vienne wrote: > > The main thing that bothers me is that I will need to pass the > Nats.State to every update function because subscribing requires an > update of the state... And I see no way to avoid that except using an > e

Re: [elm-discuss] Re: Implementing a protocol on top of WebSocket: should I build a effect module ?

2017-05-17 Thread Christophe de Vienne
Le 17/05/2017 à 09:15, Christophe de Vienne a écrit : > > > Le 17/05/2017 à 08:24, Wojciech Piekutowski a écrit : >> There's also https://github.com/fbonetti/elm-phoenix-socket/. It doesn't >> use an effect manager, but apparently because of that doesn&

Re: [elm-discuss] Re: Implementing a protocol on top of WebSocket: should I build a effect module ?

2017-05-17 Thread Christophe de Vienne
bonus. Le 17/05/2017 à 01:38, Oliver Searle-Barnes a écrit : > You might find https://github.com/saschatimme/elm-phoenix useful to look > at, it's an effects manager phoenix channels built on top of the > websocket effects manager. > > On Tuesday, 16 May 2017 15:30:18 UTC+1,

Re: [elm-discuss] Re: Implementing a protocol on top of WebSocket: should I build a effect module ?

2017-05-17 Thread Christophe de Vienne
Le 17/05/2017 à 08:24, Wojciech Piekutowski a écrit : > There's also https://github.com/fbonetti/elm-phoenix-socket/. It doesn't > use an effect manager, but apparently because of that doesn't notify > about disconnection. > Very interesting. One limit I see is that only one type of Msg can be

Re: [elm-discuss] Implementing a protocol on top of WebSocket: should I build a effect module ?

2017-05-16 Thread Christophe de Vienne
it's any solace, that's what regular effects > managers do as well, so I wouldn't feel too bad about it. > > But maybe someone can render this whole message moot by saying "just write an > effects manager because there is no prohibition on one effects manager usin

Re: [elm-discuss] Implementing a protocol on top of WebSocket: should I build a effect module ?

2017-05-16 Thread Christophe de Vienne
Le 16/05/2017 à 17:17, Christophe de Vienne a écrit : > Thank you for the feedback. > > I am still trying to find a non-effect based API. Did not find anything > satisfying so far. > > The WebSocket.LowLevel module is interesting for send batches, but my > main issue

Re: [elm-discuss] Implementing a protocol on top of WebSocket: should I build a effect module ?

2017-05-16 Thread Christophe de Vienne
27;s not open-source, so can't share the code.) > > --Aaron V. > > On Tue, May 16, 2017 at 7:30 AM, Christophe de Vienne > mailto:christo...@cdevienne.info>> wrote: > > Hi everyone, > > I am attempting to implement the pub/sub NATS (https://nats

[elm-discuss] Implementing a protocol on top of WebSocket: should I build a effect module ?

2017-05-16 Thread Christophe de Vienne
ick such an API with a TEA approach ? If not is there any documentation I can read to get familiar with them ? Is there any existing module that does this kind of thing for another protocol ? Thanks! -- Christophe de Vienne -- You received this message because you are subscribed to the Google Group

Re: [elm-discuss] Poll for Intermediate to Advanced topics that people struggle with

2017-04-24 Thread Christophe de Vienne
you! > > -- > 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 > <mailto:elm-discuss+unsub