You gotta love FileMaker Go. Go’s ability to effortlessly create data-driven mobile apps and extend existing desktop data applications to mobile users is transformative. But sooner or later, almost all of us run up against one of Go’s core limitations: Its lack of native plugins.
Most of us understand this isn’t an oversight, but rather a basic constraint imposed by the architecture of Apple’s iOS. Still, the inability to extend Go’s native toolbox through plugins often limits the capabilities and expressiveness of Go solutions. Many developers and users have probably daydreamed of how much better their mobile solutions might be if only they could find some way of extending Go with plugin functionality. If only… if only…
In FileMaker Go 12, we can now do exactly this.
Giving New Life To Your Mobile Database
OK. Let’s get started…
A Quick Review. Or, "How To Create Your Very Own Monster in 4 Easy Steps"
Let’s quickly recap the steps explained previously, this time following in the footsteps of that immortal classic, “Young Frankenstein”.
Step 1: Find a Body
As the movies teach us, a budding mad scientist building a creature from scratch must start with a body. When the young Dr. Frankenstein needed a body for his creature, he was forced to unearth a cold, hulking corpse in the dead of night. We FileMaker Go developers have it much easier: We’ll just place a named Web Viewer on our Go layouts, staying nice and cozy as we do so.
Step 2: Select a Brain (and Make it a Good One)
Step 3: Give Your Creature Life
Step 4: Teach Your Creature to Speak
Finally, our now-living creature must be able to communicate to us. Here’s where FileMaker 12’s new fmp:// protocol really helps us out: In earlier versions of Go, Web Viewers trying to converse with native FileMaker scripts made awkward grunting noises, just like so many matinee creatures. Igor, Frau BlÃ¼cher and company needed an entire movie to resolve this tricky conundrum, ultimately resorting to a dangerous brain transference procedure to enable their monster to communicate clearly. In our case, FileMaker 12’s new fmp:// protocol makes it easy: Our Web Viewers will speak directly and eloquently to our native FileMaker scripts right out of the box, with no need for expensive brain surgeries our HMO’s likely won’t cover. Huzzah!
And Now to the Laboratory…
jsGO Web Viewer
jsGO Custom Functions
Is It Friendly?
Any useful plugin must be easy to integrate into our solutions and simple to use. We understand that any FileMaker plugin will be complex under the hood, but we also expect this complexity to be hidden within the plugin. Our technique meets this test nicely.
Putting On The Ritz
Follow Brian on Twitter
. . . . . . . . . . . . .