How It Works
SCSubscribe2.HowItWorks History
Hide minor edits - Show changes to output
Changed line 15 from:
-> When you're testing SeedCode Subscribe using our public engine, you're actually using our instance of the seedcode_subscribe_engine on our demo sever.
to:
-> When you're testing SeedCode Subscribe using our public engine, you're actually using our instance of the seedcode_subscribe_engine on our demo sever. (The free demo of SeedCode Subscribe does not include this seedcode_subscribe_engine folder)
Changed line 11 from:
'''2. The seedcode_subscribe_engine'''
to:
'''2. The seedcode_subscribe_engine folder'''
Changed lines 1-2 from:
SeedCode Subscribe is actually pretty simple and is made up of three parts.
to:
SeedCode Subscribe is actually pretty simple. It is made up of three parts.
Changed lines 5-10 from:
-> The SeedCode_Subscribe_Setup.fmp12 file is just a URL builder. It helps you write URLs that you then subscribe to in iCal or Google Calendar. Much of the work in the setup file is in validating these URLs and checking your work.
-> You can think of a URL as a way of describing a find request for events in your FileMaker files.
-> Since SeedCode_Subscribe.fmp12 just helps you build URLs it doesn't need to be hosted withyour solution unless you're using Google Calendar. Learn more about that [[GoogleCalendar | here]].
-> You can think of a URL as a way of describing a find request for events in your FileMaker files.
-> Since SeedCode_Subscribe.fmp12 just helps you build URLs it doesn't need to be hosted with
to:
-> The SeedCode_Subscribe_Setup.fmp12 file is just a tool that builds your subscription URLs for you. These are the URLs you enter into iCal or Google Calendar to subscribe to the data that comes from your FileMaker database. Much of the work in the Setup file is in composing and validating these URLs and checking your configuration.
-> You can think of the subscription URL as a way of describing a find request for events in your FileMaker file.
-> As such, the SeedCode_Subscribe_Setup.fmp12 file does not need to be hosted on a server, unless you are using Google Calendar. Learn more about that [[GoogleCalendar | here]].
-> You can think of the subscription URL as a way of describing a find request for events in your FileMaker file.
-> As such, the SeedCode_Subscribe_Setup.fmp12 file does not need to be hosted on a server, unless you are using Google Calendar. Learn more about that [[GoogleCalendar | here]].
Changed lines 13-15 from:
-> The seedcode_subscribe_engine consists of a php file which sits on your FileMaker Server. This translates URL requests from iCal or Google Calendar into find requests for FileMaker Server and then transforms the results into the iCal grammar iCal and Google Calendar expect.
-> When you're testing Subscribe using ourdemo server you're actually using our instances of the seedcode_subscribe_engine on one of our demo severs.
-> When you're testing Subscribe using our
to:
-> The seedcode_subscribe_engine folder sits on your FileMaker Server. The files it contains translate the URL requests from iCal or Google Calendar into find requests that act upon your FileMaker file, and then transforms the results into the data format iCal and Google Calendar expect.
-> When you're testing SeedCode Subscribe using our public engine, you're actually using our instance of the seedcode_subscribe_engine on our demo sever.
-> When you're testing SeedCode Subscribe using our public engine, you're actually using our instance of the seedcode_subscribe_engine on our demo sever.
Changed lines 3-6 from:
'''1. The SeedCode_Subscribe.fmp12'''
-> The SeedCode_Subscribe.fmp12FileMaker file is just a URL builder. It helps you write URLs that you then subscribe to in iCal or Google Calendar. Much of the work in SeedCode_Subscribe.fmp12 is in validating these URLs and checking your work.
-> The SeedCode_Subscribe.fmp12
to:
'''1. SeedCode_Subscribe_Setup.fmp12'''
-> The SeedCode_Subscribe_Setup.fmp12 file is just a URL builder. It helps you write URLs that you then subscribe to in iCal or Google Calendar. Much of the work in the setup file is in validating these URLs and checking your work.
-> The SeedCode_Subscribe_Setup.fmp12 file is just a URL builder. It helps you write URLs that you then subscribe to in iCal or Google Calendar. Much of the work in the setup file is in validating these URLs and checking your work.
Changed line 19 from:
-> Your FileMaker file holds the data you'd like to see in the calendar. In the SeedCode_Subscribe.fmp12 URL builder you've specified which layout and which fields contain the specific data you'd like to see in any given calendar. The URL also holds attributes of the calendar that aren't ''in'' your data (like the calendar's color and name).
to:
-> Your FileMaker file holds the data you'd like to see in the calendar. In the SeedCode_Subscribe_Setup.fmp12 you've specified which layout and which fields contain the specific data you'd like to see in any given calendar. The URL also holds attributes of the calendar that aren't ''in'' your data (like the calendar's color and name).
Added lines 14-15:
-> When you're testing Subscribe using our demo server you're actually using our instances of the seedcode_subscribe_engine on one of our demo severs.
Changed lines 3-11 from:
'''1. The SeedCode_Subscribe.fmp12''' FileMaker file is just a URL builder. It helps you write URLs that you then subscribe to in iCal or Google Calendar. Much of the work in SeedCode_Subscribe.fmp12 is in validating these URLs and checking your work.
You can think of a URL as a way of describing a find request for events in your FileMaker files.
Since SeedCode_Subscribe.fmp12 just helps you build URLs it doesn't need to be hosted with your solution unless you're using Google Calendar. Learn more about that [[GoogleCalendar | here]].
'''2. The seedcode_subscribe_engine'''consists of a php file which sits on your FileMaker Server. This translates URL requests from iCal or Google Calendar into find requests for FileMaker Server and then transforms the results into the iCal grammar iCal and Google Calendar expect.
3. Your FileMaker file holds the data you'd like to see in the calendar. In the SeedCode_Subscribe.fmp12 URL builder you've specified which layout and which fields contain the specific data you'd like to see in any given calendar. The URL also holds attributes of the calendar that aren't ''in'' your data (like the calendar's color and name).
You can think of a URL as a way of describing a find request for events in your FileMaker files.
Since SeedCode_Subscribe.fmp12 just helps you build URLs it doesn't need to be hosted with your solution unless you're using Google Calendar. Learn more about that [[GoogleCalendar | here]].
'''2. The seedcode_subscribe_engine'''
3. Your FileMaker file holds the data you'd like to see in the calendar. In the SeedCode_Subscribe.fmp12 URL builder you've specified which layout and which fields contain the specific data you'd like to see in any given calendar. The URL also holds attributes of the calendar that aren't ''in'' your data (like the calendar's color and name).
to:
'''1. The SeedCode_Subscribe.fmp12'''
-> The SeedCode_Subscribe.fmp12 FileMaker file is just a URL builder. It helps you write URLs that you then subscribe to in iCal or Google Calendar. Much of the work in SeedCode_Subscribe.fmp12 is in validating these URLs and checking your work.
-> You can think of a URL as a way of describing a find request for events in your FileMaker files.
-> Since SeedCode_Subscribe.fmp12 just helps you build URLs it doesn't need to be hosted with your solution unless you're using Google Calendar. Learn more about that [[GoogleCalendar | here]].
'''2. The seedcode_subscribe_engine'''
-> The seedcode_subscribe_engine consists of a php file which sits on your FileMaker Server. This translates URL requests from iCal or Google Calendar into find requests for FileMaker Server and then transforms the results into the iCal grammar iCal and Google Calendar expect.
'''3. Your FileMaker File'''
-> Your FileMaker file holds the data you'd like to see in the calendar. In the SeedCode_Subscribe.fmp12 URL builder you've specified which layout and which fields contain the specific data you'd like to see in any given calendar. The URL also holds attributes of the calendar that aren't ''in'' your data (like the calendar's color and name).
-> The SeedCode_Subscribe.fmp12 FileMaker file is just a URL builder. It helps you write URLs that you then subscribe to in iCal or Google Calendar. Much of the work in SeedCode_Subscribe.fmp12 is in validating these URLs and checking your work.
-> You can think of a URL as a way of describing a find request for events in your FileMaker files.
-> Since SeedCode_Subscribe.fmp12 just helps you build URLs it doesn't need to be hosted with your solution unless you're using Google Calendar. Learn more about that [[GoogleCalendar | here]].
'''2. The seedcode_subscribe_engine'''
-> The seedcode_subscribe_engine consists of a php file which sits on your FileMaker Server. This translates URL requests from iCal or Google Calendar into find requests for FileMaker Server and then transforms the results into the iCal grammar iCal and Google Calendar expect.
'''3. Your FileMaker File'''
-> Your FileMaker file holds the data you'd like to see in the calendar. In the SeedCode_Subscribe.fmp12 URL builder you've specified which layout and which fields contain the specific data you'd like to see in any given calendar. The URL also holds attributes of the calendar that aren't ''in'' your data (like the calendar's color and name).
Changed lines 1-11 from:
to:
SeedCode Subscribe is actually pretty simple and is made up of three parts.
'''1. The SeedCode_Subscribe.fmp12''' FileMaker file is just a URL builder. It helps you write URLs that you then subscribe to in iCal or Google Calendar. Much of the work in SeedCode_Subscribe.fmp12 is in validating these URLs and checking your work.
You can think of a URL as a way of describing a find request for events in your FileMaker files.
Since SeedCode_Subscribe.fmp12 just helps you build URLs it doesn't need to be hosted with your solution unless you're using Google Calendar. Learn more about that [[GoogleCalendar | here]].
'''2. The seedcode_subscribe_engine''' consists of a php file which sits on your FileMaker Server. This translates URL requests from iCal or Google Calendar into find requests for FileMaker Server and then transforms the results into the iCal grammar iCal and Google Calendar expect.
3. Your FileMaker file holds the data you'd like to see in the calendar. In the SeedCode_Subscribe.fmp12 URL builder you've specified which layout and which fields contain the specific data you'd like to see in any given calendar. The URL also holds attributes of the calendar that aren't ''in'' your data (like the calendar's color and name).
'''1. The SeedCode_Subscribe.fmp12''' FileMaker file is just a URL builder. It helps you write URLs that you then subscribe to in iCal or Google Calendar. Much of the work in SeedCode_Subscribe.fmp12 is in validating these URLs and checking your work.
You can think of a URL as a way of describing a find request for events in your FileMaker files.
Since SeedCode_Subscribe.fmp12 just helps you build URLs it doesn't need to be hosted with your solution unless you're using Google Calendar. Learn more about that [[GoogleCalendar | here]].
'''2. The seedcode_subscribe_engine''' consists of a php file which sits on your FileMaker Server. This translates URL requests from iCal or Google Calendar into find requests for FileMaker Server and then transforms the results into the iCal grammar iCal and Google Calendar expect.
3. Your FileMaker file holds the data you'd like to see in the calendar. In the SeedCode_Subscribe.fmp12 URL builder you've specified which layout and which fields contain the specific data you'd like to see in any given calendar. The URL also holds attributes of the calendar that aren't ''in'' your data (like the calendar's color and name).
