-
Notifications
You must be signed in to change notification settings - Fork 358
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A javascript recurrence library #457
Comments
@thefliik rSchedule looks cool. Is there a demo site that shows off the UI? I'd love to look at other alternatives to |
@taylorbrooks rSchedule has no UI, it's purely a library for the logic. In this respect it is like ice_cube, except the processing happens on the client side. In my case, I use it with I haven't made a demo site for rSchedule, but it has a wiki site that explains how to use it and shows off the API. |
Btw, feel free to close this at any time |
Awesome - thanks for the heads up @thefliik this looks great! |
When I first started using ice_cube to handle recurring dates, maybe a year+ ago, I wasn't sure how I could also handle recurrence information on the client side. I use rails in api mode to power an Angular application, so the
recurring_select
gem mentioned in the readme wasn't a good choice.After some hunting, I found rrulejs, which was pretty nice but, at that time, poorly maintained and buggy. It also didn't support time zones and breaks the ical spec in a few places, and I had to patch ice_cube to work with it. Obviously not ideal (though in the past month one community member has stepped up and fixed most all of these problems).
So I ended up making my own javascript (typescript) recurrence library that supports the ICAL spec and can communicate to/from ice_cube via ICAL strings. You can check it out over at rSchedule. It works very well with ice_cube.
rSchedule has full timezone support (depending on what javascript date library you're using with it), so I've paired it with the ice_cube timezone branch in #455, though that isn't necessary if someone doesn't care about timezone support.
Anyway, thanks so much for building and maintaining ice_cube for all this time!!! Having build rSchedule, I know how incredibly time consuming that must have been...
For anyone interested in using ice_cube with a (javascript / typescript) client side app, I'd recommend checking out rSchedule, as just sending down a schedule's ICAL string and iterating the dates on the client side is much less data intensive then sending individual dates to the client from the server.
rSchedule supports RRULE, EXRULE, RDATE, and EXDATEs.
Example rSchedule usage with ice_cube
Server side
client side
Check out the rSchedule repo for more info
ps: I called out ice_cube as inspiration at the end of the project's README :)
The text was updated successfully, but these errors were encountered: