That's a great piece of article, you're awesome. A simple chat app tutorial with devise and broadcasting, with the ability to edit/delete will be a great help. Specially, what I'll be achieving from that tutorial is, a way to access `current_user` within back-end and pass the context/tubro_streams accordingly, [basically not with client-side JS but with backend]
Would really enjoy a slightly more comprehensive update. After using turbo frame with stimulus controllers we ran into several issues because the stimulus controllers aren't aware of the page changes. This means for example that stimulus controllers need to be nested within the frames to work properly
Yup! That's right. This has been true for as long as I can remember. Especially for new tech. It gets better with time, but in the meantime, you've gotta figure it out yourself. Or subscribe to my channel 😉 😉
A very good "wrap your brain around it" explanation. Thanks! PS. Can you use an external websocket and turbo-streams to get data into the application also ?
I think I am cheating. I just wrapped turbo stream tags into my turbo frame response. The turbo frame loads flawlessly, detects the the turbo stream tags which themselves update other pages of the page. Nesting is the way to go. No need to op-in into action-cable🙃 Or you can nest turbo frame tags which results in more requests but also updates in multiple sections.
I don't understand the point of turbo-frame & turbo-streams, it looks messy compared to how it was done even with jQuery alone. HTMX & Alpine.js look a lot cleaner to me than hotwire.
Well the point is you ca improve an existing (non-hotwire) site without doing much work. You don't need to change the old HTML to make the new one more reactive.
Cezar, Whenever I run 'Turbo::StreamsChannel.broadcast_update_to("teststr", target: "content", html: "foo") It gives me: [ActionCable] Broadcasting to tester: "foo" => nil
![[#2024MAMA] BIGBANG (빅뱅) - 뱅뱅뱅 (BANG BANG BANG) + FANTASTIC BABY | Mnet 241123 방송](http://i.ytimg.com/vi/EQsYfiPR9uM/mqdefault.jpg)
These tutorials are so great, thanks a lot!
You are welcome
Excellent, knowing this difference was muchly needed and you made it really accessible. Thanks!
Reading Ruby Weekly's and find this! Awesome.
Thanks Oscar
Thanks, concise and exactly what I needed as I was also a bit confused about which I should be using.
You're welcome Brad
Great explanation about turbo frames and turbo streams, one of the best explanations. Thanks to share this content.
Thank you
that is such a helpful video, i did have so clear with why frames or streams, but i have it clear right now thanks to you
I'm glad you like it ;)
That's a great piece of article, you're awesome. A simple chat app tutorial with devise and broadcasting, with the ability to edit/delete will be a great help. Specially, what I'll be achieving from that tutorial is, a way to access `current_user` within back-end and pass the context/tubro_streams accordingly, [basically not with client-side JS but with backend]
Thanks man. Not sure what you're after with the current user, but you might want to check the other videos on the Hotwire playlist.
This made a lot more sense, thank you very much!
Happy to hear that 👍
Would really enjoy a slightly more comprehensive update. After using turbo frame with stimulus controllers we ran into several issues because the stimulus controllers aren't aware of the page changes. This means for example that stimulus controllers need to be nested within the frames to work properly
Great video ... helped me a lot conceptually!
I'm happy to hear that
Amazing! So useful, keep up great content 😊
For some reason the Ruby on Rails official documentation is not as good as other web frameworks. Plus books for RoR's are not up to date.
Yup! That's right.
This has been true for as long as I can remember. Especially for new tech. It gets better with time, but in the meantime, you've gotta figure it out yourself. Or subscribe to my channel 😉 😉
Great as usual. Thank you!
Thank you Rafael.
A very good "wrap your brain around it" explanation. Thanks!
PS. Can you use an external websocket and turbo-streams to get data into the application also ?
Haven't tried that yet. So, I'm not sure.
謝謝你的影片幫助了我很多，thank you
Awesome video!
Glad you liked it
Thanks!
Great! Thanks
I think I am cheating. I just wrapped turbo stream tags into my turbo frame response. The turbo frame loads flawlessly, detects the the turbo stream tags which themselves update other pages of the page. Nesting is the way to go. No need to op-in into action-cable🙃 Or you can nest turbo frame tags which results in more requests but also updates in multiple sections.
That's cool, but you loose the caching benefit. And the lazy-loading one ;)
Can someone discover Reflexes ? One short video pls )))
Sure, who do I make the invoice to? :)
You look very familiar. Are you famous in some other channel? Maybe it was tiktok... ;)
Nope.
I don't understand the point of turbo-frame & turbo-streams, it looks messy compared to how it was done even with jQuery alone. HTMX & Alpine.js look a lot cleaner to me than hotwire.
Well the point is you ca improve an existing (non-hotwire) site without doing much work.
You don't need to change the old HTML to make the new one more reactive.
This did not clear up anything...
Cezar,
Whenever I run 'Turbo::StreamsChannel.broadcast_update_to("teststr", target: "content", html: "foo")
It gives me:
[ActionCable] Broadcasting to tester: "foo"
=> nil
That should be good. Are you not seeing the result?
@@mixandgo It should give the result as a 0, or 1.
Although I figured it out later. It was the redis configuration in the cable.yml
@@talhakhan4457 well, yes the method just enqueues the job. And the Redis server needs to be started.