I Cal
SeedCodeComplete2.ICal History
Hide minor edits - Show changes to output
Added lines 21-22:
''Zulu support is built into SeedCode Complete as of version 3.0. You'll still need to purchase a license of %newwin% [[http://www.seedcode.com/zulu | Zulu]], but the integration is all done for you.''
Changed lines 3-4 from:
Yes. The calendar can show iCal data sources along side FileMaker records. Learn more here: [[Multiple Sources]] ''Note that version 3.0 of SeedCode Complete removed the ability to show iCal sources along side your FileMaker Records; this was slowing down the calendar a bit and with %newwin% [[http://www.seedcode.com/zulu | Zulu]] it didn't seem necessary any more.''
to:
Yes. The calendar can show iCal data sources along side FileMaker records. Learn more here: [[Multiple Sources]]
''Note that version 3.0 of SeedCode Complete removed the ability to show iCal sources along side your FileMaker Records; this was slowing down the calendar a bit and with %newwin% [[http://www.seedcode.com/zulu | Zulu]] it didn't seem necessary any more.''
''Note that version 3.0 of SeedCode Complete removed the ability to show iCal sources along side your FileMaker Records; this was slowing down the calendar a bit and with %newwin% [[http://www.seedcode.com/zulu | Zulu]] it didn't seem necessary any more.''
Changed lines 3-4 from:
Yes. The calendar can show iCal data sources along side FileMaker records. Learn more here: [[Multiple Sources]]
to:
Yes. The calendar can show iCal data sources along side FileMaker records. Learn more here: [[Multiple Sources]] ''Note that version 3.0 of SeedCode Complete removed the ability to show iCal sources along side your FileMaker Records; this was slowing down the calendar a bit and with %newwin% [[http://www.seedcode.com/zulu | Zulu]] it didn't seem necessary any more.''
Changed lines 17-18 from:
If you need a live connection between FileMaker and iCal, check out %newwin% [[http://www.seedcode.com/zulu | Zulu]], our server-side plugin that turns FileMaker Server into an iCal Server. This means you can view ''and edit'' your FileMaker records from any iCal compatible client, including the calendar on your iPhone and iPad.
to:
If you need a live connection between FileMaker and iCal, check out %newwin% [[http://www.seedcode.com/zulu | '''Zulu''']], our server-side plugin that turns FileMaker Server into an iCal Server. This means you can view ''and edit'' your FileMaker records from any iCal compatible client, including the calendar on your iPhone and iPad.
Added lines 15-18:
!! Live Connection to FileMaker from iCal
If you need a live connection between FileMaker and iCal, check out %newwin% [[http://www.seedcode.com/zulu | Zulu]], our server-side plugin that turns FileMaker Server into an iCal Server. This means you can view ''and edit'' your FileMaker records from any iCal compatible client, including the calendar on your iPhone and iPad.
If you need a live connection between FileMaker and iCal, check out %newwin% [[http://www.seedcode.com/zulu | Zulu]], our server-side plugin that turns FileMaker Server into an iCal Server. This means you can view ''and edit'' your FileMaker records from any iCal compatible client, including the calendar on your iPhone and iPad.
Changed lines 7-8 from:
The Pro calendar includes support for exporting found sets of events to the iCal format. You'll find a button in the upper right of the Event List layout that will export the found set as an .ics file to your desktop. This script takes a source number as a parameter so you can export any of your FileMaker sources to iCal.
to:
The calendar includes support for exporting found sets of events to the iCal format. You'll find a button in the upper right of the Event List layout that will export the found set as an .ics file to your desktop. This script takes a source number as a parameter so you can export any of your FileMaker sources to iCal.
Added lines 22-23:
Finally, if you're exporting on Windows, you'll need the to have the free ScriptMaster plugin from [[http://www.360works.com/ftp-plugin/ | 360Works]] installed: our scripts use this to get past a bug in FileMaker's xml export.
Changed lines 13-21 from:
-> Consider automating this by scheduling these exports using FileMaker Server script schedules. Then use an [[http://www.360works.com/ftp-plugin/ | ftp plugin]] to script the delivery of these .ics files to your web server.
to:
-> Consider automating this by scheduling these exports using FileMaker Server script schedules. Then use an [[http://www.360works.com/ftp-plugin/ | ftp plugin]] to script the delivery of these .ics files to your web server.
!! Troubleshooting the iCal Export
The iCal export requires an xsl file in the Extras folder that came with SeedCode Complete.
This xsl file can be placed almost anywhere you'd like-- provided you tell the script "Export Found Set to iCal { SourceNumber }" where to find it. If you're serving the calendar you can even put the file on a web server, so everyone has the same path to it, and the give the script the file's URL.
Here's how. Edit the script "Export Found Set to iCal { SourceNumber }" and find the "Export Records" step. Click "specify" next to Specify output file. When the next screen comes up click OK and you'll be on a screen called "Specify XML and XSLT options". Select HTTP Request, and enter the URL of the seedcodeiCalExport.xsl file. Or leave the setting on "file" if you're not using a server and just find the seedcodeiCalExport.xsl file on your machine.
!! Troubleshooting the iCal Export
The iCal export requires an xsl file in the Extras folder that came with SeedCode Complete.
This xsl file can be placed almost anywhere you'd like-- provided you tell the script "Export Found Set to iCal { SourceNumber }" where to find it. If you're serving the calendar you can even put the file on a web server, so everyone has the same path to it, and the give the script the file's URL.
Here's how. Edit the script "Export Found Set to iCal { SourceNumber }" and find the "Export Records" step. Click "specify" next to Specify output file. When the next screen comes up click OK and you'll be on a screen called "Specify XML and XSLT options". Select HTTP Request, and enter the URL of the seedcodeiCalExport.xsl file. Or leave the setting on "file" if you're not using a server and just find the seedcodeiCalExport.xsl file on your machine.
Added lines 1-13:
!! Can I show iCal records IN the calendar?
Yes. The calendar can show iCal data sources along side FileMaker records. Learn more here: [[Multiple Sources]]
!! Exporting to iCal
The Pro calendar includes support for exporting found sets of events to the iCal format. You'll find a button in the upper right of the Event List layout that will export the found set as an .ics file to your desktop. This script takes a source number as a parameter so you can export any of your FileMaker sources to iCal.
Here are some tips to help you get the most out of this:
-> You can load exported files to [[http://phpicalendar.net/ | phpiCalendar]] to see that those records on your web site. Exporting multiple files will be treated as individual calendars meaning that you can try to replicate your FileMaker calendar's filters by exporting one .ics per "filter".
-> Consider automating this by scheduling these exports using FileMaker Server script schedules. Then use an [[http://www.360works.com/ftp-plugin/ | ftp plugin]] to script the delivery of these .ics files to your web server.
Yes. The calendar can show iCal data sources along side FileMaker records. Learn more here: [[Multiple Sources]]
!! Exporting to iCal
The Pro calendar includes support for exporting found sets of events to the iCal format. You'll find a button in the upper right of the Event List layout that will export the found set as an .ics file to your desktop. This script takes a source number as a parameter so you can export any of your FileMaker sources to iCal.
Here are some tips to help you get the most out of this:
-> You can load exported files to [[http://phpicalendar.net/ | phpiCalendar]] to see that those records on your web site. Exporting multiple files will be treated as individual calendars meaning that you can try to replicate your FileMaker calendar's filters by exporting one .ics per "filter".
-> Consider automating this by scheduling these exports using FileMaker Server script schedules. Then use an [[http://www.360works.com/ftp-plugin/ | ftp plugin]] to script the delivery of these .ics files to your web server.
