Menu
▾
▴
phpicalendar-devel
|
From: Bill F. <fe...@re...> - 2002-10-24 18:48:41
|
>- creating an iCal with repeating events displays correctly. However, >if a single occurrence of these repeated events is deleted, it will >still be displayed. Moreover, if a single occurrence of a repeated >event is simply shortened, both the shortened version and the normal >repeated version will be displayed for the same time slot. Can you share the entries from the .ics file associated with this? (Either the whole exported calendar, or just the entries between BEGIN:VEVENT and END:VEVENT corresponding with this event, there are probably multiple). Bill |
|
From: Bill F. <fe...@re...> - 2002-10-25 01:48:03
|
Oh, this uses RECURRENCE-ID instead of EXDATE to make the change. I hadn't experienced this before since the palm datebook just uses EXDATE and creates a whole new entry. Given that phpicalendar doesn't care about the relationships between events, this could just be interpreted as a request to delete the event occurrence that happens at the time of the RECURRENCE-ID and has the same UID and create the new event. This could be implemented without worrying about the order of the events in the file by deleting the event if it's already there, or otherwise creating a placeholder "black-hole" event in the master_array that the repeat code would notice and skip. Bill |
|
From: Jordan M. <jm...@MI...> - 2002-10-24 21:26:18
|
On Thursday, October 24, 2002, at 02:48 PM, Bill Fenner wrote: > Can you share the entries from the .ics file associated with this? > (Either the whole exported calendar, or just the entries between > BEGIN:VEVENT and END:VEVENT corresponding with this event, there are > probably multiple). > > Bill Ok... I just did a string search for 20021024. here is what it came up with: Right at the beginning of the file there's this: BEGIN:VCALENDAR CALSCALE:GREGORIAN PRODID:-//Apple Computer\, Inc//iCal 1.0//EN X-WR-CALNAME;VALUE=TEXT:Work X-WR-TIMEZONE;VALUE=TEXT:US/Eastern VERSION:2.0 BEGIN:VEVENT SEQUENCE:10 DTSTAMP:20020916T144235Z SUMMARY:7.02 Setup EXDATE;TZID=US/Eastern:20020924T100000 EXDATE;TZID=US/Eastern:20021024T100000 EXDATE;TZID=US/Eastern:20021015T100000 EXDATE;TZID=US/Eastern:20020926T100000 UID:A827CEFE-C6C4-11D6-8055-0050E4A08D6F DTSTART;TZID=US/Eastern:20020910T100000 DURATION:PT1H RRULE:FREQ=WEEKLY;UNTIL=20021212T045959;INTERVAL=1;BYDAY=TU,TH END:VEVENT Later on there's this: BEGIN:VEVENT RECURRENCE-ID;TZID=US/Eastern:20021024T130000 SEQUENCE:9 DTSTART;TZID=US/Eastern:20021024T130000 DTEND;TZID=US/Eastern:20021024T143000 UID:CD74D485-C6C4-11D6-8055-0050E4A08D6F DTSTAMP:20021024T051413Z END:VEVENT Does that help? Thanks, Jordan |
|
From: Jordan M. <jm...@MI...> - 2002-10-24 21:39:13
|
No, wait, here's the right stuff. Sorry... It looks like the way iCal implements the edit I made is to not include 10/24/02 as an "EXDATE" even though it should be. It puts my edit of 1-2:30 pm as a new entry entirely, so they are both displayed... BEGIN:VEVENT SEQUENCE:8 DTSTAMP:20021014T035519Z SUMMARY:7.02 TA\, Lab DTEND;TZID=US/Eastern:20020910T180000 EXDATE;TZID=US/Eastern:20021015T130000 UID:CD74D485-C6C4-11D6-8055-0050E4A08D6F DTSTART;TZID=US/Eastern:20020910T130000 RRULE:FREQ=WEEKLY;UNTIL=20021212T045959;INTERVAL=1;BYDAY=TU,TH END:VEVENT BEGIN:VEVENT RECURRENCE-ID;TZID=US/Eastern:20021024T130000 SEQUENCE:9 DTSTART;TZID=US/Eastern:20021024T130000 DTEND;TZID=US/Eastern:20021024T143000 UID:CD74D485-C6C4-11D6-8055-0050E4A08D6F DTSTAMP:20021024T051413Z END:VEVENT |
|
From: Jared <xe...@si...> - 2002-10-24 21:50:05
|
Well, EXDATE should be honored. I implemented the code for that a few versions ago. I will check into why it stopped working. With 0.7 there were a lot of code changes to the parser so it might not work anymore. As for single changed events, I haven't done that yet but am planning on it. I have an idea in mind, too, so hopefully it won't be difficult. -Jared |
|
From: Jared <xe...@si...> - 2002-10-25 00:03:28
|
As far as my testing goes, EXDATE still works properly. I didn't have to change anything. See this link: http://ical.silter.org/phpicalendar/ month.php?cal=Jareds32Classes&getdate=20021024 You'll notice that on the 1st and 2nd, and 18, and 21, I have no classes. I deleted the entries in iCal and they are EXDATEs in the .ics file. Please supply a full .ics file where this is broken so I can test the calendar myself while debugging it. I still have to implement single changed events, though. -Jared On Thursday, October 24, 2002, at 04:49 PM, Jared wrote: > Well, EXDATE should be honored. I implemented the code for that a few > versions ago. I will check into why it stopped working. With 0.7 there > were a lot of code changes to the parser so it might not work anymore. > > As for single changed events, I haven't done that yet but am planning > on it. I have an idea in mind, too, so hopefully it won't be > difficult. > > -Jared > > > > > ------------------------------------------------------- > This sf.net email is sponsored by: Influence the future of Java(TM) > technology. Join the Java Community Process(SM) (JCP(SM)) program now. > http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0003en > _______________________________________________ > Phpicalendar-devel mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel |
|
From: Jordan M. <jm...@MI...> - 2002-10-25 02:22:39
|
EXDATE is not broken for me. It's just the single changed event that doesn't display properly, because there was never an EXDATE to delete it, so it's still displayed. Thanks for your efforts. phpicalendar is quite excellent! Jordan On Thursday, October 24, 2002, at 07:43 PM, Jared wrote: > As far as my testing goes, EXDATE still works properly. I didn't have > to change anything. See this link: > http://ical.silter.org/phpicalendar/ > month.php?cal=Jareds32Classes&getdate=20021024 > > You'll notice that on the 1st and 2nd, and 18, and 21, I have no > classes. I deleted the entries in iCal and they are EXDATEs in the > .ics file. Please supply a full .ics file where this is broken so I > can test the calendar myself while debugging it. > > I still have to implement single changed events, though. > > -Jared |
|
From: Waitman C. G. <wa...@em...> - 2002-10-25 12:24:34
|
hello i haven't looked at the code closely, however a pointer - keep in mind that multiple EXDATE lines are quite possible. (ie there is no limit to the number of individual EXDATEs that can show up for each recurring event). take care Waitman Gobble EMK Design Buena Park CA 90621 +1.7145222528 http://emkdesign.com On Thu, 2002-10-24 at 14:49, Jared wrote: Well, EXDATE should be honored. I implemented the code for that a few versions ago. I will check into why it stopped working. With 0.7 there were a lot of code changes to the parser so it might not work anymore. As for single changed events, I haven't done that yet but am planning on it. I have an idea in mind, too, so hopefully it won't be difficult. -Jared ------------------------------------------------------- This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0003en _______________________________________________ Phpicalendar-devel mailing list Php...@li... https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel |
|
From: Jared <xe...@si...> - 2002-10-25 17:10:32
|
My code correctly handles multiple EXDATEs on the same line as well as multiple EXDATE= separated by line. I've also implemented the single changed events so if someone wants to download the CVS and test it out for me, I'd be much appreciative. I tested it myself but like proofreading one's own paper, it's never as good as someone else doing it. Now, on to finish search.php. -Jared On Friday, October 25, 2002, at 07:27 AM, Waitman C. Gobble wrote: > hello > > i haven't looked at the code closely, however a pointer - keep in mind > that multiple EXDATE lines are quite possible. (ie there is no limit to > the number of individual EXDATEs that can show up for each recurring > event). > > take care > > Waitman Gobble > EMK Design > Buena Park CA 90621 > +1.7145222528 > http://emkdesign.com > > > On Thu, 2002-10-24 at 14:49, Jared wrote: > Well, EXDATE should be honored. I implemented the code for that a > few > versions ago. I will check into why it stopped working. With 0.7 > there > were a lot of code changes to the parser so it might not work > anymore. > > As for single changed events, I haven't done that yet but am > planning > on it. I have an idea in mind, too, so hopefully it won't be > difficult. > > -Jared > > > > > ------------------------------------------------------- > This sf.net email is sponsored by: Influence the future > of Java(TM) technology. Join the Java Community > Process(SM) (JCP(SM)) program now. > http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0003en > _______________________________________________ > Phpicalendar-devel mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel > > > > > > ------------------------------------------------------- > This sf.net email is sponsored by: Influence the future > of Java(TM) technology. Join the Java Community > Process(SM) (JCP(SM)) program now. > http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en > _______________________________________________ > Phpicalendar-devel mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X