Refreshing The Calendar
SeedCodeCalendar12.RefreshingTheCalendar History
Hide minor edits - Show changes to output
Changed line 25 from:
-> You may want to set the calendar to refresh every few seconds so you can mount a big version in a public space to coordinate schedules. You can see some examples of this %newwin% [[http://seedcodenext.wordpress.com/2011/02/10/whiteboard-versions-of-the-calendar/ | here]] and learn how to automate that refresh in %newwin% [[http://seedcodenext.wordpress.com/2011/11/04/calendar-as-dashboard/ | this blog post]].
to:
-> You may want to set the calendar to refresh every few seconds so you can mount a big version in a public space to coordinate schedules. You can see some examples of this %newwin% [[http://www.seedcode.com/whiteboard-versions-of-the-calendar/ | here]] and learn how to automate that refresh in %newwin% [[http://www.seedcode.com/calendar-as-dashboard/ | this blog post]].
Changed lines 13-14 from:
-> You'll see a "refresh" button in the calendar header to the right of the arrows that move to the next dat/week/month. This button is there in case you'd like to manually ask the server if there are any new events to display. The calendar caches the events it draws and doesn't continually ask the server for new events: this is one reason the calendar is so much faster than traditional FileMaker calendars.
to:
-> You'll see a "refresh" button in the calendar header to the right of the arrows that move to the next day/week/month. This button is there in case you'd like to manually ask the server if there are any new events to display. The calendar caches the events it draws and doesn't continually ask the server for new events: this is one reason the calendar is so much faster than traditional FileMaker calendars.
Changed lines 21-25 from:
-> The calendar layouts have a [[Script triggers | script trigger]] assigned to them which will refresh the calendar each time you arrive at the calendar layout.
to:
-> The calendar layouts have a [[Script triggers | script trigger]] assigned to them which will refresh the calendar each time you arrive at the calendar layout.
'''Refreshing on a timer'''
-> You may want to set the calendar to refresh every few seconds so you can mount a big version in a public space to coordinate schedules. You can see some examples of this %newwin% [[http://seedcodenext.wordpress.com/2011/02/10/whiteboard-versions-of-the-calendar/ | here]] and learn how to automate that refresh in %newwin% [[http://seedcodenext.wordpress.com/2011/11/04/calendar-as-dashboard/ | this blog post]].
'''Refreshing on a timer'''
-> You may want to set the calendar to refresh every few seconds so you can mount a big version in a public space to coordinate schedules. You can see some examples of this %newwin% [[http://seedcodenext.wordpress.com/2011/02/10/whiteboard-versions-of-the-calendar/ | here]] and learn how to automate that refresh in %newwin% [[http://seedcodenext.wordpress.com/2011/11/04/calendar-as-dashboard/ | this blog post]].
Changed lines 9-10 from:
-> If you'd like to add some additional behaviors to the process of editing an event, add them to the script "Close Window & Refresh Calendar" right before or after the commit step after the comment "Commit Record".
to:
-> If you'd like to add some additional behaviors to the process of editing an event, add them to the script "Close Window & Refresh Calendar" before the comment "Commit Record". (Changes made later in the script may be happening on the wrong record as our Dependency Chain scripts may have moved us to another record.)
Changed lines 21-27 from:
-> The calendar layouts have a [[Script triggers | script trigger]] assigned to them which will refresh the calendar each time you arrive at the calendar layout.
'''Refreshing iCal sources'''
-> If you've set up one of your [[multiple sources | sources]] as an iCal URL you many not want to refresh the URL each time you refresh the calendar (as pulling down the URL contents is the slowest thing the calendar does). So we've created a method by which you can specify how often you'd like that URL refreshed.
-> On the Source No X layout you've mapped to this source (as part of your [[integration]]) you'll see a value for "Refresh Every" on the "Recommended" tab. Edit this value in layout mode to reflect the number of hours you'd like to wait between refreshes of the URL. With this value in place, we'll only include the URL in regular calendar refreshes (such as when switching views or editing an event) every X hours.
'''Refreshing iCal sources'''
-> If you've set up one of your [[multiple sources | sources]] as an iCal URL you many not want to refresh the URL each time you refresh the calendar (as pulling down the URL contents is the slowest thing the calendar does). So we've created a method by which you can specify how often you'd like that URL refreshed.
-> On the Source No X layout you've mapped to this source (as part of your [[integration]]) you'll see a value for "Refresh Every" on the "Recommended" tab. Edit this value in layout mode to reflect the number of hours you'd like to wait between refreshes of the URL. With this value in place, we'll only include the URL in regular calendar refreshes (such as when switching views or editing an event) every X hours
to:
-> The calendar layouts have a [[Script triggers | script trigger]] assigned to them which will refresh the calendar each time you arrive at the calendar layout.
Changed lines 5-8 from:
-> When you click on an event in the calendar, we present the event in an Event Details mini window. When you close that window we try to refresh the calendar if you've modified the record, provided you've clicked the green "check" button at the bottom of the window: if you close the window using the Close Window command or the red close button on the window frame, we simply close the window and don't attempt to refresh then calendar.
-> If you're interested in how this works we're recording the modification state of the record when the window is opened (and this supports having multiple Event Detail windows open at once). Then when you click our blue button to close the window we're checking the modification count and refreshing the calendar if the event was modified.
-> If you're interested in how this works we're recording the modification state of the record when the window is opened (and this supports having multiple Event Detail windows open at once). Then when you click our blue button to close the window we're checking the modification count and refreshing the calendar if the event was modified.
to:
-> When you click on an event in the calendar, we present the event in an Event Details mini window. When you close that window we try to refresh the calendar if you've modified the record, provided you've clicked the green "check" button at the bottom of the window: if you close the window using the Close Window command or the red close button on the window frame, we simply close the window and don't attempt to refresh the calendar.
-> If you're interested in how this works, we're recording the modification state of the record when the window is opened (and this supports having multiple Event Detail windows open at once). Then when you click our blue button to close the window we're checking the modification count and refreshing the calendar if the event was modified.
-> If you're interested in how this works, we're recording the modification state of the record when the window is opened (and this supports having multiple Event Detail windows open at once). Then when you click our blue button to close the window we're checking the modification count and refreshing the calendar if the event was modified.
Changed lines 23-24 from:
Refreshing iCal sources
to:
'''Refreshing iCal sources'''
Changed lines 11-15 from:
> > refreshing iCal sources
to:
'''The refresh button'''
-> You'll see a "refresh" button in the calendar header to the right of the arrows that move to the next dat/week/month. This button is there in case you'd like to manually ask the server if there are any new events to display. The calendar caches the events it draws and doesn't continually ask the server for new events: this is one reason the calendar is so much faster than traditional FileMaker calendars.
-> This means, however, that edits and new event records won't just show up on your calendar without any interaction on your part. Normally this isn't a big deal as the calendar requests new events from the server each time you edit a record, filter the calendar, or switch views. But if you're just staring at your screen, you may want to click "refresh" to make sure you have the latest data from the server.
-> Note that while this doesn't sound very "FileMaker like", most complicated screens (and certainly most traditional calendars) don't "refresh" automatically either, since the relationships they use for display are too "deep" to respond to notifications of new or edited records from the server.
'''Refreshing when arriving at the calendar layout'''
-> The calendar layouts have a [[Script triggers | script trigger]] assigned to them which will refresh the calendar each time you arrive at the calendar layout.
Refreshing iCal sources
-> If you've set up one of your [[multiple sources | sources]] as an iCal URL you many not want to refresh the URL each time you refresh the calendar (as pulling down the URL contents is the slowest thing the calendar does). So we've created a method by which you can specify how often you'd like that URL refreshed.
-> On the Source No X layout you've mapped to this source (as part of your [[integration]]) you'll see a value for "Refresh Every" on the "Recommended" tab. Edit this value in layout mode to reflect the number of hours you'd like to wait between refreshes of the URL. With this value in place, we'll only include the URL in regular calendar refreshes (such as when switching views or editing an event) every X hours.
-> You'll see a "refresh" button in the calendar header to the right of the arrows that move to the next dat/week/month. This button is there in case you'd like to manually ask the server if there are any new events to display. The calendar caches the events it draws and doesn't continually ask the server for new events: this is one reason the calendar is so much faster than traditional FileMaker calendars.
-> This means, however, that edits and new event records won't just show up on your calendar without any interaction on your part. Normally this isn't a big deal as the calendar requests new events from the server each time you edit a record, filter the calendar, or switch views. But if you're just staring at your screen, you may want to click "refresh" to make sure you have the latest data from the server.
-> Note that while this doesn't sound very "FileMaker like", most complicated screens (and certainly most traditional calendars) don't "refresh" automatically either, since the relationships they use for display are too "deep" to respond to notifications of new or edited records from the server.
'''Refreshing when arriving at the calendar layout'''
-> The calendar layouts have a [[Script triggers | script trigger]] assigned to them which will refresh the calendar each time you arrive at the calendar layout.
Refreshing iCal sources
-> If you've set up one of your [[multiple sources | sources]] as an iCal URL you many not want to refresh the URL each time you refresh the calendar (as pulling down the URL contents is the slowest thing the calendar does). So we've created a method by which you can specify how often you'd like that URL refreshed.
-> On the Source No X layout you've mapped to this source (as part of your [[integration]]) you'll see a value for "Refresh Every" on the "Recommended" tab. Edit this value in layout mode to reflect the number of hours you'd like to wait between refreshes of the URL. With this value in place, we'll only include the URL in regular calendar refreshes (such as when switching views or editing an event) every X hours.
Changed lines 9-15 from:
-> If you'd like to add some additional behaviors to the process of editing an event, add them to the script "Close Window & Refresh Calendar" right before or after the commit step after the comment "Commit Record".
to:
-> If you'd like to add some additional behaviors to the process of editing an event, add them to the script "Close Window & Refresh Calendar" right before or after the commit step after the comment "Commit Record".
> > the refresh button
> > refreshing when arriving at the calendar layout
> > refreshing iCal sources
> > the refresh button
> > refreshing when arriving at the calendar layout
> > refreshing iCal sources
Changed lines 1-9 from:
to:
!! When does the calendar refresh?
'''Editing Events'''
-> When you click on an event in the calendar, we present the event in an Event Details mini window. When you close that window we try to refresh the calendar if you've modified the record, provided you've clicked the green "check" button at the bottom of the window: if you close the window using the Close Window command or the red close button on the window frame, we simply close the window and don't attempt to refresh then calendar.
-> If you're interested in how this works we're recording the modification state of the record when the window is opened (and this supports having multiple Event Detail windows open at once). Then when you click our blue button to close the window we're checking the modification count and refreshing the calendar if the event was modified.
-> If you'd like to add some additional behaviors to the process of editing an event, add them to the script "Close Window & Refresh Calendar" right before or after the commit step after the comment "Commit Record".
'''Editing Events'''
-> When you click on an event in the calendar, we present the event in an Event Details mini window. When you close that window we try to refresh the calendar if you've modified the record, provided you've clicked the green "check" button at the bottom of the window: if you close the window using the Close Window command or the red close button on the window frame, we simply close the window and don't attempt to refresh then calendar.
-> If you're interested in how this works we're recording the modification state of the record when the window is opened (and this supports having multiple Event Detail windows open at once). Then when you click our blue button to close the window we're checking the modification count and refreshing the calendar if the event was modified.
-> If you'd like to add some additional behaviors to the process of editing an event, add them to the script "Close Window & Refresh Calendar" right before or after the commit step after the comment "Commit Record".
