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.
@mariuslundgard awesome! You got a github star :-)
I hope I can start wrapping https://github.com/marcusnielsen/rxjs-server as a cycle.js driver in the future. And I would love to have the req/res-part available as well.
I just don’t have the time to figure out if I need cycle.js or not in my projects. But I do use most of the thoughts I’ve heard about MVI, but as model, view, interactions, and state.
where interactions are actions (input functions), events (output event streams), and reactions (chaining composed events).
i mean try,
input$ = DOM.select(document).events('keypress')
Which makes sense to me...selecting document feels a bit weird.
sorry for confusion ;) my fault, i used https://github.com/TylorS/cycle-snabbdom/blob/master/src/fromEvent.js#L37 and it worked for me ;(
The reason
DOM.select() doesn't select from document, is because it's external to your main(). Drivers are the place where you listen to what is external to your main().
The #cycleconf live stream https://youtu.be/B2BFwIshais
Other attempts were intermittently successful, presumably dependent on where focus was
I will write a blog post or two about my experiences with cycle.js as a n00b :)
Also, finally starting a proper project in cycle today
w00t
