Yep, since ice_cube is made for occurrences and not durations - you'd
have to store these separately. I'm working with a branch now that
will support end_times for rules, so you could call occurring_at?
(Time.now) on a rule and see if it occurs anywhere in the duration.
I'll have this ready in the next few days
Thanks,
John C
On Jun 1, 3:02 pm, mikrogroove <o...@mikrogroove.com> wrote:
> Hi John,
>
> Many thanks for your quick reply! I knew about the .until() option,
> but it's not quite what I was after though. From the readme:
> "Individual rules may optionally specify an until date, which is a
> date that that individual rule is no longer effective". I need the
> rule to remain effective for the next occurrence of the event. Think
> of it this way: what if I have a weekly meeting every Monday between
> 9.30am and 10.30am and I do .occurs_at?(Time.now) on a Monday @ 10am?
> What I'm after is a way to specify the duration of each occurrence,
> but perhaps I'm better off storing this separately? But then how to
> deal with a schedule with multiple rules (where each rule might have a
> different duration)?
>
> Cheers,
>
> mikrogroove
>
> On 1 June, 15:14, John Crepezzi <john.crepe...@gmail.com> wrote:
>
>
>
> > Mikro,
>
> > Thanks, I'm glad you like it :)
>
> > Individual rules can take an end date as follows:
> > rule = IceCube::Rule.weekly.until(Time.local(2010, 10, 6))
>
> > Just a note: Until times are inclusive.
>
> > Hope this helps!
> > Thanks,
> > John Crepezzi <john.crepe...@gmail.com>
>
> > On Jun 1, 5:43 am, mikrogroove <o...@mikrogroove.com> wrote:
>
> > > This is a great gem, and probably the best starting point I could have
> > > hoped for in order to meet my project's requirements - thanks a
> > > million for putting it together!
>
> > > I'm dealing with recurring events which can be both stuff like normal
> > > business hours (mon-fri 10-18 & sat 12-18) or more obscure ones
> > > (second sunday of every month 12-19). I've set up a simple model and
> > > associated form which generates rules for the starting times, and it
> > > all works very nicely indeed (I render the schedule to YAML before
> > > storing in DB). But then *doh* it hits me: there is no way to specify
> > > an end time other than the time when the recurring series as a whole
> > > should end. How do I go about giving each recurring event a time
> > > span?
>
> > > Many thanks,
>
> > > mikrogroove
>
> > > On 26 Apr, 23:25, John Crepezzi <john.crepe...@gmail.com> wrote:
>
> > > > == Aboutice_cubeice_cubeis a time recurrence library for Ruby. The API is modeled
> > > > after iCalendar repeating events, making it very easy to describe
> > > > complex rules and conjunctions in pure Ruby. ice_cube'spower lies in
> > > > its ability to specify multiple rules - and easily query and expand
> > > > them. Most importantly,ice_cubeis fast, extremely expressive, and
> > > > removes ugly complex date logic from your application.
>
> > > > == Example
> > > > Rule.yearly.day(:friday).day_of_month(13).month_of_year(:october)
>
> > > > == Getice_cube
> > > > website:http://seejohnrun.github.com/ice_cube/
> > > > github: http://github.com/seejohnrun/ice_cube
>
> > > > gem installice_cube
>
> > > > Thanks,
> > > > John Crepezzi
> > > > <j...@crepezzi.com>
--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
No comments:
Post a Comment