Revision as of 17:39, 20 March 2013

Nota Bene

this a spot to jot down guidelines of varying types, largely for front end developers & designers. This includes code style, theming style, and whatever else will help us produce a consistent, shiny produce faster. If you have questions about this page, please ping :ally in #windev.

Message Dialogs
- Use message dialogs to present blocking questions that require the user's input.
- Use message dialogs for rror messages that apply to the overall app context.
Use "Title Case" only for heading text. For other text (including button labels, menu items, etc.) use "Sentence case" [1][2].

Generally we use Mozilla Coding Style, with a few exceptions:
- You don't need to wrap lines to 80 characters. Use longer lines (up to around 120 characters; use your judgement) if it improves readability.
Consistency is king, and supersedes any particular rule.

Coding Style exceptions:
- Put the opening brace on the same line as the "function" keyword (rather than on a separate line by itself).
https://developer.mozilla.org/en-US/docs/JavaScript_Tips

if you create an attribute and it has only one value, do not set it to true/false. Remove the attribute in the case of false. This produces cleaner, more concise css, without imperiling js readability.

@@ Line 3: / Line 3: @@
 = Design/Theming guidelines =
-* use flyout panes over dialogs
+*Message Dialogs
+** Use message dialogs to present blocking questions that require the user's input.
+** Use message dialogs for rror messages that apply to the <strong>overall app context</strong>.
 * Use "Title Case" only for heading text.  For other text (including button labels, menu items, etc.) use "Sentence case" [http://msdn.microsoft.com/en-us/library/windows/apps/hh465308.aspx][http://msdn.microsoft.com/en-us/library/windows/desktop/aa511453.aspx].
 = Coding Guidelines =
 * Generally we use [https://developer.mozilla.org/en-US/docs/Developer_Guide/Coding_Style Mozilla Coding Style], with a few exceptions: