10 Good Developer Habits & Scripts

Sometimes, it's those little suggestions or tricks which make for a more enjoyable and productive development environment. In this video, I cover some of what I consider to be the most helpful things for working within FileMaker - at least when it comes to scripts and good habits.

Hate having to scroll down your long list of scripts in order to target the one script you're working on? Use a Testing Code script. Working with more than one developer and need a good method of communicating what was done and when? Use some dedicated "dev" scripts. Need to open those lengthy API docs for that integration you're working on? Make a Docs script.

If there isn't some little tip or tidbit in this video that helps you become a better FileMaker developer then, congratulations, you've reached the level of Master FileMaker Developer!

AttachmentSize
10GoodDeveloperHabits.zip1.65 MB
Tags:

Comments

Hey Matt - Great tutorial as always.
Just wondering if the sample file is supposed to be locked so that we cannot access the script workspace ?

Thanks
Dave

The file should open with the normal full access default Admin account. Maybe check the download and make sure the properties on the file don’t have write access disabled?

-- Matt Petrowsky - ISO FileMaker Magazine Editor

Strange behaviour as @StephenWWonfor mentioned. The file auto logged in as Admin with no password.
Reopened holding the shift key and manually entered accountname Admin and all is working as expected now.

Thanks again

Dave - "Admin" and no password.
Matt - great stuff as always.
Note: Did not behave as expected first time, now it does - opens logged in to Admin

Hi Matt,

As always — great video — thanks.

About the "deprecated" folder — I have used this technique for years — works great.

Let me add this tip. For any script I add to this folder, I select all script lines and use the "Disable" function. I do this as an extra level of security - thus ensuring that the script can not actually run.

In deprecated scripts, it can be helpful to add some notification as the very first step - whether that's Show Custom Dialog, or writing a log entry, or sending an email. It's also worthwhile to rename the script with "DEPRECATED " as a prefix to the original name; it stands out when using the debugger.

--
Daniel Farnan

Ignorance is curable, not preventable

Hi,
Thanks for a great video. I also do my development on Mac. Which monitors are you using in 'Portrait mode' on either side and how do you connect them?

Shree

MedPro ehf