From: Benjamin L. <be...@um...> - 2002-12-01 06:54:26
|
You make a good point here. As far as integrating with iCal directly I=20= do think working directly with the files may be the way to go in the=20 future. I think in my project I approached things from a slightly=20 different point of view, thinking of the server as being remote and not=20= read/writable by iCal (except for the DAV publishing currently=20 supported). Given those limitations, this provides a way to enter=20 events away from your copy of iCal and still receive them later. It's=20= possible, though, that the annoyances of not being able to edit the=20 online calendar from iCal will be too much, and make this all not very=20= useful. That said, there are a few other reasons for using a database - namely=20= I think it's much easier to deal with editing events in a database than=20= modifying a flat file. Another issue is that many web hosting=20 providers do not provide anyway to give the web server/php write=20 permission to your files. In my case, even writing to /tmp is=20 disabled. As for using MySQL, it just seems to be a typical database=20 system these days. What I've built is sort of an independent thing that knows how to write=20= ics files. That's the functionality I built first (minus any user=20 interface). But my goal all along was to integrate with phpicalendar,=20= and so it can also just build the parsed master array that phpicalendar=20= uses. Ben On Sunday, December 1, 2002, at 01:09 AM, Wilfredo S=E1nchez wrote: > Why use MySQL instead of editing the ics calendar files directly? =20= > Or is this a independent thing that just happens to know how to=20 > generate ics files? > > The reason I care is that I figure that iCal will become smart=20 > enough at some point that it will be able to open ics files over DAV=20= > as read-write. Which means the authoritative file can on the net=20 > instead of on one of my computers, and all my Macs can edit it using=20= > iCal (no iSync required) and other software (eg. phpicalendar) can=20 > also edit it. > > If you store the data in MySQL and generate ics files from there,=20 > this wouldn't be possible for those calendars; the only way to edit=20 > them would be though your app. Plus it requires MySQL, which isn't=20 > all that easy to set up and manage. > > -wsv > > > On Saturday, November 30, 2002, at 02:50 PM, Benjamin Levy wrote: > >> phpMyCal is an interface for a schedule database using MySQL. > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Get the new Palm Tungsten T=20 > handheld. Power & Color in a compact size!=20 > http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en > _______________________________________________ > Phpicalendar-devel mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel |