VirtueMart

h1. GUI standard

Here follows a list of best practices when working develop a virtuemart view.

h2. Using javascript

Administrators should have js enabled. We can expect that administrators have js enabled. Therefore the backend can have features that only reachable with js.

But the shoppers are sometimes afraid to use js and dont trust a shop that is only working with js. So the whole frontend should be workable without js. This does not mean that every feature for comfort must be accessible without js, but the base functions.

h2. Use of of JText and hardcoded formats and simular

@echo JText::_('VM_FILES_LIST_THUMBNAIL_IMG').": ";@

This is very bad and mustn't done. The ":" is hardcoded in the code. The right solution here is to write

@echo JText::_('VM_FILES_LIST_THUMBNAIL_IMG');@

and to add the colon to the language file.

h2. Clicking cancel

When the user clicks cancel, the user is taken back from the editing screen to the page listing. No cancellation message will be shown.

h2. Delete button on row

The page listings should not contain a delete button per row. A single delete button needs to be placed in the toolbar.

h2. Database ID numbers

The page listings should not contain a database ID number.

h2. Sortable columns

A column should, where possible be made sortable by clicking on the column header.

h2. List order fields

A list order field should for new entries be disabled and shown the text string containing: "New items default to the last place. Ordering can be changed after this item is saved." For existing entries, the List order dropdown will be shown, this will allow the user to choose where to place the item.

h2. Hiding of layouts for the joomla view chooser

It is important that there is always the default layout visible in the chooser. In other case layouts used for overrides, makes it impossible to choose the default layout.