Hi All,

I asked a couple of questions today.

To try to "give back" (in the smallest of ways) I offer up this tip.

It is based on a best practice that I first learned in the Luke & Laura PHP
and MySQL book:

Insert Comments for everything you are *going* to do into your scripts
before you actually build them. Then write the codes around your comments.

I have added to this my personal practice of adding (in PHP) echo"";
statements for those same comments so I can actually run it and see the path
that it takes me on.

This is now possible in FileMaker.

Now when I am building a script (or a series scripts that work together) I
can use the CustomDialog() function.

so my script might look like:
CustomDialog("COMMENT";"This is where I will open a new window so the user
can select a Class")

The great thing is that you don't need to redundantly write the CustomDialog
and the Comment for good documentation, instead you can write the
CustomDialog and walk through your application process with CustomDialogs
walking you through your code and/or warning you of unfinished work. Then
when you have finished your code, just use the "Disable" button for all of
you CustomDialog comment script steps and they remain in the script, inert
and acting as, well, comments!

I think I will even write a custom function that will append all manner of
environment variables (like dataviewer) FileName, ScriptName maybe some
others. Since I can resize the dialog box if I want to see the details then
I can put everything I want at the bottom of the Comment.

FWIW: $0.02

Thanks.

-- 
Sincerely,
Brad

Reply via email to