DayBackForFileMaker

In App Updates

DayBackForFileMaker.InAppUpdates History

Hide minor edits - Show changes to output

May 19, 2023, at 04:34 PM by 192.88.134.15 -
March 22, 2020, at 05:54 PM by 192.88.134.15 -
Changed lines 5-6 from:
We use this to deliver all sorts of enhancements to the calendar, including some big features like {-FileMaker Go support-} (delivered Jan 15, 2014) and the {-gantt chart-} (delivered Dec 7, 2015). (Here is a list of the [[version history | updates delivered so far]].)
to:
We've used this to deliver all sorts of enhancements to the calendar, including some big features like FileMaker Go support, the Gantt chart, and calendar %newwin% [[https://www.seedcode.com/publish-filemaker-calendar/ | sharing]]. (Here is a list of the [[version history | updates delivered so far]].)
Changed lines 13-14 from:
If you’ve purchased DayBack Calendar on a monthly or yearly subscription, you can download in-app updates for the life of your subscription. But if you purchased DayBack outright, your free updates end after the first year. If your first year of in-app updates have expired, you can extend your updates by purchasing additional years here: %newwin% [[https://www.seedcode.com/extend-in-app-updates/ | extend in-app updates]].
to:
If you’ve purchased DayBack Calendar on a monthly or yearly subscription, you can download in-app updates for the life of your subscription.

But if you purchased DayBack outright, your free updates end after the first year. If your first year of in-app updates have expired, you can extend your updates by purchasing additional years here: %newwin% [[https://www.seedcode.com/extend-in-app-updates/ | extend in-app updates]].
Changed lines 19-25 from:
A lot of the codebase for DayBack is written in JavaScript and executed in the web viewer: that code is modified through these in-app updates without developers needing to do anything. However we are still running this in FileMaker, and there are many interactions with the FileMaker file itself. Sometimes this means there will be necessary changes in FileMaker scripts and possibly layouts. Generally it will be a matter of copying and pasting scripts from a newly downloaded version of DayBack. You can find a link to specific instructions on the [[VersionHistory | version history]] page. If FileMaker file changes are required the update will have two components. Update the core calendar codebase as shown in the video above, then follow the instructions for updating FileMaker scripts.
to:
A lot of the codebase for DayBack is written in JavaScript and executed in the web viewer: that code is modified through these in-app updates without developers needing to do anything. However we are still running this in FileMaker, and there are many interactions with the FileMaker file itself. Sometimes this means there will be necessary changes in FileMaker scripts and possibly layouts. Generally, it will be a matter of copying and pasting scripts from a newly downloaded version of DayBack. You can find a link to specific instructions on the [[VersionHistory | version history]] page. If FileMaker file changes are required the update will have two components. Update the core calendar codebase as shown in the video above, then follow the instructions for updating FileMaker scripts.

!! What if I haven't updated in a REALLY long time

You may find you have a lot of FileMaker changes to make if there are a ton of updates between your version of DayBack and the latest one. These changes aren't *hard*--it's just copying and pasting, so just take your time--but it can be tedious.

SeedCode can make these changes for you and even keep your files up to date as part of an %newwin% [[https://www.seedcode.com/implementation-packages/ | implementation package]]. If that sounds good, please %newwin% [[https://www.seedcode.com/contact/ | get in touch]] for more info
.
December 05, 2018, at 06:06 PM by KC Embrey - Added #Revert
Added line 19:
[[#Revert]]
June 05, 2018, at 05:42 PM by KC Embrey - Typo fix
Changed line 17 from:
A lot of the codebase for DayBack is written in JavaScript and executed in the web viewer: that code is modified though these in-app updates without developers needing to do anything. However we are still running this in FileMaker, and there are many interactions with the FileMaker file itself. Sometimes this means there will be necessary changes in FileMaker scripts and possibly layouts. Generally it will be a matter of copying and pasting scripts from a newly downloaded version of DayBack. You can find a link to specific instructions on the [[VersionHistory | version history]] page. If FileMaker file changes are required the update will have two components. Update the core calendar codebase as shown in the video above, then follow the instructions for updating FileMaker scripts.
to:
A lot of the codebase for DayBack is written in JavaScript and executed in the web viewer: that code is modified through these in-app updates without developers needing to do anything. However we are still running this in FileMaker, and there are many interactions with the FileMaker file itself. Sometimes this means there will be necessary changes in FileMaker scripts and possibly layouts. Generally it will be a matter of copying and pasting scripts from a newly downloaded version of DayBack. You can find a link to specific instructions on the [[VersionHistory | version history]] page. If FileMaker file changes are required the update will have two components. Update the core calendar codebase as shown in the video above, then follow the instructions for updating FileMaker scripts.
December 11, 2017, at 04:04 AM by 192.88.134.15 -
Added lines 12-13:

If you’ve purchased DayBack Calendar on a monthly or yearly subscription, you can download in-app updates for the life of your subscription. But if you purchased DayBack outright, your free updates end after the first year. If your first year of in-app updates have expired, you can extend your updates by purchasing additional years here: %newwin% [[https://www.seedcode.com/extend-in-app-updates/ | extend in-app updates]].
November 20, 2017, at 09:57 PM by 192.88.134.15 -
Changed line 3 from:
DayBack can deliver code changes--both bug fixes and new features--without asking you to reintegrate the calendar into your files.
to:
DayBack can deliver code changes--both bug fixes and new features--without asking you to reintegrate the calendar into your files and without overwriting changes you've made.
November 19, 2017, at 12:27 AM by 192.88.134.15 -
Changed line 15 from:
A lot of the codebase for DayBack is written in Javascript and executed in the web viewer: that code is modified though these in-app updates without developers needing to do anything. However we are still running this in FileMaker, and there are many interactions with the FileMaker file itself. Sometimes this means there will be necessary changes in FileMaker scripts and possibly layouts. Generally it will be a matter of copying and pasting scripts from a newly downloaded version of DayBack. You can find a link to specific instructions on the [[VersionHistory | version history]] page. If FileMaker file changes are required the update will have two components. Update the core calendar codebase as shown in the video above, then follow the instructions for updating FileMaker scripts.
to:
A lot of the codebase for DayBack is written in JavaScript and executed in the web viewer: that code is modified though these in-app updates without developers needing to do anything. However we are still running this in FileMaker, and there are many interactions with the FileMaker file itself. Sometimes this means there will be necessary changes in FileMaker scripts and possibly layouts. Generally it will be a matter of copying and pasting scripts from a newly downloaded version of DayBack. You can find a link to specific instructions on the [[VersionHistory | version history]] page. If FileMaker file changes are required the update will have two components. Update the core calendar codebase as shown in the video above, then follow the instructions for updating FileMaker scripts.
November 19, 2017, at 12:21 AM by 192.88.134.15 -
Deleted lines 8-9:
%newwin% [[https://vimeo.com/243469547]]
Deleted lines 9-10:

(:vimeo 243469547 width=500:)
November 19, 2017, at 12:19 AM by 192.88.134.15 -
Added lines 11-12:
%newwin% [[https://youtu.be/XfDBbOg_0O8]]
Added lines 14-15:

(:youtube XfDBbOg_0O8 width=500:)
November 18, 2017, at 11:53 PM by 192.88.134.15 -
November 18, 2017, at 11:52 PM by 192.88.134.15 -
Added lines 10-11:

(:vimeo 243469547 width=500:)
November 18, 2017, at 11:52 PM by 192.88.134.15 -
Deleted lines 9-10:

(:vimeo 243469547 width=500:)
November 18, 2017, at 11:49 PM by 192.88.134.15 -
Changed lines 9-12 from:
%newwin% [[https://youtu.be/1Ll_qIGMBwM]]

<iframe src="https://player.vimeo.com/video/243469547" width="500" frameborder="0" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>

to:
%newwin% [[https://vimeo.com/243469547]]
Deleted lines 11-12:

(:youtube 1Ll_qIGMBwM width=500:)
November 18, 2017, at 11:48 PM by 192.88.134.15 -
Changed line 13 from:
(: vimeo 243469547 width=500:)
to:
(:vimeo 243469547 width=500:)
November 18, 2017, at 11:43 PM by 192.88.134.15 -
November 18, 2017, at 11:43 PM by 192.88.134.15 -
Added lines 10-13:

<iframe src="https://player.vimeo.com/video/243469547" width="500" frameborder="0" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>

(: vimeo 243469547 width=500:)
September 11, 2017, at 11:30 PM by KC Embrey - added a space
Changed line 5 from:
Weuse this to deliver all sorts of enhancements to the calendar, including some big features like {-FileMaker Go support-} (delivered Jan 15, 2014) and the {-gantt chart-} (delivered Dec 7, 2015). (Here is a list of the [[version history | updates delivered so far]].)
to:
We use this to deliver all sorts of enhancements to the calendar, including some big features like {-FileMaker Go support-} (delivered Jan 15, 2014) and the {-gantt chart-} (delivered Dec 7, 2015). (Here is a list of the [[version history | updates delivered so far]].)
April 11, 2017, at 06:34 PM by 192.88.134.15 -
Added lines 8-9:

%newwin% [[https://youtu.be/1Ll_qIGMBwM]]
November 07, 2016, at 08:12 PM by 192.88.135.15 -
Changed lines 3-5 from:
New to this version of the calendar is the ability to deliver code changes--both bug fixes and new features--without asking you to reintegrate the calendar into your files.

We'll use
this to deliver all sorts of enhancements to the calendar, including some big features like {-FileMaker Go support-} (delivered Jan 15, 2014) and the {-gantt chart-} (delivered Dec 7, 2015). (Here is a list of the [[version history | updates delivered so far]].)
to:
DayBack can deliver code changes--both bug fixes and new features--without asking you to reintegrate the calendar into your files.

Weuse
this to deliver all sorts of enhancements to the calendar, including some big features like {-FileMaker Go support-} (delivered Jan 15, 2014) and the {-gantt chart-} (delivered Dec 7, 2015). (Here is a list of the [[version history | updates delivered so far]].)
December 07, 2015, at 09:14 PM by 192.88.134.15 -
Changed line 5 from:
We'll use this to deliver all sorts of enhancements to the calendar, including some big features like {-FileMaker Go support-} (delivered Jan 15, 2014) and the gantt chart. (Here is a list of the [[version history | updates delivered so far]].)
to:
We'll use this to deliver all sorts of enhancements to the calendar, including some big features like {-FileMaker Go support-} (delivered Jan 15, 2014) and the {-gantt chart-} (delivered Dec 7, 2015). (Here is a list of the [[version history | updates delivered so far]].)
November 24, 2015, at 05:21 PM by 192.88.134.15 -
Changed line 5 from:
We'll use this to deliver all sorts of enhancements to the calendar, including some big features like {-FileMaker Go support-} (delivered Jan 15, 2014 in [[VersionHistory | build]] 9.06) and the gantt chart. (Here is a list of the [[version history | updates delivered so far]].)
to:
We'll use this to deliver all sorts of enhancements to the calendar, including some big features like {-FileMaker Go support-} (delivered Jan 15, 2014) and the gantt chart. (Here is a list of the [[version history | updates delivered so far]].)
November 24, 2015, at 05:20 PM by 192.88.134.15 -
Changed lines 5-7 from:
We'll use this to deliver all sorts of enhancements to the calendar, including some big features like {-FileMaker Go support-} (delivered Jan 15, 2014 in [[VersionHistory | build]] 9.06) and the gantt chart.

Here's what it looks like in action:
to:
We'll use this to deliver all sorts of enhancements to the calendar, including some big features like {-FileMaker Go support-} (delivered Jan 15, 2014 in [[VersionHistory | build]] 9.06) and the gantt chart. (Here is a list of the [[version history | updates delivered so far]].)

And here
's what it looks like in action:
May 10, 2015, at 02:51 AM by 142.4.217.188 -
Changed line 5 from:
We'll use this to deliver all sorts of enhancements to the calendar, including some big features like (- touch device support -) (delivered Jan 15, 2014 in [[VersionHistory | build]] 9.06) and the gantt chart.
to:
We'll use this to deliver all sorts of enhancements to the calendar, including some big features like {-FileMaker Go support-} (delivered Jan 15, 2014 in [[VersionHistory | build]] 9.06) and the gantt chart.
May 10, 2015, at 02:51 AM by 142.4.217.188 -
Changed line 5 from:
We'll use this to deliver all sorts of enhancements to the calendar, including some big features like (-touch device support-) (delivered Jan 15, 2014 in [[VersionHistory | build]] 9.06) and the gantt chart.
to:
We'll use this to deliver all sorts of enhancements to the calendar, including some big features like (- touch device support -) (delivered Jan 15, 2014 in [[VersionHistory | build]] 9.06) and the gantt chart.
May 10, 2015, at 02:48 AM by 142.4.217.188 -
Deleted lines 0-1:
''Note: Touch support for iPad and FMGo was added via in-app updates on Jan 15, 2014 in [[VersionHistory | build]] 9.06.''
Changed lines 5-6 from:
We'll use this to deliver all sorts of enhancements to the calendar, including some big features like mobile device support and the gantt chart.
to:
We'll use this to deliver all sorts of enhancements to the calendar, including some big features like (-touch device support-) (delivered Jan 15, 2014 in [[VersionHistory | build]] 9.06) and the gantt chart.
Changed line 13 from:
A lot of the codebase for DayBack is written in Javascript and executed in the web viewer. We are still running this in FileMaker though, and there are many interactions with the FileMaker file itself. Sometimes this means there will be necessary changes in scripts and possibly layouts. Generally it will be a matter of copying and pasting scripts from a newly downloaded version of DayBack. You can find a link to specific instructions on the [[VersionHistory | version history]] page. If FileMaker file changes are required the update will have two components. Update the core calendar codebase as shown in the video above, then follow the instructions for updating FileMaker scripts etc.
to:
A lot of the codebase for DayBack is written in Javascript and executed in the web viewer: that code is modified though these in-app updates without developers needing to do anything. However we are still running this in FileMaker, and there are many interactions with the FileMaker file itself. Sometimes this means there will be necessary changes in FileMaker scripts and possibly layouts. Generally it will be a matter of copying and pasting scripts from a newly downloaded version of DayBack. You can find a link to specific instructions on the [[VersionHistory | version history]] page. If FileMaker file changes are required the update will have two components. Update the core calendar codebase as shown in the video above, then follow the instructions for updating FileMaker scripts.
February 19, 2015, at 05:29 PM by 142.4.217.187 -
Changed line 15 from:
A lot of the codebase for DayBack is written in Javascript and executed in the web viewer. We are still running this in FileMaker though and there are many interactions with the FileMaker file itself. Sometimes this means there will be necessary changes in scripts and possibly layouts. Generally it will be a matter of copying and pasting scripts from a newly downloaded version of DayBack. You can find a link to specific instructions on the [[VersionHistory | version history]] page.
to:
A lot of the codebase for DayBack is written in Javascript and executed in the web viewer. We are still running this in FileMaker though, and there are many interactions with the FileMaker file itself. Sometimes this means there will be necessary changes in scripts and possibly layouts. Generally it will be a matter of copying and pasting scripts from a newly downloaded version of DayBack. You can find a link to specific instructions on the [[VersionHistory | version history]] page. If FileMaker file changes are required the update will have two components. Update the core calendar codebase as shown in the video above, then follow the instructions for updating FileMaker scripts etc.
February 19, 2015, at 05:27 PM by 142.4.217.187 -
Added lines 13-16:
!! What if FileMaker file changes are required?

A lot of the codebase for DayBack is written in Javascript and executed in the web viewer. We are still running this in FileMaker though and there are many interactions with the FileMaker file itself. Sometimes this means there will be necessary changes in scripts and possibly layouts. Generally it will be a matter of copying and pasting scripts from a newly downloaded version of DayBack. You can find a link to specific instructions on the [[VersionHistory | version history]] page.

Changed line 21 from:
To revert, visit the "Under The Hood" layout and click "Revert to Previous Version".
to:
To revert, visit the "Under The Hood" layout and click "Revert to Previous Version". If any FileMaker script changes were made those will not revert and you may need to undo those changes manually. You could do this by pasting script contents from a backup into the scripts that changed.
January 15, 2015, at 09:24 PM by 142.4.217.187 -
Added lines 1-2:
''Note: Touch support for iPad and FMGo was added via in-app updates on Jan 15, 2014 in [[VersionHistory | build]] 9.06.''
Changed line 7 from:
We'll use this to deliver all sorts of enhancements to the calendar, including some big features like mobile device support (iPad support added in [[VersionHistory | build]] 9.06) and the gantt chart.
to:
We'll use this to deliver all sorts of enhancements to the calendar, including some big features like mobile device support and the gantt chart.
January 15, 2015, at 09:21 PM by 142.4.217.188 -
Changed line 5 from:
We'll use this to deliver all sorts of enhancements to the calendar, including some big features like (-mobile (-device-) support-) (iPad support added in [[VersionHistory | build]] 9.06) and the gantt chart.
to:
We'll use this to deliver all sorts of enhancements to the calendar, including some big features like mobile device support (iPad support added in [[VersionHistory | build]] 9.06) and the gantt chart.
January 15, 2015, at 09:21 PM by 142.4.217.188 -
Changed line 5 from:
We'll use this to deliver all sorts of enhancements to the calendar, including some big features like (-mobile device support-) (iPad support added in [[VersionHistory | build]] 9.06) and the gantt chart.
to:
We'll use this to deliver all sorts of enhancements to the calendar, including some big features like (-mobile (-device-) support-) (iPad support added in [[VersionHistory | build]] 9.06) and the gantt chart.
January 15, 2015, at 09:20 PM by 142.4.217.188 -
Changed line 5 from:
We'll use this to deliver all sorts of enhancements to the calendar, including some big features like mobile device support and the gantt chart.
to:
We'll use this to deliver all sorts of enhancements to the calendar, including some big features like (-mobile device support-) (iPad support added in [[VersionHistory | build]] 9.06) and the gantt chart.
Changed line 13 from:
Should we ever release a breaking change, you'll have the ability to revert to the last version you were running before the update. At the start of the update routine, DayBack saves a copy of your current code base just in case you need to revert. (Only one copy is store, so you can only revert one version back.)
to:
Should we ever release a breaking change, you'll have the ability to revert to the last version you were running before the update. At the start of the update routine, DayBack saves a copy of your current code base just in case you need to revert. (Only one copy is stored, so you can only revert one version back.)
Changed line 1 from:
!! How can I keep DayBack up to date?
to:
!! How Do In-App Updates Work?
Changed line 1 from:
!! How can I keep my app up to date?
to:
!! How can I keep DayBack up to date?
Added lines 1-2:
!! How can I keep my app up to date?
Changed lines 5-6 from:
We hope to use this to deliver all sorts of enhancements to the calendar, including some big features like the gantt chart.
to:
We'll use this to deliver all sorts of enhancements to the calendar, including some big features like mobile device support and the gantt chart.
Added lines 11-17:
!! What if I don't like an update or it breaks something?

Should we ever release a breaking change, you'll have the ability to revert to the last version you were running before the update. At the start of the update routine, DayBack saves a copy of your current code base just in case you need to revert. (Only one copy is store, so you can only revert one version back.)

To revert, visit the "Under The Hood" layout and click "Revert to Previous Version".

=)
Changed line 7 from:
(:youtube sBB0NGXJT-E width=500:)
to:
(:youtube 1Ll_qIGMBwM width=500:)
Changed line 7 from:
(:youtube IsBB0NGXJT-EI width=500:)
to:
(:youtube sBB0NGXJT-E width=500:)
Changed line 7 from:
(:youtube IAr8uQoDt1I width=500:)
to:
(:youtube IsBB0NGXJT-EI width=500:)
Changed line 7 from:
(:youtube |sBB0NGXJT| width=500:)
to:
(:youtube IAr8uQoDt1I width=500:)
Changed lines 7-8 from:
(:youtube |sBB0NGXJT width=500:)
to:
(:youtube |sBB0NGXJT| width=500:)
Changed line 7 from:
(:youtube sBB0NGXJT width=500:)
to:
(:youtube |sBB0NGXJT width=500:)
Changed lines 1-7 from:
%color=red% >> How do we check for updates, vid of the in-app update process. Need the Account Settings messaging file working before we can screenshoot or film this.
to:
New to this version of the calendar is the ability to deliver code changes--both bug fixes and new features--without asking you to reintegrate the calendar into your files.

We hope to use this to deliver all sorts of enhancements to the calendar, including some big features like the gantt chart.

Here's what it looks like in action:

(:youtube sBB0NGXJT width=500:)
Changed line 1 from:
%color=red% >> How do we check for updates, vid of the in-app update process.
to:
%color=red% >> How do we check for updates, vid of the in-app update process. Need the Account Settings messaging file working before we can screenshoot or film this.
Added line 1:
%color=red% >> How do we check for updates, vid of the in-app update process.
(855) SEEDCODE
[email protected]
Follow us: