Its bit unclear about the things you have mentioned about the UI changes. As I can understand the UI changes needed are minimal. As an example when creating and new event, user must get an option to declare it as a recurring event and the recurring frequency. I can't think of big changes needed to the UI. As I can feel, the events shown in the calendar need not to be changed. Please correct me if I'm wrong.
Thank you. On Mon, Mar 17, 2014 at 9:30 PM, Maduranga Siriwardena < maduranga.siriward...@gmail.com> wrote: > Thank you for the reply. I'll do the necessary changes to the proposal and > inform you when I'm finished. > > Regarding libraries I have included, I have worked with library biweekly > used for iCal object parsing. And it seems to be the library I have > mentioned for CalDav must be changed as it gives full version only in the > paid version. > > Thank you > > > On Mon, Mar 17, 2014 at 5:46 PM, Irina Arkhipets < > irina.arkhip...@gmail.com> wrote: > >> Hi Maduranga, >> >> Sure, you need to add several columns to the appointments table and create >> some additional tables to cover the ical spec.I believe it's impossible to >> make all working using existing database structure. >> >> One more thing which I suppose you have missed are GUI changes. How are >> you >> going to detect which events should be shown on the particular >> day/week/month? I.e. if user goes to some day in the calendar - which >> events should be shown there? >> >> Regarding the used librarues - I used ical4j and caldav4j in one of my >> projects, and have not got experience with the ones from your proposal. >> >> Best regards, >> Irina >> >> >> >> On Mon, Mar 17, 2014 at 6:40 PM, Maduranga Siriwardena < >> maduranga.siriward...@gmail.com> wrote: >> >> > Hi all, >> > Though I created a draft project proposal, I have little bit of a >> concern >> > regarding the storage of iCal objects. Current appointments table have >> the >> > columns to store the general properties of the iCal objects. But the >> iCal >> > spec describes lot more properties for the iCal objects. So the current >> > appointments table may not be enough to hold all the data. In that case >> > what should I do? Is it okay to add more columns to appointments table >> or >> > create more tables as necessary? >> > Some possible mappings between the iCal object properties and >> appointments >> > column tables are mentioned in my project proposal sent in the previous >> > mail. But there also I have faced so problems regarding mapping the two >> > parties. >> > Please help me >> > >> > Thank you. >> > >> > >> > On Sun, Mar 16, 2014 at 8:30 PM, Maduranga Siriwardena < >> > maduranga.siriward...@gmail.com> wrote: >> > >> > > Hi all, >> > > I have written a draft proposal for the project. Please go through it >> and >> > > suggest any possible improvements. Bellow here is the google doc I >> have >> > > created. >> > > >> > > >> > > >> > >> https://docs.google.com/document/d/1zvz768aEwc-5K7YMXJF7AIeVYF_DqDHzDvU2l0e4EJ0/edit?usp=sharing >> > > >> > > Thank you >> > > -- >> > > Maduranga Siriwardena >> > > Undergraduate >> > > University of Moratuwa, Faculty of Engineering >> > > Department of Computer Science and Engineering >> > > >> > >> > >> > >> > -- >> > Maduranga Siriwardena >> > Undergraduate >> > University of Moratuwa, Faculty of Engineering >> > Department of Computer Science and Engineering >> > >> > > > > -- > Maduranga Siriwardena > Undergraduate > University of Moratuwa, Faculty of Engineering > Department of Computer Science and Engineering > -- Maduranga Siriwardena Undergraduate University of Moratuwa, Faculty of Engineering Department of Computer Science and Engineering
