iOS SDK
DayBackForFileMaker.IOSSDK History
Show minor edits - Show changes to output
Changed lines 7-17 from:
Next, there are two places to update with this $$URLScheme variable. First, the navigate to your Calendar layout and edit webviewer's calculated web address, replacing "fmp://" in the sc_filepath variable with
-> $$URLScheme & "://"
Second, open the "Get Webviewer Calendar FilePath" script and edit the $$sc_Webviewer_URL Set Variable step. Just like the webviewer, edit the sc_filepath variable by replacing "fmp://" with
-> $$URLScheme & "://"
That's it!
to:
Find step-by-step instructions, and a great case study here: %newwin% [[https://www.seedcode.com/dayback-calendar-for-ios/ | DayBack in native iOS apps]].
We'd %newwin% [[https://www.seedcode.com/contact/ | love to hear]] about DayBack running in your custom iOS apps =)
We'd %newwin% [[https://www.seedcode.com/contact/ | love to hear]] about DayBack running in your custom iOS apps =)
Changed line 17 from:
That's it! We'd love to hear about DayBack running in your custom iOS apps =)
to:
That's it! We'd %newwin% [[https://www.seedcode.com/contact/ | love to hear]] about DayBack running in your custom iOS apps =)
April 20, 2016, at 01:35 PM
by - Initial content
Changed lines 5-17 from:
Yes! (stay tuned)
to:
Yes! Only a few changes are needed to get DayBack working in your bundled app. In short, DayBack uses the "fmp" url protocol to call scripts in FileMaker Pro or Go, but for iOS SDK bundled apps, we need to use your app's url scheme instead.
First, add a Set Variable step to the "Upon Opening" script, setting a global variable named $$URLScheme. Using Case(), set this variable to the URL scheme you defined when bundling your app, or to "fmp", depending on Get ( ApplicationVersion ) or Get ( SystemPlatform ). If the same DayBack file may be accessed through your app or through FileMaker Go, you can use Get ( ApplicationPath ) to further differentiate between FM Go and your custom app.
Next, there are two places to update with this $$URLScheme variable. First, the navigate to your Calendar layout and edit webviewer's calculated web address, replacing "fmp://" in the sc_filepath variable with
-> $$URLScheme & "://"
Second, open the "Get Webviewer Calendar FilePath" script and edit the $$sc_Webviewer_URL Set Variable step. Just like the webviewer, edit the sc_filepath variable by replacing "fmp://" with
-> $$URLScheme & "://"
That's it! We'd love to hear about DayBack running in your custom iOS apps =)
First, add a Set Variable step to the "Upon Opening" script, setting a global variable named $$URLScheme. Using Case(), set this variable to the URL scheme you defined when bundling your app, or to "fmp", depending on Get ( ApplicationVersion ) or Get ( SystemPlatform ). If the same DayBack file may be accessed through your app or through FileMaker Go, you can use Get ( ApplicationPath ) to further differentiate between FM Go and your custom app.
Next, there are two places to update with this $$URLScheme variable. First, the navigate to your Calendar layout and edit webviewer's calculated web address, replacing "fmp://" in the sc_filepath variable with
-> $$URLScheme & "://"
Second, open the "Get Webviewer Calendar FilePath" script and edit the $$sc_Webviewer_URL Set Variable step. Just like the webviewer, edit the sc_filepath variable by replacing "fmp://" with
-> $$URLScheme & "://"
That's it! We'd love to hear about DayBack running in your custom iOS apps =)
Added lines 1-5:
(:title iOS SDK:)
!! Will DayBack work with the new iOS SDK?
Yes! (stay tuned)
!! Will DayBack work with the new iOS SDK?
Yes! (stay tuned)
