:)
Just wondering :)
(There's an echo)
I missed it
Anyone know how I can render a VTree to a string?
And perhaps to avoid the XY problem just mentioned in the presentation: I want to test the view without needing to know the exact structure. Thus, my thinking was that if I could render it to an HTML string, I could use Cheerio (JQuery-like) to find an element in the rendered view.
damn that's when I wish I was there in person so I could ask multiple things haha
totally forgot to mention I updated the socket.io driver!! need to get it out to npm unless you want it as part of Cycle @staltz ? https://github.com/Cmdv/cycle-socket.io
my slides from cycleconf Lightning talks - "Cycling for noobs" http://www.slideshare.net/SteveLee/cycling-for-noobs
A persistent, shared todo list; a websockets game; chat rooms and more running flawlessly (as far as I can tell ) in a Motorcycle.js application. The repo is at JS-monads-part6 and the online demonstration is at http://schalk.net:3055. There are two major cycles involved in the application. Motorcycle.js is one. The other is processed user input going to the modified Haskell Wai Websockets server and then being received (sometimes after server processing) by group members for parsing and updating the virtual DOM . My JS-monads are in a mature state now, and are very helpful in running the application in an understandable, easily maintainable, reactive manner. I feel so relaxed and and unburdened now that React.js and Node.js are becoming distant memories.
byt the way another big win of XStream is .do(x=>console.log(x)) -> .debug(x) ftw
@marcusnielsen I have a work-in-progress req/res driver https://github.com/mariuslundgard/cycle-http-context-driver/blob/develop/src/http-context-driver.ts. It's similar to how RPC works using a message queue (in that it passes the response around for correlation).
And used like this in a component:
import {HTTPContext} from '../../http-context-driver'
function FrontPage ({HTTP}) {
return {
HTTP: HTTP.map((ctx: HTTPContext) => {
const outgoing: HTTPContext = {
request: ctx.request,
response: ctx.response,
body: 'FrontPage'
}
return outgoing
})
}
}
export default FrontPage
I'm not sure it's a perfect fit for req/res, however I find it nice to be able to deal with req/res in a similar manner as the rest of the app.