A group from Excelisys consisting of Andrew Persons, Mike Duncan and Geoff Ryle participated in the recording of an Adatasol podcast last night. We had a great time, and enjoyed talking tech and FileMaker with co-hosts Dan Weiss and Theo Gantos. In the podcast, we discussed our latest free “tips-n-tricks” postings that take advantage of FileMaker Pro 10‘s new script triggers feature. Check out past podcasts at their website or on iTunes, and stay tuned for our upcoming episode.
Check out the new “Tips-n-Trick” file just posted to the “Downloads” section of our web site, contributed by Mike Duncan, Lead Developer at Excelisys, Inc.
FileMaker Pro 10 introduced native script triggers as a tool for developers to utilize in their solutions. This example demonstrates the usage of a search filter, which many FileMaker developers are familiar with in complex portal filtering solutions. Now, with the use of script triggers, it is simple enough to implement the same functionality but you are not restricted to displaying results in a portal, and therefore have much more flexibility in the interface. Instead of being required to set a complex key that drives a relationship, your search script can be as simple or exotic as your solution requires. One key difference available in FileMaker Pro 10 is that you no longer need to wait for a field to be exited in order to trigger an action, allowing interaction between the user and database not available before without the use of third party plug-ins.
This example is a simple implementation of script triggers by using the OnObjectModify trigger set on the global fields that are being used to provide search criteria on the sample data. As the user types search criteria, a search script gets run, narrowing the search results in real time. Also used in this demo is the new functionality to set a field by name. This is used to allow the user to select a field to search on, which is used to set the field by name that is searched. This sounds simple enough, and displaces the need for large, complex branching “if” statements in a script editor that might have duplicated this functionality in previous versions of FileMaker.
Since these fields wouldn’t be applicable in Find Mode, we also set an object with text that displays only when you are in Find Mode that alerts the user to this fact as a reminder, as well as graying out the filter fields. This is done using conditional formatting to change the appearance of text and layout objects that are dependent on the current mode.
Script Triggers in FileMaker Pro 10 are an absolute game changer for developer in what they can accomplish. Hopefully this example provides a small peek at the potential that this new functionality provides.
Special thanks to Brian Dunning for providing the sample data used in this demonstration that is available at http://www.briandunning.com/sample-data/
Everyone at Excelisys loves to hear that rhetorical question asked: “Woah! You can do THAT in FileMaker?” Oh yeah, you can. Well this is one of those moments, and we just posted a demo file and white paper about it up on our Excelisys web site.
http://www.excelisys.com/tips-tricks-filemaker-downloads.php
With the new script triggers introduced in the recently released FileMaker Pro 10, we all can now deliver a richer user experience to our customers – one that incorporates a familiar and elegant interface mechanism: drag-and-drop.
The new demo file we’ve posted is fully unlocked, requires FileMaker Pro 10, and includes three interface examples of the drag-and-drop technique. There is also an embedded PDF white paper that further explains how the whole thing is built, with sample code.
The most obvious use is sorting. Let’s say you’re in a band and you’re trying to organize a set list. Just drag the song titles into the order you want, or change it up again just by dragging. How long have we wanted this feature?
Another great use is building a list. Let’s say you’re managing the receiving dock in a warehouse and you have two lists: the one on the left shows four items ordered on a PO, while the list on the right is blank but will include the items you are receiving. Today you only received one item, so you drag that item from the list on the left into the list on the right. Easy, right?
But here’s yet another great example: nesting in a hierarchical interface. We’ve previously posted a tip on how to build a hierarchical interface, so here’s how to – BAM! – kick it up a notch. Let’s say you have an outline for a presentation, and you decide to move some of your subtopics to another parent topic. By just dragging the subtopic to another topic in the list, you have rearranged your outline – any nested subtopics in the item you moved are automatically moved with it, just as you’d expect.
And that’s when it hits you… THIS is FileMaker???
These great techniques, examples and white papers are brought to you (once again) by eX-Team Senior Developer Andrew Persons.
Can you think of any other great drag-and-drop example ideas? Leave us a comment and tell us about it, and if applicable let us know how this technique helped you in your projects.
Explore the eX Cetera Blog |
|||||
|
|
|||||
