groupdate
turbo-rails
| groupdate | turbo-rails | |
|---|---|---|
| 2 | 48 | |
| 3,704 | 1,983 | |
| - | 1.4% | |
| 4.8 | 8.3 | |
| 24 days ago | 1 day ago | |
| Ruby | JavaScript | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
groupdate
-
railstart-niceadmin support more features
- [groupdate](https://github.com/ankane/groupdate)
-
railstart-niceadmin release now!Backend management system based on Bootstrap 5 and NiceAdmin and Rails 7
groupdate
turbo-rails
-
Can't get Rails 7 turbo_stream_from to update view from broadcast
The install notes here link to an issue specific to webpacker. Try that and see if it works?
-
Strong reasons to pick htmx, over hotwire?
True, in theory it is. A lot of it is coded in libraries like turbo-rails, though. And these are Rails-specific. But I've seen it being used in some Laravel projects, also I used it with Hanami.
-
Rails 7 - Turbo Frame and Turbo Stream
Check out https://github.com/hotwired/turbo-rails/blob/main/app/models/turbo/streams/tag_builder.rb
-
Use turbo_streams to update the client in real time from inside a loop?
So apart from the pretty obvious question of "why on earth would you want to do this?", I think there's a misunderstanding here of the intended use case of turbo streams. You have a page, and then some state changes on the server and you want to update the page to reflect that. Incrementing a variable doesn't really qualify as a state change, but perhaps a Product changing from "not good" to "good" would be an event worth broadcasting, which you could do using the Broadcastable concern in turbo-rails.
-
Where do I start for learning "HTML over the wire"
Use this too: https://github.com/hotwired/turbo-rails
-
Using ViewComponents with Turbo
Not mentioned in the article, but it's nice that turbo-rails recently gained the ability to pass ViewComponent objects directly to turbo stream helpers. https://github.com/hotwired/turbo-rails/pull/433
- is turbo and stimulus compatible with rails 4 ?
-
Turbo-Rails just got better
Release notes: https://github.com/hotwired/turbo-rails/releases/tag/v1.4.0
-
Live Visit Count for website or page. ActionCable, Turbo Broadcasts, Kredis
turbo/streams_channel.rb - a way to link a turbo stream with an ActionCable channel.
-
We're breaking up with JavaScript front ends
The readme seems to give a pretty good overview of turbo: https://github.com/hotwired/turbo-rails
What are some alternatives?
Chronic - Chronic is a pure Ruby natural language date parser.
Stimulus - A modest JavaScript framework for the HTML you already have
time_diff - Gem which calculates the difference between two times
hotwire-rails - Use Hotwire in your Ruby on Rails app
biz - Time calculations using business hours.
Turbolinks - Turbolinks makes navigating your web application faster
business_time - Support for doing time math in business hours and days
Webpacker - Use Webpack to manage app-like JavaScript modules in Rails
Recurrence - A simple library that handles recurring events.
hotwire-tabs
local_time - Rails engine for cache-friendly, client-side local time
webpack - A bundler for javascript and friends. Packs many modules into a few bundled assets. Code Splitting allows for loading parts of the application on demand. Through "loaders", modules can be CommonJs, AMD, ES6 modules, CSS, Images, JSON, Coffeescript, LESS, ... and your custom stuff.