JavaScript is Eating the FileMaker World Video

My presentation, “JavaScript is Eating the World” was released last week along with the rest of the Web Track presentations.

Read more

v1.5 of Barcode Creator Released

We rolled out a new version of Barcode Creator over the weekend. We added support for another symbology bringing the total to 19, and we added one improvement to the QR Code generation. This upgrade is free for all owners of Barcode Creator. You can download it from your account at Geist Interactive

New Symbology

Added the “GS1 DataBar Expanded” symbology. This is the same as DataBar Expanded, but with strict GS1 validation. (DataBar Expanded behaves the same: it will still encode data as GS1 if the input follows GS1 formatting rules, but will also tolerate non-GS1 data, as before.)

Improvements

Improved QR Code compatibility with scanners that do not use the default configuration from the QR Code 2005 specification (including FileMaker Go).

Upgrading

It is always best to start over. Delete the old Barcode Creator module folder and copy and paste or import the new one into your file. Then reconnect your scripts.

FileMaker DevCon 2016

I am back! Last year, I took the year off from speaking. But this year I am back. I have two presentations on totally awesome fun topics; building native iOS apps, and JavaScript.

Read more

FileMaker QuickBooks Mac Integration

We love FileMaker. We love QuickBooks Online. We also love Macs, and that proved to be a problem. The existing solutions for connecting FileMaker to Quickbooks Online required a Windows PC. The combination of FileMaker QuickBooks Mac was a problem. We decided to solve it. Read more

What Can WordPress Teach FileMaker?

WordPress is the dominant web platform on the planet.  It’s ecosystem is orders of magnitude larger than FileMaker’s. Clearly they are doing something right.  Is there anything that FileMaker and FileMaker Developers can learn from WordPress’s success? Read more

Announcing GoSign v3, Scriptable, FileMaker Signature Capture

FileMaker Signature Capture

Newbury Park, California, Feb 5th, 2014 – Geist Interactive is pleased to introduce GoSign 3.0 for FileMaker Go and FileMaker Pro. GoSign 3.0 is a major rewrite of the popular FileMaker Signature Capture add-on for FileMaker Go. GoSign allows FileMaker Signature Capture to happen anywhere in the layout, including in new FileMaker 13 PopOver Controls and Slide Panels. Read more

Looping Through and Filtering Lists with FileMaker

Looping through and filtering lists of values turns out to be a common task in FileMaker.  Having a few different techniques at your disposal is quite useful. In this post, we are going to look at a set of related techniques for processing lists.  First we look at how to loop through each item and perform some function or task on each item.  Then we will move on to a custom function for filtering lists by any valid FileMaker expression.  Finally we will use another Custom Function to easily parse Layout Object Names from a layout and use them in a dynamic slide navigation scheme.

Read more

What Does GetField(fieldName) Return?

FileMaker’s GetField() function has always been struck me as a curious beast.  Every since it’s release back in Filemaker 5.5 or there abouts I had assumed that it returned the contents of the field specified by the parameter.  But there were a couple of cases where it didn’t work that way and I’d get fooled every once in while.  I didn’t quite understand what was going on.  I think I finally stumbled on an easy way to keep it straight. Read more

Unit Testing in FileMaker

Unit Testing is the practice of  testing individual chunks of code to make sure they are working as designed.  Ideally it is done with a single click of a button, so that you can do it all the time.  Traditional FileMaker coding doesn’t lend itself to this practice very well.  It’s just too tightly coupled.  But if you take some time to organize your code in a modular way you can start to incorporate something like Unit Tests into your development practice.

First you need to separate out the logic you want to test into well factored API like scripts.  These can take parameters and they usually return a result.  The main point is that you give these scripts the power to do what the need to do to your database, and you make sure that they report back if they fail or not.

Once you have your API scripts laid out you can the write yourself a bunch of test scripts that exercise those API script and make sure they are doing their job.  I put my Unit Tests in a separate file so I don’t clutter up my deliverable files. Then as I go along writing code, I periodically go back and run all the scripts. When I do something that cause my tests to fail, I can see it right away.  I know what test broke and hopefully I get some kind of error that might help tell me how it broke. From there, its relatively easy to go about fixing the code.

Here is a movie that shows what that ends up looking like.