Spaces
People
Browse
Pages
Blog
Labels
Space Operations
Create
Quick Search
Help
Online Help
Keyboard Shortcuts
Feed Builder
What’s new
Available Gadgets
Log In
Proposals
Current proposals
Rejected proposals
Best Practice
Best Practice
You are not logged in. Any changes you make will be marked as
anonymous
. You may want to
Log In
if you already have an account. You can also
Sign Up
for a new account.
This page is being edited by
.
image-effects
image-attributes
search
attachments
weblink
advanced
Paragraph
Paragraph
Heading 1
Heading 2
Heading 3
Heading 4
Heading 5
Heading 6
Preformatted
Quote
Bold
Italic
Underline
Colour picker
More colours
Formatting
Strikethrough
Subscript
Superscript
Monospace
Clear Formatting
Bullet list
Numbered list
Task list
Outdent
Indent
Align left
Align center
Align right
Link
Table
Insert
Insert Content
Image
Link
Attachment
Symbol
Emoticon
Wiki Markup
Horizontal rule
Task List
Insert Macro
User Mention
Info
JIRA Issue
Status
Gallery
Table of Contents
Other Macros
Page Layout
No Layout
Two column (simple)
Two column (simple, left sidebar)
Two column (simple, right sidebar)
Three column (simple)
Two column
Two column (left sidebar)
Two column (right sidebar)
Three column
Three column (left and right sidebars)
Undo
Redo
Find/Replace
Keyboard Shortcuts Help
Hide the toolbars
Launch editor full screen
<p>I like to propose a new section <strong>Best Practice</strong> besides <strong>Coding Standards</strong>.</p> <p>Some ideas or discussions in <strong>Coding Standards</strong> are already belong more into <strong>Best Practice</strong> than <strong>Coding Standards</strong>, like using UUID for primary key fields, or systems to use for passing script parameters.</p> <p>I understand, there is not always a clear line between both sections. But consider this, when you rely on custom functions, you need FileMaker Pro Advance. But the <strong>Coding Standard</strong> should apply to simple FileMaker Pro users as well.</p> <p>Perhaps we can mention certain features in <strong>Coding Standards</strong> and add a link to <strong>Best Practice</strong> for further explanation and discussion.</p> <p>Some items I would rather put into <strong>Best Practice</strong>:</p> <ul> <li>Field CLIPBOARD</li> <li><span style="text-decoration: line-through;">Custom function UUID</span> (done)</li> <li>Script parameter system</li> </ul> <p>Arnold Kegebein<br /> <sup>arnold (at) kegebein (dot) net</sup></p>
If you are unable to use this CAPTCHA please
contact your administrator
for assistance.
Attachments
Labels
Watch this page
What did you change?
Notify watchers
Edit
Preview
Save
Cancel
Next hint