Thanks. Needs a bit of assets size reduction though
Jason Rice
@ricejasonf
I'm just perusing through your stuff. It looks like you have a Beast based http server or client, but your websockets is wasm on the server side. Is that right?
err... websockets
Damien Buhl
@daminetreg
We have beast for non wasm platforms in nxxm/xxhr
Which is an high level http client
And for the backend it’s for the moment node based
I use the node runtime to forward http request to c++ route handler
The stuff that is perhaps nearest to nbdl is wasmabi
That in the demo runs on websocket but also can on html serversent events
Jason Rice
@ricejasonf
wasmabi? I don't see that. a repo?
nbdl is a generic state manager
It has integrations for rendering state as dom and stuff though
Damien Buhl
@daminetreg
Wow that’s cool
Jason Rice
@ricejasonf
Some of the stuff in it can be used stand-alone, but for the most part, it is like a framework similar to angular
very much a wip though
Damien Buhl
@daminetreg
So wasmabi isn’t the same thing but the state management that I implemented in bellevue is similar then: https://github.com/nxxm/bellevue
So we are building the same thing, you are more advanced though. I didn’t understand nbdl could be used for dom rendering
Have you seen asm-dom of mbasso ?
Jason Rice
@ricejasonf
yes
my dom manipulation implementation is naive atm
but it only updates the nodes that are mutable
_
Damien Buhl
@daminetreg
I have a closed source implementation of bellevue which is more advanced but it’s under nda and so on. So now I’m rebuilding opensource
Mutable dom nodes ?
Jason Rice
@ricejasonf
nda with a client?
Damien Buhl
@daminetreg
Yes it is a project for the pharmaceutical industry and geared towards graph
datapoint graphics representations for researchers