Standard feature layouts 1.6 - Revision history

Elin: /* Parameters */

2010-02-07T16:03:31Z

‎Parameters

Elin: /* Language Strings */

2010-02-07T16:02:06Z

‎Language Strings

Elin: /* Ordering of Toolbars */

2010-02-07T15:58:40Z

‎Ordering of Toolbars

Elin at 15:50, 7 February 2010

2010-02-07T15:50:43Z

Elin at 02:15, 15 January 2010

2010-01-15T02:15:54Z

Elin: Common layout elements

2010-01-14T08:20:39Z

Common layout elements

New page

Common features should be organized consistently across different parts of the application.
Some layouts will have additional element and these should be ordered in a fixed area within each of these.

== Ordering of Toolbars ==

Toolbars for forms, from left to right in left to right languages.

* Apply (save without closing)
* Save & Close
* Save as Copy
* Save & New
* Close/Cancel (Cancel only for new items)
* Help

Toolbars for grids

* New
* Edit
* Separator
* Publish
* Unpublish
* Separator
* Remove
* Archive
* Trash/Delete (Delete only when trash state is selected)
* Separator
* Options
* Separator
* Help

==Parameter Groupings==

Left pane, top to bottom

* Title
* Alias
* State
* Access
* Text

Right pane, top to bottom

* Required
* Basic Options
* Integration
* Access Rules
* Meta Data

All required elements must have required="true" in the corresponding xml.

==Grid Headers==

Filters

* Text Field
* Search
* Clear
* Select Access
* Select State
* Select Category

Right to left

* Check Box
* Title
* State
* Ordering
* Access
* ID

[[Category:Specifications Version 1.6]] [[Category:Specifications]]

@@ Line 76: / Line 76: @@
 ==Parameters==
-* Defaults should always be "Use Global" or ""
+* Defaults should always be "Use Global" or "" (i.e. empty string).
 ==Language Strings==

@@ Line 81: / Line 81: @@
 *Strings in text should be in all uppercase (no spaces, separate words with underscores for readability)
-*Put the most general string possible and allow for overrides
+*Put the most general string possible and allow for overrides. Put the string in the most general place possible to encourage consistency and reuse.
-  For example JTOOLBAR_XXX should always be put into the en.mod_toolbar.ini so that there is consistent usage throughout. This is important even if the toolbar item only exists once, since third party developers may need to use it.
+  For example JTOOLBAR_XXX should always be put into the en.mod_toolbar.ini so that there is consistent usage throughout.
 [[Category:Specifications Version 1.6]] [[Category:Specifications]]

← Older revision		Revision as of 15:50, 7 February 2010
Line 78:		Line 78:
	* Defaults should always be "Use Global" or ""		* Defaults should always be "Use Global" or ""

		+	==Language Strings==
		+
		+	*Strings in text should be in all uppercase (no spaces, separate words with underscores for readability)
		+	*Put the most general string possible and allow for overrides
		+	For example JTOOLBAR_XXX should always be put into the en.mod_toolbar.ini so that there is consistent usage throughout. This is important even if the toolbar item only exists once, since third party developers may need to use it.


	[[Category:Specifications Version 1.6]] [[Category:Specifications]]		[[Category:Specifications Version 1.6]] [[Category:Specifications]]

@@ Line 26: / Line 26: @@
 * Trash/Delete (Delete only when trash state is selected)
 * Separator
-* Options
+* Defaults (Preferences)
 * Separator
 * Help

@@ Line 72: / Line 72: @@
 * Access
 * ID
 [[Category:Specifications Version 1.6]] [[Category:Specifications]]