Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Dioxus 0.3 – Templates, Hot Reloading, LiveView, and More

dioxuslabs.com

Post reply on HN
Print view View original

31–33 of 33 posts

Re: Dioxus 0.3 – Templates, Hot Reloading, LiveView, and More

#31

Post by quechimba »

jkelleyrtp wrote: post #15
floodfx wrote: post #7

Great to see another language adopting LiveView! (Author of LiveViewJS[1] here). Are you using Phoenix’s javascript client (and protocol) or rolling your own? [1] - http://LiveViewJS.com

We're using our own protocol right now - haven't really looked too deeply at the Phoenix protocol. We use templates (like Solid or Blockdom) to build and patch the page which is pretty specific to Dioxus.

Interesting! I implemented a virtual DOM in Ruby which streams patches to the browser.

I think this is is a really powerful way to make web apps and it's nice to see that others are doing it too.

Re: Dioxus 0.3 – Templates, Hot Reloading, LiveView, and More

#32

Post by quechimba »

toolz wrote: post #5
manmal wrote: post #4

Earlier quoted context omitted.

OTOH, LiveView sounds generic enough to become the name of the whole paradigm.

I would support liveview defining the entire process. I've written a lib myself to do liveview type things and coming up with a solid descriptor for things like conference talks was basically impossible. I write a lot of elixir and I would presume "phoenix liveview" is probably what people use to describe the elixir lib to people outside of the ecosystem anyways.

What about "live streaming server-side rendering", or Live SSR? That implies it's live and server side rendered...

I've been working with on like this for a while and I would also like to have a good name for it.

LiveView is a good name but not for generic use since there is a library with that name already.

Re: Dioxus 0.3 – Templates, Hot Reloading, LiveView, and More

#33

Post by POiNTx »

victorbjorklund wrote: post #30
POiNTx wrote: post #29

Earlier quoted context omitted.

That's something I need to look into. - Should be possible by saving the store in the localstorage and fetching it again on a different page. - Or saving the store to the window[1], as long as the page transitions happen through a live redirect[2] it should still be there. I'm building a collection of examples[3] and if I can get it working I'll add it. [1] https://wout.space/notes/how-to-share-store-between-multiple…

Yea, for sure it should be possible to do it with local storage but the real cool thing would be to be able to keep state in js between live redirects. Like you said it should be possible if using live redirect. Would love that. Good luck! Hope to be able to use your library in the future.

Hey, I got a simple example of using stores where you live redirect between 2 liveviews but the store information is kept. Was able to do it with saving the store to the window:

https://github.com/woutdp/live_svelte/tree/master/examples/s...

What could be cool if I can somehow map the reactive liveview state directly to a store... not sure how to do this yet but hope I can figure it out

Post reply on HN