At PauseOnError, Vincenzo Menanno led the session on FileMaker User Experience (UX) for Developers, brainstorming how to improve the tools we use as FileMaker developers. There were a couple dozen participants, including Heather Winkle, Product Manager for User Experience at FileMaker Inc.
In February, four Beez traveled to New York for PauseOnError, the annual winter gathering of FileMaker developers. PauseOnError runs as an “Unconference”; attendees organize the entire agenda, and work together to support presentations and ad-hoc discussions. This makes for a highly-relevant and participatory experience.
The attached file demonstrates a technique for opening/closing areas of a record, allowing a user to hide the information they don’t want to see.
FileMaker File: DisclosureAreas2.fp7
Neither I nor my client can anticipate every chart that the solution’s users might want to see. A user’s desire to view a high-level visual representation of their data can be spontaneous and idiosyncratic. This technique allows for the user to create an ad hoc chart, albeit within narrow parameters (i.e. the chart is simple, presents only counts of values, and is pre-formatted).
FileMaker File: ChartActiveField.fp7
I wanted to quickly create a firewall port forward (AKA NAT rule) for the Terminal Services port on a Cisco ASA 5505. Since it had initially been setup using ASDM, it seemed natural to also create the port forward this way.
I recently needed to total up some records in a found set in a FileMaker solution, but I wanted to keep all the revisions within the scripts so that I could easily migrate the changes from the development system to production. This solution also already had quite a few “special case” calcs and fields, and I didn’t want to add any more clutter to the schema.
We recently needed to remove the intermediate directories in a large number of parent directories. So, if we started with /A/B/C/D, we wanted to end up with /A/B/D. It seemed simple at the time, so I blithely said “Sure, I can write that easily as a shell script”.
We have a wiki server running Mac OS X Server 10.6, and rather than have users type something like this:
which would be the standard URL, we instead wanted to use the much simpler:
If you have a FileMaker system and you need to script the processing of adding or removing files on the server, the first problem you are going to come across is: how do I stop the server from a script?
You may already be familiar with the fmsadmin command. This is present on both Mac OS and Windows installs of FileMaker server. You can simply run the following command in Terminal to stop the server:
fmsadmin stop server