The Latest Episode

You are missing some Flash content that should appear here! Perhaps your browser cannot display it, or maybe it did not initialize correctly.

Tuesday, August 17, 2010 - 09:31

Matt talks to Richard and Jesse about what we've learned in a couple weeks since Go came out. This includes some basic performance metrics, syncing data, early successes, and deployment models. Also, we tie in to the latest products from 360 Works, including SuperContainer which now supports FM Go.

Naming Conventions

Naming Conventions

FILEMAKER PLUG-IN DEVELOPMENT:

360Works your FileMaker plug-in development partner!

NEWS

IT'S NOT FILEMAKER

  • Streaks Free iPhone application for iPhones (iTunes link).
  • Slife tracks everything you do on your computer (Mac & Windows).

DISCUSSION:

Petrowsky, Navarre and special guest John Sindelar of Seedcode talk about conventions. We discuss the importance of naming table occurrences, fields, layouts, scripts, and value lists. Which are the most important, what are the factors to consider, and what are you trying to achieve.

File details
Media file: 

You are missing some Flash content that should appear here! Perhaps your browser cannot display it, or maybe it did not initialize correctly.

Surprisingly interesting!

John nailed it when he implied this is something people care about more than they realize. I wasn't that excited by the topic but I really enjoyed listening to it and even "rewound" it in a couple of places. Thanks so much!

podcast getting better

Matt Navarre's conventions are strikingly similar to my own - therefore he must be right. One of the things I think you missed in discussing field naming conventions is how table width (related to normalization) influences your conventions. If your tables are fairly narrow (mine are typically a dozen fields or less) I believe you'll find a lot of the metadata people tend to add to their field names less useful and somewhat distracting. You also find, for better or for worse, that the table and table occurrence names take on somewhat greater importance.

To be fair to Matt P., I also use his dot convention for variable and object names. For both I typically use object.name as my notation. For variables within scripts, where they are typically used to store field values, this ends up being table.fieldName. For layout objects these end up being objectType.objectName (e.g. field.zipCode or tabPanel.Customers).

Seriously, the podcast is getting much better. Maybe you can dedicate an episode for Matt P. to exorcise all of the silliness and bad jokes, I think that would make the podcast top notch. That's not to say the podcast should be all serious; I think it's good to be lighthearted as long as it doesn't get distracting.

Post new comment

The content of this field is kept private and will not be shown publicly.
  • You can use Markdown syntax to format and style the text. Also see Markdown Extra for tables, footnotes, and more.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <blockquote>
  • Lines and paragraphs break automatically.

More information about formatting options