ISO FileMaker Magazine

When FileMaker, Inc. released the new theming system for FileMaker Pro a while back, they made one of the best decisions possible for a development platform. They chose to go with an industry standard instead of rolling their own solution.

The standard they chose to use was CSS (Cascading Style Sheets). While their implementation was specific to the platform, and the whole "cascading" part didn't really apply, the choice was a good one.

Today, the upside is the fact that it's the same language of the web. The same which is used to provide ultimate control over how everything looks on a given web page. Essentially, full power and control to the designer or developer. The downside, in FileMaker's case, is they can only expose certain aspects of the CSS as their internal development resources allow. They have to keep moving the product forward in other areas as well as the user interface.

So, knowing that CSS is behind the scenes, there are certain things we can do to modify the look and feel beyond what FileMaker's Inspector palette exposes. This video is about a certain insider trick which can make your use of a company logo infinitely easier when it comes time to make a simple change down the road. Check it out!

What would software be without icons? Would it be like looking at a tree without leaves? For some reason, a tree just looks more like a tree when it has leaves. Right?

So, this video is about how FileMaker uses SVG icons within it’s buttons. If you’ve always wondered how to make the most of FileMaker’s support of SVG icons, then look no further. In this video I’ll show you my own personal workflow for creating and integrating icons into a FileMaker solutions. You can integrate icons into your solution in a surprisingly quick fashion if you’re willing to get familiar with a bit of node and gulp.

Of course, even if you have no desired to install node.js, you may very well find tips and tricks which will help you expedite the process of integrating icons.

For me, it's always been one of those itches I could never quite scratch. You know, the fact that in order to show some of your user interface graphics you needed to store these graphics within your database - along with your data.

In fact, it's pretty much accepted that you create container fields, many times within a dedicated table, to store graphics and resources.

The issue I had with this approach was not that it needs to be done, but the fact that the user interface graphics were not separated out from the rest of my data. I wanted to be able to simply "draw" graphics onto the layout.

Well, this itch can now be scratched with FileMaker 13's new Base64* set of functions. While you still need at least one container field in order to render your graphics, the new additions have reduced the number of fields in total.

Watch this video to gain a full understanding of how this works and just how easy it is to integrate into your own solutions!