On Tue, Mar 26, 2013 at 9:25 PM, Irina Arkhipets <[email protected]>wrote:
> Hi Dishara, > > I don't think you can use RDATE for the implementing recurrences. > For example, it would be impossible to describe an endless recurrence > without untill date at all. > > As Maxim already wrote, the main problem is database. > > Its structure should allow: > > - Create/update/delete recurrence events > - Detect which recurrence instances appears in the given period of time > - Allow to modify all the instances, one instance or a tail of the > instances (the third case is actually optional - AFAIK not all the calendar > applications support this-and-after recurrences, and this case is not > strongly specified in RFC 2445). > - Allow to have recurrence exceptions, i.e. to remove single instance in > the recurrence chain > Ok. Got the point. So basically we need a CRUD API for recurrence events where it will perform the CRUD operations against the DB. And that interface will be called from the iCal4j wrapper layer. Can you please name the table which stores the events currently. I searched in org.apache.openmeetings.persistence.. packages, but could not find such table. > > Additionally, you would need to take into account time zone differences > problems from the very beginning. Say, if user with time zone A invited > user with time zone B to the daily meeting, and DST periods are different > for A and B, it's not trivial how to calculate start time of the events on > each day. > > Anyway, I would suggest to start from thinking about the database structure > - how recurrence rules would be stored in the OpenMeetings database and how > they can be queried from there. > It seems like if the event is recurrent, recurrence rules should be stored > in some separate table which does not present currently in OpenMeetings > database. > Since the normal events and recurrence events are independent, and has nothing to do with each other(correct me if I am wrong), shall we store recurrent events on a separate table. And also from APi level a rule can be added to a event. So rule is a part of an event. Hence ideally what should happen is we serialize the Event Bean where it should store with the rules and etc. Are we already storing events as beans ? Or we just store what is only necessary like event Id/type and etc. > > Best regards, > Irina. > > On Tue, Mar 26, 2013 at 6:14 PM, Dishara Wijewardana < > [email protected]> wrote: > > > Hi Irina, > > Sorry for the late reply since I was not well in last couple of day. I > was > > able to set up ical4j and tested locally with all following mentioned > > aspects with the API, relating to recurrence events. > > > > i.e > > - Created an event (VEvent) for a given day/for a given period of > > time (Monday 1PM - 4PM) > > - Added attendees to the event > > - Added Recurrence Rule for the event in different combinations > > (WEEKLY(specified days only with a starting day for the week), > DAILY,HOURLY > > along with a given interval/setUntil and etc) > > - Created a ical4j Calendar and added the previously created > VEvent. > > - And tried calculating the recurrence set with a given period of > > time with different combinations. > > > > And those helped me to get familiar a bit with the ical4j API. > > > > So in terms of this project, I am +1 for using RRule for implementing > > recurrence events using ical4j. We can also use sequence of dates (RDATE) > > for the same purpose. But I have not tried that yet. Please let me know > if > > there is any advantage you already know using RDATE over RRule for this > > particular purpose. Seems RRule is much cleaner and made for this > purpose. > > > > On Fri, Mar 22, 2013 at 7:22 AM, Dishara Wijewardana < > > [email protected]> wrote: > > > > > > > > > > > On Thu, Mar 21, 2013 at 10:44 PM, Irina Arkhipets < > > > [email protected]> wrote: > > > > > >> Dishara, > > >> > > >> Yes, moreover - this library is already used in OpenMeetings. > > >> > > >> Wonderful.. In fact I have created an eclipse project and was able to > > > build the trunk.I will look in to this ical4j API and get an > > understanding > > > of how this can be incorporated to this project implementation. And > thank > > > you for pointing out the ical4j. > > > > > > > > >> Regards, > > >> Irina. > > >> > > >> On Thu, Mar 21, 2013 at 10:49 PM, Dishara Wijewardana < > > >> [email protected]> wrote: > > >> > > >> > On Thu, Mar 21, 2013 at 11:23 AM, Irina Arkhipets < > > >> > [email protected] > > >> > > wrote: > > >> > > > >> > > Hi Dishara, > > >> > > > > >> > > FYI: you can try ical4j library for your project as it already > > >> implements > > >> > > required recurrence models for java. > > >> > > > > >> > > > >> > Hi Irina, > > >> > This seems pretty good indeed. I also saw quite a few positive > > feedbacks > > >> > for them. Before digging in to this, can we ship this as a > dependency > > >> under > > >> > Apache License 2 ? > > >> > Please refer [1]. > > >> > > > >> > [1] - http://build.mnode.org/projects/ical4j/license.html > > >> > > > >> > > > > >> > > https://sourceforge.net/projects/ical4j/ > > >> > > > > >> > > Best regards, > > >> > > Irina. > > >> > > > > >> > > On Wed, Mar 20, 2013 at 12:41 AM, Dishara Wijewardana < > > >> > > [email protected]> wrote: > > >> > > > > >> > > > Hi all, > > >> > > > This is regarding the JIRA [1] created for one of the GSoC 2013 > > >> project > > >> > > > ideas. And I am moving the discussion regarding $subject at [1] > to > > >> open > > >> > > > meeting dev list. > > >> > > > > > >> > > > Just a small brief of my self to the mailing list: I am Dishara > > >> > > Wijewardana > > >> > > > who is interested in contributing to Apache projects and I have > > >> > > > successfully completed my last year GSoC (2012) in Apache > Velocity > > >> > > project > > >> > > > and there I implemented a complete JSR 223 API support for > > velocity. > > >> > And > > >> > > > willing to take part in GSoC this year with Apache OpenMeetings. > > >> > > > > > >> > > > Hi Irina, > > >> > > > It seems that what you basically mentioned on [1] are the > > >> fundamental > > >> > > facts > > >> > > > from iCalendar Specification which is related to recurrence > events > > >> > > > implementation. But I will start looking in to the spec [2] to > > get a > > >> > > better > > >> > > > understanding and meanwhile will checkout the code and build it > > >> first > > >> > of > > >> > > > all, and hopefully find a way in to the Open Meetings code base > > ;-). > > >> > Will > > >> > > > post If I encounter any issues. > > >> > > > > > >> > > > [1] - https://issues.apache.org/jira/browse/OPENMEETINGS-549 > > >> > > > [2] - http://www.ietf.org/rfc/rfc2445.txt > > >> > > > > > >> > > > -- > > >> > > > Thanks > > >> > > > /Dishara > > >> > > > > > >> > > > > >> > > > >> > > > >> > > > >> > -- > > >> > Thanks > > >> > /Dishara > > >> > > > >> > > > > > > > > > > > > -- > > > Thanks > > > /Dishara > > > > > > > > > > > -- > > Thanks > > /Dishara > > > -- Thanks /Dishara
