Some of us on the Beezwax team had the pleasure of watching John Sindelar and Todd Geist present their new GoZync framework at June’s DIGFM developer meetup. If you know anything about either of these fellows, you know that they are both very sharp and visionary developers. Now they’ve thrown their collective brain power at the problem of “How do mobile users work with their databases offline?”
Color is one of the most important tools available to you when designing user interfaces. Using a little color can turn a drab wall of text into something attractive and readable.
Can you build an Assets Management database in FileMaker Pro in 80 minutes?
Thursday night Beezwax completed that challenge!
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 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.
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